Gajim - 2025-01-17


  1. lissine

    CuriousPanda84, It's possible that the old avatar is cached by your contact's client

  2. lissine

    Tell them to log out and log in again

  3. CuriousPanda84

    would restarting the client not trigger that same flow?

  4. lissine

    It depends on which client they use Are they using Gajim?

  5. CuriousPanda84

    Yes. We are both using Gajim.

  6. lissine

    Yes, it should be.

  7. lissine

    You can also try doing the same

  8. CuriousPanda84

    Well yes, we have both tried restarting with no luck.

  9. lissine

    can you see the avatar from a third account?

  10. CuriousPanda84

    I was just going to try that to troubleshoot. I can check

  11. CuriousPanda84

    Yes, after I exchanged contact requests from a secondary account the pfp showed up

  12. CuriousPanda84

    And like I mentioned before, my Gajim client doesn't let me toggle on the "Share my online status" toggle with the contact I am having issues with. It simply resets back to off everytime

  13. lovetox

    Yes that's the problem

  14. lovetox

    If you don't share status it does not share the avstar

  15. lovetox

    On what Gajim version are you?

  16. chud

    > When I "note to myself" at work (Gajim 1.8.4), I don't get the messages at home (Gajim master of last week) and vice versa. That should work, right? I also encounter this behavior, across clients, I'm in draugr.de. I may randomly see or not see the messages on the other client if it's offline when the message is sent. I'm guessing the server may be imposing some crazy limit on mam size for myself-to-myself message store?.. Anyway, it doesn't seem to be the client's fault, because I get this across gajim, dino and cheogram.

  17. cal0pteryx

    chud: did you check if mam was disabled for specific contacts in your account?

  18. chud

    How?

  19. lovetox

    cal0pteryx: I bet its all ejabberd servers

  20. lovetox

    Ask in the support chat what the rules are for putting messages to self into MAM

  21. chud

    This is terrible UX when you don't know if these messages will be lost, to the point where it should be considered a bug.

  22. lovetox

    It's probably more of a server config bug

  23. lovetox

    But hard to say if we don't know the exact reason

  24. lovetox

    I just know I don't have this problem with any ejabberd or prosody instance I used

  25. chud

    I think it is almost definitely a server issue, but I'm just saying clients should at least be able to indicate to the user somehow that hey, this server is f***d up.

  26. lovetox

    Would be nice, I actually want that for some server stuff that we can discover

  27. lovetox

    But I doubt this is one of them

  28. Schimon

    Good day!

  29. Schimon

    > 🔈 Follow Gajim: https://fosstodon.org/@gajim I think, that it would be productive to have a Libervia or Movim account, because Gajim is of XMPP.

  30. Kris

    Why not both?

  31. chud

    why not bridge?

    🌉 2
  32. debacle

    > cal0pteryx: I bet its all ejabberd servers I experienced the problem on debian.org, which is prosody 0.12.3.

  33. lovetox

    https://share.hoerist.com/philipp/85CdE66NS5W9OjrZ/43d9df7f-a29a-4d0c-9f66-b09c9eb60765.png

  34. lovetox

    debacle, ^

  35. lovetox

    here you can find the resource priority

  36. debacle

    > here you can find the resource priority Funny: I have four accounts online right now and can see this field only on one of them! That's why I didn't find it first. On that account, it is `0`.

  37. lovetox

    debacle, sounds weird, there is no code that hides this setting

  38. lovetox

    What version of Gajim are you using?

  39. lovetox

    debacle if you want to debug this it seems there is no way around getting server debug logs

  40. lovetox

    that you dont see the priority setting i can not really explain, there is no code that hides that setting

  41. lovetox

    maybe you run some modified Gajim version?

  42. debacle

    > maybe you run some modified Gajim version? It's the one I created for Debian experimental: `1.9.5+git20250111.b3e738d2-1` It is not heavily patched: https://salsa.debian.org/xmpp-team/gajim/-/tree/debian/experimental/debian/patches?ref_type=heads

  43. debacle

    Oh, forget it! My fault!

  44. debacle

    I was confused by "Adjust to status".

  45. debacle

    I just can't switch it off.

  46. debacle

    No, it works, it just takes some time.

  47. lovetox

    set it to 0

  48. debacle

    All good, all perfect, it's probably just my aging eyes.

  49. lovetox

    and tell me if the problem occurs again

  50. lovetox

    we definitly should remove this stuff

    👍 1
  51. lovetox

    nobody needs this

  52. debacle

    Yes, done. Can't see before Monday, though ;-)

  53. lovetox

    yeah np