Gajim - 2019-10-05

  1. marmistrz Gajim 1.1.3 repeatedly shows an event (the blue exclamation mark) for a muc mention. How do I stop it (make gajim aware that I don't have to be notified again)?
  2. marmistrz Is it fixed in master btw?
  3. lovetox dont know any blue eclamation mark marmistrz
  4. lovetox please screenshot
  5. marmistrz
  6. marmistrz This is how the tray icon behaves when you are mentioned
  7. marmistrz but for one MUC I'm always getting this for one old message
  8. marmistrz Here come the logs: 05.10.2019 09:25:57 (I) nbxmpp.idlequeue: read timeout set for fd 29 on 55 seconds
  9. lovetox do you have enabled to be notified on new messages?
  10. lovetox every message in a muc is new
  11. lovetox we dont load messages from the database in a muc
  12. marmistrz lovetox, no.
  13. marmistrz I suppose these are fetched by MUC-MAM
  14. lovetox is it always only one message?
  15. lovetox this MUC seems like it has no MAM
  16. lovetox and i think this is the problem
  17. marmistrz No, it's messages from last 37 days
  18. lovetox so whats the problem? you dont want to be notified if someone mentions you in the last 37 days?
  19. marmistrz I don't want to be notified that I was mentioned every time I open gajim
  20. lovetox open means starting the application?
  21. marmistrz yup
  22. marmistrz Or reconnect, probably
  23. lovetox so are you saying this one muc downloads the same history again and again on ever restart?
  24. marmistrz Yes.
  25. marmistrz Conversations says that MAM is supported for this channel
  26. lovetox ok so then thats the problem isnt it? and not that you get mentioned for a message you received
  27. lovetox yeah then please gather logs when you join the channel and download these messages
  28. marmistrz Yes. I have the full logs, I'll send them by pm
  29. marmistrz I said _repeatedly_ in the first message :)
  30. gerald I think the restore_lines param in the advance config editor it only honored for 1:1 chats, right? Is there something similar for MUCs?
  31. lovetox no
  32. wurstsalat gerald: this would become obsolete if we had history load on scrolling to the top. But this needs the conversation textview redesign first :)
  33. gerald >history load on scrolling to the top agree, this would be best. >conversation textview redesign first as always, everything is connected :)
  34. gerald also, highlighting quotes is definitely needed, very glad this is on the meta issue you send me yesterday
  35. wurstsalat gerald: missing something on that list? :)
  36. gerald wurstsalat, nope, as I was reading through it, I was nodding constantly, thinking oh yes, nice, yes please.
  37. gerald also, I'm excited for MR !515 Chat Markers :)
  38. gerald re. you'r using the prosody module muc_http_log for this. I've just asked about this in the prosody muc, but didn't get a definte answer: with this module, is every public's muc history exposed via http or is there a more granular setting on a room by room basis?
  39. gerald ^Got the answer in the prosody muc: every publicly listed and not for members-only has it's history exposed via http if you use mod_http_muc_log.
  40. wurstsalat > also, I'm excited for MR !515 Chat Markers :) Yes!
  41. bot Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _gajim_ < >: *8409f5e7* < > Plugins: Fix registering modules on enabling account
  42. gerald wurstsalat, >gerald: missing something on that list? :) I'm not sure if Message/conversation appearance is the right meta list, but it would be nice if one could choose a nick *before* entering a MUC.
  43. lovetox we just removed that
  44. lovetox or no you never could do that actually
  45. lovetox this would disrupt the join process
  46. lovetox hm i guess we could add something to the join dialog, but not sure its worth it
  47. lovetox you can still choose your nick after you join
  48. lovetox and i would argue most people dont use custom nicks for each muc
  49. lovetox so the few that do, i think its fine if they change it after join
  50. gerald >and i would argue most people dont use custom nicks for each muc I'd disagree, I think it's pretty common for public anon. mucs. >disrupt For public mucs that you join via the search.jabbercat menu, you could just add a nickname textfield I imagine.
  51. gerald This only occured to me when I was having another look at Dino, only then I realized that this is a really nice little feature imho
  52. bot Philipp Hörist pushed 2 commits to branch _refs/heads/master_ of _python-nbxmpp_ < >: *ff8e7bb6* < > Determine remote jid correctly in all cases *6a89fcfb* < > Message Properties: Expose from and to attribute
  53. bot Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _gajim_ < >: *13acb5af* < > MAM: Simplify _parse_chat_attrs() This became more simple due to nbxmpp changes
  54. bot Philipp Hörist pushed 2 commits to branch _refs/heads/master_ of _gajim-plugins_ < >: *5ade5cb0* < > [omemo] Adapt to nbxmpp changes Correctly determine session JID after nbxmpp changes *0f9c5aa6* < > [omemo] Update manifest.ini