> This requires huge changes in all OMEMO implementations, and there are > quite few already: https://omemo.top >
I count 4 implementations in an incomplete list of 40 clients. As far as I understand, clients already need to fork and patch libsignal to be compliant with OMEMO anyway. 3DH takes 4 lines of code (you can make it a one-liner if you want to), so that doesn't sound too bad? so I'm expecting independent implementations of the protocol pretty soon. > I would think the list of people interested in an open E2E chat protocol is limited, and one of them already has its own implementation. > there is no Olm library for java at the moment, so again there is a missing implementation. If OMEMO is a succesful, implementable protocol (instead of a wrapper around a library that only a very limited number of people can use), the argument of 'there is no code for this' will quickly be outdated. thanks, Remko
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
