-
sunglocto
What OMEMO version is recommended for implementation?
-
singpolyma
depends. What is your goal?
-
sunglocto
implementing OMEMO into a client
-
singpolyma
But is your goal compatibility with the largest number of other clients? Or some other goal
-
sunglocto
yes, compatibility with other clients
-
singpolyma
Version 0.3
-
sunglocto
of the XEP?
-
alexkurisu
> What OMEMO version is recommended for implementation? Both 0.3 and 0.9
-
sunglocto
Got it, thanks
-
wgreenhouse
0.3 to talk to everything out there now, 0.9 to futureproof
-
wgreenhouse
relatedly; for clients doing this now, what's the best heuristic for deciding which to use
-
higor
hello✎ -
higor
hello . ✏
-
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
-
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.
-
alexkurisu
> relatedly; for clients doing this now, what's the best heuristic for deciding which to use Use lowest common denominator?
-
alexkurisu
If all parties support 0.9, then use 0.9, otherwise use 0.3
-
moparisthebest
how could you possibly tell that
-
moparisthebest
you don't know what clients I'm using now, let alone future ones I might use
-
devo
Thank you very much. I'll take a look
-
lovetox
what is the question? how to decide what to implement or what to use when you add a new contact?
-
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
-
lovetox
and what to use you see in pubsub, every device announces what it supports