[OTR-dev] OTR support for Gajim

Kjell Braden kb at pentabarf.de
Mon Aug 22 07:59:47 EDT 2011

On 08/19/2011 11:30 PM, Aaron Toponce wrote:
> On Thu, Aug 18, 2011 at 10:09:00PM +0200, Jonathan Schleifer wrote:
>> I was the one removing OTR. I spent a lot of time to get it working properly, but that's not really possible if you are forced to parse strings containing HTML that are even localized to see if an error happened…
> I hope you don't think I was criticizing your code, or attacking you in any
> way. I appear to come off that way on mailing lists. I was just curious
> what it would take, in the long shot, to get it working. It appears that
> 0.15 will support plugins, and a plugin is ready, or getting ready, to go
> live with it.
> --
> . o .   o . o   . . o   o . .   . o .
> . . o   . o o   o . o   . o o   . . o
> o o o   . o .   . o o   o o .   o o o
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev


 being the one who was working on gajim-otr, I think I need to clarify
one or another point here:

 First: the libotr itself is not bad. I found that working with it can
be really easy. The worst (and the IMHO only really critical, though js
may disagree here) problem was that can't implement callbacks for the
libotr in python. You can, but you have to deal with python-exceptions,
and the libotr callbacks must not fail. I used abort() for that matter,
which was probably not my best idea. ;-)

 Mostly for that project I built the python-otr bindings (ie. a python
interface to the libotr), which was mostly a 1:1 mapping to the libotr
api and therefore not quite what you like to use in python. For that
reason, gajim-otr was pretty much unusable and was abandoned. Few
months ago I had some time left and created a pure python implementation
of the otr protocol (this means, its not the libotr, but it is
compatible in what it does) [1]. It works, but hasn't received much
testing. I have a working gajim plugin but currently don't really have
the time to release it for beta.

On 08/18/2011 02:42 PM, Sven Moritz Hallberg wrote:
> overall, to my gut it sounds i bit
> like he expected a three-line drop-in that would just magically work for
> the developer. and you're just not going to get that if the software
> you're talking about is security software that is trying hard to
> automagically work for the *user*.

 I have no idea what your gut read or saw about that story, but it
definitely had nothing to do with three-line drop-ins.

[1] http://lists.cypherpunks.ca/pipermail/otr-dev/2011-May/001174.html


More information about the OTR-dev mailing list