jdev - 2021-12-01

  1. edhelas

    Wow fun

  2. edhelas

    Telegram is synchronising "in redaction" messages

  3. edhelas

    Basically i started to type a message on my phone and saw it appearing on desktop. So basically they sync up a draft.

  4. Ge0rG

    That's actually quite a nice UX.

  5. Ge0rG

    I've had that situation multiple times, that I wanted to send a message from the PC enriched with a link from my phone, or to switch typing in the middle of things because typing on the PC is so much easier

  6. edhelas

    I'm wondering how this could be replicated on XMPP šŸ¤”

  7. edhelas

    I can actually sync it in Movim easily between the different tabs :p

  8. Ge0rG

    edhelas: write a XEP to send message drafts as a custom element in the <message> to your own JID, implement it together with XEP-0352 to prevent constant flooding on each typed letter

  9. edhelas

    why not use a pep node and store draft messages there :p

  10. edhelas

    with itemid = JID of the future receiver

  11. Link Mauve

    Implement XEP-0301!

  12. Martin

    > I'm wondering how this could be replicated on XMPP šŸ¤” Maybe stuff from RTT could be reused. Afair Dino has something.

  13. Ge0rG

    <message from="georg@yax.im/desktop" to="georg@yax.im"> <draft xmlns="urn:xmpp:message-draft" to="jdev@muc.xmpp.org"> I was thinking abo </draft> </message>

  14. Ge0rG

    edhelas: the big challenge is how to E2EE your drafts

  15. Martin

    Multi-Device Support to sync input between different instances of Dino. With this, a user can start composing a message on one device and finish on another. (Details, see here) https://wolfieanmol.github.io/gsoc-blog/support-for-multiple-devices-muc/

  16. Ge0rG

    Sending RTTs to the MUC might not be such a wise idea

  17. pep.

    Ge0rG, how e2ee your drafts? At first glance I don't see this particularly hard

  18. Link Mauve

    pep., one issue could be that as you know a former draft is very likely to be a prefix of a latter one, it could weaken the encryption.

  19. pep.

    With OMEMO you're not sending to yourself (the same device) so that's fine. If you send to your own jid you might want to include in clear that it's a draft, or not even since you'd be able to know with the id that it comes from you..

  20. pep.


  21. Link Mauve

    The more the attacker knows about your plain text, the more your encryption could be vulnerable.

  22. Link Mauve

    Although Iā€™m not aware of any such issue in current algorithms.

  23. pulkomandy

    If you append some salt to the draft before encryption, you can easily make sure it's not a strict prefix

  24. pulkomandy

    Maybe even better to prepend some salt?

  25. pep.

    There is an rpad element in SCE already. If oldmemo is used maybe it can be specified where to put that pad (and that's where I bail out, don't know much about that)

  26. Zash

    Nice things only being available if you move forward might help push forward nice things?

  27. pep.

    The endless loop of going forward(tm)

  28. Zash

    Something something wheels and turning.

  29. lovetox

    bitlbee code comment about caps in presence

  30. lovetox

    it doesnt send the hash attr

  31. lovetox

    /* The XEP wants this hashed, but nobody's doing that. */

  32. lovetox

    i think they didnt really get what the xep was about

  33. lovetox

    ok so i get it they didnt want to hash their disco info, because it was too much work

  34. lovetox

    now they put in just the client version so ver=3.6.1

  35. Zash

    How old is that line?

  36. lovetox

    but obviously this is not sha-1 hash

  37. lovetox

    so they dont add the hash attr

  38. Zash

    Very very very old things don't

  39. lovetox

    would it still be an improvement if we add hash=sha-1?

  40. lovetox

    if they only change disco features between released versions, this would still work

  41. lovetox

    no it would not for gajim, as it hashes the disco info itself and would report it if it does not is the same

  42. lovetox

    ... so i still get a warning in logs

  43. Zash


  44. Zash

    Huh, this was only done in 2007?

  45. Zash

    And then we have https://xmpp.org/extensions/xep-0390.html