Modern XMPP project discussion - 2020-02-21

  1. DebXWoody

    Hello. What is the plan to solve the OMEMO 12/16 problem? Will the clients move to "12-sending"?

  2. Zash

    I'd feel like OMEMO crypto details are out of scope for this

  3. Daniel

    DebXWoody, everything you need to know is in this thread: https://nitter.net/iNPUTmice/status/1228950491805167617

  4. DebXWoody

    As far as I understood, Monal is not wrong, unfortunately he didn't implement the old solution. Maybe not the best idea. Anyway, there is an issue with impacts the system and we should try to solve it. A) Ask Anu to support read of old format. B) Inform the community about the issue (I think the most people knows, but not the users). C) Maybe a list of Clients which is sending 12 to keep track on it.

  5. Daniel

    I think the community is sufficiently informed. But desktop programs don't role out over night

  6. emus

    Anu is limited to the libaries he is using as I understood

  7. Daniel

    DebXWoody: the tldr is: it's going to be fine. Don't worry about it

  8. DebXWoody

    👍😉

  9. MattJ

    Zash: I don't think it's out of scope... aiming to document everything that is useful to XMPP devs

  10. MattJ

    Though I feel the XEP is ultimately the best place for such essential interop details...

  11. Zash

    Mmmmhm

  12. vanitasvitae

    > DebXWoody: the tldr is: it's going to be fine. Don't worry about it Famous last words :P

  13. MattJ

    :)

  14. Neustradamus

    DebXWoody: https://twitter.com/search?f=tweets&vertical=default&q=omemo12byteiv -> Monal, Conversations, Converse.js, JSXC, Gajim, Profanity, Psi/Psi+, python-omemo, Smack, Tigase Siskin IM, Tigase Beagle IM have already good OMEMO.

  15. Ge0rG

    Neustradamus: 16 bytes was good, 12 bytes is better. 0 bytes is best!

  16. Zash

    Why not -i bytes?

  17. DebXWoody

    Neustradamus: Thanks. As Daniel said, one thing is to provider the fix, but the other is to deliver it 🙄