Replies (24)

I can send OMEMO messages between XMPP and IRC. But that's besides the point. My comment about having one standard was about not having one for DM's and another for group chats, when everyone is using only one (because group chats serves for DM's).
I am not sure if it's possible (or desirable). Usually there are specific features (or simplifications) on each of them to warn a separate protocol. For instance, if you are doing a private zap, you want the amount to be public and the rest private, which creates metadata leaks on purpose. Sometimes, "leaks" are desirable. In other times they must be forbidden. But who knows, maybe there is a way to merge them all.
OMEMO is pretty cool. How does OMEMO accomplish syncing between user devices? @JeffG @jb55 According to Straub, OMEMO uses the Double Ratchet Algorithm "to provide multi-end to multi-end encryption, allowing messages to be synchronized securely across multiple clients, even if some of them are offline" Bold claims. Sounds like exactly what we need… πŸ€” image
In the two minutes look I just took at Omemo, it looks like it’s using the same principles that signal and my NIP are using. I’d be willing to bet the device syncing is the same. In any case. I’ll definitely take what i can from it. Fwiw; group messaging is doable with this basic system as well.
@JeffG @DETERMINISTIC OPTIMISM 🌞 @Colby Serpa Reading this thread has been illuminating: https://old.reddit.com/r/signal/comments/10edi7b/signal_encryption_vs_xmpp_omemo/ To sum it up: 1. OMEMO is essentially Signal's encryption protocol (and it is web, thanks to movim folks). 2. The rest of the Signal protocol is snake oil. 3. Anonymization should be worked on a different layer. For point three I have a solution in mind that would like to discuss with anyone interested in funding the project.
↑