jdev - 2026-01-28


  1. sunglocto

    What OMEMO version is recommended for implementation?

  2. singpolyma

    depends. What is your goal?

  3. sunglocto

    implementing OMEMO into a client

  4. singpolyma

    But is your goal compatibility with the largest number of other clients? Or some other goal

  5. sunglocto

    yes, compatibility with other clients

  6. singpolyma

    Version 0.3

  7. sunglocto

    of the XEP?

  8. alexkurisu

    > What OMEMO version is recommended for implementation? Both 0.3 and 0.9

  9. sunglocto

    Got it, thanks

  10. wgreenhouse

    0.3 to talk to everything out there now, 0.9 to futureproof

  11. wgreenhouse

    relatedly; for clients doing this now, what's the best heuristic for deciding which to use

  12. higor

    hello

  13. higor

    hello .

  14. devo

    Hello everyone. I’m new to this protocol and I’m using it together with Stanza.io and ejabberd. Could you guide me on a solution to mark messages as read? I’ve already tried XEP-0333, but it didn’t work very well

  15. Link Mauve

    devo, you might want to have a look at XEP-0490, it’s much newer and not supported everywhere yet, but for self-read markers it does what you want.

  16. alexkurisu

    > relatedly; for clients doing this now, what's the best heuristic for deciding which to use Use lowest common denominator?

  17. alexkurisu

    If all parties support 0.9, then use 0.9, otherwise use 0.3

  18. moparisthebest

    how could you possibly tell that

  19. moparisthebest

    you don't know what clients I'm using now, let alone future ones I might use

  20. devo

    Thank you very much. I'll take a look

  21. lovetox

    what is the question? how to decide what to implement or what to use when you add a new contact?

  22. lovetox

    omemo is session based per device, encryption is per device, so you can use omemo1 with one device, omemo2 with another device in the same message

  23. lovetox

    and what to use you see in pubsub, every device announces what it supports