5 ms·

And of course most XMPP clients which support OMEMO only support an old version of it, which is incompatible with the new OMEMO version, currently only supporte

by F3nd0 23d ago

And of course most XMPP clients which support OMEMO only support an old version of it, which is incompatible with the new OMEMO version, currently only supported by KDE’s own client—Kaidan. That also happens to be the only desktop client I feel like I’d actually enjoy using (if only I could use it to talk with people not using Kaidan).

jcbrand 23d ago
FWIW Converse.js and Dino also support the latest OMEMO.
- F3nd0 23d ago
  Oh, nice! It looks like Converse.js has added it just two months ago, but I haven’t been able to find anything for Dino (only complaints about as old as the latest release, about the newest OMEMO not being supported). Was it shipped very silently, or are they perhaps planning to add it in an upcoming release?
  - jcbrand 23d ago
    Looks like I might have been wrong about Dino, sorry about that. I worked on adding OMEMO2 support to Converse.js via libomemo.js and I tested it against Kaidan.
goffi 22d ago
Libervia (on which I'm working) does support OMEMO:2 (it was actually the first client to implement it) + legacy one + OX (OpenPGP) + OX for Pubsub (so you can encrypt everything pubsub related: blog, forums, tickets, etc). () Anyway, there is a discovery mechanism, and clients do adapt the version used by peers, so there is no incompatibility. Kaidan choose for a while to have only OMEMO:2, because resources are limited and they were going for the latest version first, but resource are limited for everybody, and it took times for others to implement OMEMO:2 too. NLnet/NGI did (and still does) gave financial support on several XMPP projects (including mine, huge thanks to them), and, curiously, when there is money to help, implementations happen. That's problem nb 1 with XMPP: lack of financial resource. () GUI (notably web UI) is being reworked, not stable yet, but the CLI is pretty solid.

by F3nd0 23d ago

jcbrand 23d ago

FWIW Converse.js and Dino also support the latest OMEMO.

F3nd0 23d ago
Oh, nice! It looks like Converse.js has added it just two months ago, but I haven’t been able to find anything for Dino (only complaints about as old as the latest release, about the newest OMEMO not being supported). Was it shipped very silently, or are they perhaps planning to add it in an upcoming release?
- jcbrand 23d ago
  Looks like I might have been wrong about Dino, sorry about that. I worked on adding OMEMO2 support to Converse.js via libomemo.js and I tested it against Kaidan.

goffi 22d ago

Libervia (on which I'm working) does support OMEMO:2 (it was actually the first client to implement it) + legacy one + OX (OpenPGP) + OX for Pubsub (so you can encrypt everything pubsub related: blog, forums, tickets, etc). () Anyway, there is a discovery mechanism, and clients do adapt the version used by peers, so there is no incompatibility. Kaidan choose for a while to have only OMEMO:2, because resources are limited and they were going for the latest version first, but resource are limited for everybody, and it took times for others to implement OMEMO:2 too. NLnet/NGI did (and still does) gave financial support on several XMPP projects (including mine, huge thanks to them), and, curiously, when there is money to help, implementations happen. That's problem nb 1 with XMPP: lack of financial resource. () GUI (notably web UI) is being reworked, not stable yet, but the CLI is pretty solid.