Gajim - 2017-10-22

  1. erik I used the whiteboard. However, I was missing the ability to draw on my screen, meaning I had to draw/write with my mouse. That doesn't work for me. I've thought about buying a pen device for it. So far didn't find anything which looked like it would work.
  2. erik I'm running into these exact problems with MS's Lync application. The reason to look for the pen device is that we have a "Surface Hub" at work with pens. That works great with the Lync/Skype whiteboard.
  3. Link Mauve erik, sounds like a missing touch or tablet support, were you on master or on the latest stable?
  4. Link Mauve I know GTK+ only got tablet support recently, but touch was around 3.0.
  5. erik Link Mauve, I'm on nightly. But the missing touch support is in my laptop :-)
  6. erik I was just providing feedback on the questions regarding the whiteboard.
  7. Link Mauve Recently as of last year:
  8. erik it's useful, but even more so when you have pen/touch support.
  9. Link Mauve I don’t think anyone had pens or touchscreens back when this plugin got written.
  10. erik yea. But using a digital whiteboard to a useful extent without pen or touch, you need an exceptional level of mouse control
  11. Link Mauve I’m not saying it shouldn’t be done, I’m just explaining why it’s the way it is.
  12. Link Mauve And back then, on MSN, people were using the mouse just fine.
  13. lovetox erik, Link Mauve: the way i see it its possible, the current plugin just catches mouse events
  14. lovetox someone would have to add catching touch events
  15. lovetox which is a own event class in gtk3
  16. Link Mauve lovetox, note that touch and pens are totally different.
  17. lovetox how?
  18. lovetox you think gtk knows when i use a pen to touch the display or the fingerß
  19. lovetox you think gtk knows when i use a pen to touch the display or the fingerß
  20. lovetox you think gtk knows when i use a pen to touch the display or the finger?
  21. Link Mauve Tablet devices generally have a lot of different modes, they handle pressure, eraser mode, shape, and a lot of different things.
  22. Link Mauve The article I linked highlights some of them.
  23. Link Mauve And explains why there is a different API.
  24. ahemlockslie Am I correct that the latest implementation of XEP-0313 Message Archive Management is 0.3?
  25. lovetox no
  26. lovetox
  27. lovetox gajim master branch supports mam:2
  28. lovetox gajim 0.16.8 support mam:1 and below
  29. lovetox gajim master, also supports mam:2 and below
  30. ahemlockslie Sounds like I need to switch to master, then...
  31. lovetox on what system are you?
  32. lovetox we have packages on Arch and Debian testing/unstable
  33. debacle For Debian: 0.16.8 in testing/unstable, master in experimental.
  34. lovetox ups then i wrote that wrong
  35. lovetox in the readme
  36. lovetox ah no, its the correct link to experimental
  37. lovetox but you told me it works also in testing and unstable
  38. concerto lovetox: I removed Acronyms Expander and Gajim seems to be working again.
  39. concerto (Well, I removed Clickable Nicknames too. On the off chance there was some interaction.)
  40. debacle lovetox: yes, I'm on Debian testing and Gajim master works on this (so it should also work on unstable). master is not yet as smooth as Gajim 0.16.8.
  41. lovetox whats not smooth?
  42. bot Philipp Hörist pushed 5 commits to branch _refs/heads/master_ of _gajim_ <>: *0aa07522* <> Logger: Refactor get_jid_id() - Cache jid_id so we save on DB querys *1c736922* <> MUC: Save last message time after each message *accef11c* <> Logger: Get rid of old jids list Use _jid_ids dict instead *b95759df* <> Logger: Refactor insert_jid() - make it use get_jid_id() and return the jid_id *398ad0ee* <> Fix removing avatar sha from DB the account name was passed instead of the account jid
  43. lovetox Link Mauve, with stanza-ids, do i have to validate the by attr to be my server
  44. lovetox is this in anyway security relevant?
  45. lovetox i think the server should take care that no entity adds a stanza-id element to the message
  46. lovetox and i validate that the MAM Message for ex. comes from my server anyway
  47. Link Mauve Yes, it is.
  48. lovetox ah there could be potentially more then one stanza id?
  49. Link Mauve The server should remove them.
  50. lovetox ony if the by attr matches the server
  51. Link Mauve Oh btw, you can only be certain that it’s your server doing it if it supports mam :2.
  52. lovetox otherwise it can leave them
  53. Link Mauve Yeah.
  54. lovetox i just read that i have to check for urn:xmpp:sid:0
  55. Link Mauve MAM :2 guarantees your server knows about sid :0.
  56. lovetox hm deduplication only needed with MAM
  57. lovetox i guess its enough to check for mam namespace yeah
  58. lovetox also with normal muc history, but i try to switch to mam for that anyway
  59. Link Mauve When you know the MUC supports MAM, you can safely ask for zero stanza and query it yourself, it’s a lot more flexible.
  60. lovetox of course, just that this needs me to disco the muc before i join it
  61. lovetox because muc history can not be retrieved after join
  62. lovetox this in turn makes auto joining room at startup more traffic heavy, and slower
  63. lovetox ..
  64. Link Mauve I’d say it’s actually faster if you don’t ask for any history.
  65. Link Mauve That way you only get the presences and the subject.
  66. Link Mauve And Gajim can be reactive (that is, joined) much faster.
  67. lovetox i compared it to never get history if muc is not available
  68. lovetox but i guess i will do the disco thing, in the long run this is probably wise anyway to know of the caps of the room
  69. Link Mauve Yeah.
  70. Link Mauve That’s also what I plan to do in poezio, once we finally have a MAM UI.
  71. bot Philipp Hörist pushed 2 commits to branch _refs/heads/master_ of _python-nbxmpp_ <>: *3275b1fd* <> Update .gitignore *3417ccbf* <> Add getStanzaIDAttrs() method