I’ll definitely have a look into it. It’s probably all based on the same principles.
The name "OMEMO" is a recursive acronym for "OMEMO Multi-End Message and Object Encryption". 🌀
Multi-end is literally in the name… interesting. Maybe something you can learn here for your spec’ nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc
Discussion
Both Signal and OMEMO use Double Ratchet, so probably!
Imagine if you pull off crafting a hybrid spec combining the best of both on Nostr… Godspeed! 🫡
💯🤙
we will
because it's so simple
nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc
nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8
nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9
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.