[Standards] OMEMO:2 Spec Sprint
chrisballinger at gmail.com
Mon Jan 13 19:34:09 UTC 2020
Neat! I know that OTRv4 uses a similar pre-key mechanism. I'm not sure if
anyone else has looked into supporting OTRv4, but it might be something to
consider if we're going back to the drawing board. In its current form it
requires a separate pre-key server, but it would be great if that
requirement could be eliminated: https://github.com/otrv4/prekey-server-xmpp
On Mon, Jan 13, 2020 at 5:08 AM Paul Schaub <vanitasvitae at fsfe.org> wrote:
> Hi everyone!
> With the current discussions and plans around XEP-0384 being retired
> soon, some of us found it important to come up with a properly specified
> replacement in time.
> That's why there will be an OMEMO:2 Specification Sprint! \o/
> We are going to learn from the mistakes of the old specification and aim
> to create a new iteration which hopefully fixes a lot of little issues
> and addresses the concerns raised by its predecessor. Our primary goal
> is obviously to break the hard dependency on libsignal to allow for
> implementors to use permissively licensed libraries.
> If you like to attend, you should have a pretty good understanding of
> OMEMO in its current form*.
> We are targeting some weekend in the end of February for the Sprint
> which will probably take place in Düsseldorf, Germany. More precise
> details and a Wiki page will follow once we have a venue.
> If you are interested, please let us know by replying to this mail.
> Happy Hacking!
> *: XEP-0384 and how it's implemented in the wild.
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards