[guardian-dev] OTR4j and OTRv3

[Eleanor Saitta]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2013.01.10 04.39, Nathan of Guardian wrote:
> On 01/10/2013 10:18 AM, Chris Ballinger wrote:
>> After helping someone write a wrapper for libavcodec using the
>> NDK I think it isn't that difficult to do the bridging, but (if
>> i'm not mistaken) there
> It isn't so much a question of using the NDK or not, as we are
> already fairly committed there with SQLCipher, Tor, GnuPG, etc.
> 
> I am more asking is it a healthy thing to have two OTR efforts
> working parallel with libotr as the lead, and OTR4J always playing
> catch-up, or should we commit to bringing and utilizing libotr to
> Android? Should all the crypto-chat clients in the world be based
> on the same OTR library, or should we encourage diversity?

IMNSHO, having two implementations *greatly* improves correctness in
both of them.  Also, as folks have mentioned, there are other users of
OTR4J who we (OpenITP) would like to see brought forward too.  While
there are things that the other projects (Jitsi, primarily) will also
need to do, having the library support finished will make it much
easier to convince those projects to do the work.

E.

- -- 
Ideas are my favorite toys.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iF4EAREIAAYFAlDu2+sACgkQQwkE2RkM0wrQFAD/X2M65w2nF6Apfuldj8n8LycI
a0O0pRiblZCYRVb8SiYA/jMSyZQsvs63hu8jngIgfmrTk6qZSkUP/Bd2H/ftNdLx
=kl6f
-----END PGP SIGNATURE-----