That's great! Please let me know if you're having any problems or
questions with the implementation in Jitsi.
I've already got it working for a week or so. No problems there. I've
just been testing and defining the operation set necessary for querying
the necessary information about the IM protocol. Also, I've been playing
around with it using different clients to see whether there would be any
problems, but so far it looks pretty good.
Just to let you know, there is at least one known problem on the Jitsi
side of the implementation where the toolbar icon looses track of the
actual otr4j session status and so it displays the wrong icon and
executes the wrong actions. Don't get confused by that, it's not a
problem introduced by your changes.
Hmmm... I can't recall seeing anything like that. I'll keep an eye out
in case I encounter this issue.
Also, you're a Jitsi dev now, and as we have discussed this previously
on the list, please feel free to push your changes, no code review
required At least I don't see it necessary.
Okay, sure. Just wanted to make sure that you're aware I'm fiddling with
your privacy thingies
On 09/30/2014 10:17 AM, George Politis wrote:
On 29/09/2014 21:49, Danny van Heumen wrote:
I have pushed fragmentation support for outgoing messages to
github.com/jitsi/otr4j and I have the changes for Jitsi ready at
Is it okay to just build the libraries and update them in Jitsi or does
someone want to have a look at the code first? (Given that it's OTR and
There were some other changes to otr4j too. I have correct the API
interface changes as George already pointed out to me.