Gajim - 2025-04-24


  1. nigel

    >> Maybe I should have posted that in jdev > jdev? What is it? I am interested in the key management for E2EE too. 😲

  2. nigel

    > Read markers bugs when Gajim window was closed seem to be fixed with 2.1.x! thanks ❤️

  3. badrihippo

    gimmi, that is actually being discussed in jdev at the moment, so a good time to join too!

  4. badrihippo

    On a different note: if I wanted to implement extensible in-band registration (XEP-0389) for Gajim, would that be possible using a plugin or would it involve modifying the main codebase itself?

  5. lovetox

    Main, but you would need to first start in nbxmpp

  6. badrihippo

    I see

  7. badrihippo

    Would there be interest in merging this feature to nbxmpp if I implemented it?

  8. lovetox

    Yeah why not

  9. nicomuc

    I can't investigate right now but message retractions from gajim do not show in cheogram. Maybe it's a cheogram bug. [end of the partial useless bug report]

  10. badrihippo

    Cool! We're planning to eventually use that XEP for Prav to handle "log in with phone number" in a standardised way, but I thought here would be an easier place to implement it the first time round

  11. lovetox

    nicomuc: retraction is still under decelopment

    👍 3
  12. colinr

    hellow friends does the latest version of gajim support gtk3 themes like oomox-themes

  13. colinr

    if yes please how

  14. cal0pteryx

    colinr: no, the latest version of Gajim uses gtk4

  15. colinr

    so there is no way i can customize it i need the black theme can you help out

  16. cal0pteryx

    Your theme needs to support gtk4

  17. martini_lich

    > so there is no way i can customize it i need the black theme can you help out you could try running gajim with the environment variable `GTK_THEME` set to your theme

  18. Schimon

    lovetox. I think that Metalink would be a good addition to every chat client. I have sent a respond to your message. I wouldd be glad to read your argument or respond, and continue to XSF if needed.

  19. Schimon

    lovetox. I think that Metalink would be a good addition to every chat client. I have sent a respond to your message. I would be glad to read your argument or respond, and continue to XSF if needed.

  20. lovetox

    Schimon, im not judging one standard against another here, RFC not specifically made for XMPP can be used, but a XEP should describe how and under what conditions.

  21. lovetox

    see for example Vcard, https://xmpp.org/extensions/xep-0292.html

  22. lovetox

    or here microblogging with atom https://xmpp.org/extensions/xep-0277.html

  23. Schimon

    I did not think of vCard as an example, even though I use it. Please post your argument for the record. I will refer to XSF.

  24. Schimon

    lovetox. I think that the argument about vCard is better than about Atom Over XMPP.

  25. Schimon

    lovetox. I think that the argument about vCard is better than the argument about Atom Over XMPP.

  26. lovetox

    not sure what you mean, 0277 reuses atom, to blog

  27. Schimon

    My approach was just to send Metalink as BoB and then the client would parse it.

  28. Schimon

    lovetox. Yes, it does, but in a parted fashion, which is good. It was easier for me to understand your argument when you mentioned vCard, than thinking of Atom Syndication Format.

  29. Schimon

    lovetox. Yes, it does, but in a parted fashion, which is good. It was easier for me to understand your argument when you mentioned vCard, than thinking of Atom Syndication Format, which was exactly the standard that I was thinking of while I was writing a respond to your reply.

  30. lovetox

    if you want something supported across the ecosystem in XMPP, you should propose your ideas to the community, you can do this on the standards mailing list

  31. lovetox

    im sure there are X other standards to share some file links out there, why is yours the best fit for xmpp? why not the 2 standards that already exist? etc

  32. Schimon

    I think that I have posted about it already, some months ago. I will check.

  33. lovetox

    these are things that should be discussed before clients implementing stuff

    ❤️ 1
  34. Schimon

    Yes.

  35. lovetox

    filesharing is also a bit of a sensitive topic here, there are multiple clients who support already multiple different standards, im not inclined at this point to fracture the eco system even more and implement a third standard.

  36. Schimon

    https://xmpp.pimux.de/file_share/0680a86f-f86e-743c-a463-12cfb334f0e8/gajim-yes-yess-is-now-away.png

  37. Schimon

    > filesharing is also a bit of a sensitive topic here, there are multiple clients who support already multiple different standards, im not inclined at this point to fracture the eco system even more and implement a third standard. File sharing was an example. There are many other software that support Metalink.

  38. lovetox

    but what does that help me? i dont talk to these other applications or? im talking only to other xmpp clients

  39. Schimon

    > but what does that help me? i dont talk to these other applications or? im talking only to other xmpp clients Before you have persuaded me, my argument was that it is not related to XEP, hence I have mentioned file sharing.

  40. Schimon

    > but what does that help me? i dont talk to these other applications or? im talking only to other xmpp clients Before you have persuaded me, my argument was that it is not related to XEP, hence I have mentioned file sharing as an example for my previous argument.

  41. hannibal

    > could it be a message from the muc itself? > This message has been moderated by gajim@conference.gajim.org/cal0pteryx. Begründung: Spam

  42. lovetox

    you did get this out of the database text field?

  43. lovetox

    very weird, but ok i guess we dont handle messages by the MUC itself correctly in the export

  44. lovetox

    will fix it

  45. hannibal

    > you did get this out of the database text field? yes

  46. hannibal

    only one line with this message has an empty resource the other 11 lines are fine

  47. hannibal

    Could it be caused by deleting the message locally before it was moderated?

  48. lovetox

    no, doesnt matter how it ended up there, resource = NULL is a valid case when we get message from the MUC itself

  49. lovetox

    and the function assumes there will always be a resource

  50. lovetox

    so thats the bug i will fix later

  51. hannibal

    okay

  52. nigel

    > these are things that should be discussed before clients implementing stuff ❤️