erebionThunderbird devs looking for an OMEMO library: https://bugzilla.mozilla.org/show_bug.cgi?id=1237416
I guess helpful comments will be appreciated. If anyone has a suggestion, I can add it to the issue.
genofire
Nivex 🐧 📻@genofire @erebion I saw this posted last night: https://www.poberezkin.com/posts/2025-08-12-mls-the-naked-king-of-end-to-end-encryption.html - Could be that MLS may not be the way to go?
@nivex @erebion hmm for me the post is from a person, which believe everything else is bad and develop a new Messanger (SimpleX) instatt of extend improve an existing one.
He has some good point, but the main point is not called: Interoperability, this RFC of the MIMI Working-Group is a standard which is designed to work over Messenging-Systems.
It would be fantastic if i could send Messages e.g. from Matrix to XMPP-Users or Signal ...
If we still use different E2EE for every Messenging-System (OMEMO, OLM, OTR, GPG, SMIME <- yes most based all on Signal-Protocoll but it is not standardized) we would stay in a vendor-lock (or breaking E2EE an Transports / Bridges between Messenging-Systems) ....
He has some good point, but the main point is not called: Interoperability, this RFC of the MIMI Working-Group is a standard which is designed to work over Messenging-Systems.
It would be fantastic if i could send Messages e.g. from Matrix to XMPP-Users or Signal ...
If we still use different E2EE for every Messenging-System (OMEMO, OLM, OTR, GPG, SMIME <- yes most based all on Signal-Protocoll but it is not standardized) we would stay in a vendor-lock (or breaking E2EE an Transports / Bridges between Messenging-Systems) ....
XMPP Brasil
monal-im.org 
@xmppbrasil @genofire @erebion one step at a time would mean to implement mam (xep-0313?), carbons, xep-0198, xep-0333, xep-0184 before implementing onemo. And then probably also implement sasl2 (xep-0388) + ssdp (xep-0474).