[OTR-dev] OTR version 4 Draft #2

[Ola Bini]

Hey,

> > In either case, designing the current API to anticipate one of these
> > compromises would almost certainly be a mistake for these reasons and
> > also the aforementioned complexity issue. Getting OTRv4 out the door and
> > into users' hands soon is far more important.
> 
> Totally agree that getting this finished and into the plugins,
> which will take time, is most important. Maybe it's time to
> prototype libotr-ng integration in pidgin-otr and friends and
> possibly incorporate feedback before the first stable release.

In fact, when we started doing libotr-ng we also started on prototype
pidgin-otr implementation. A first version of libotr-ng worked quite
well from inside of Pidgin - however, things on the spec side have now
raised away and we haven't looked at the Pidgin side for a while. We
do expect to re-initiate that work very soon. We are of course using
these experiences in our thinking around the design of the API for libotr-ng.

Cheers
-- 
 Ola Bini (https://olabini.se)

 "Yields falsehood when quined" yields falsehood when quined.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20180511/0047fad1/attachment-0001.sig>