Something I've noticed that's happened over a few Jitsi version
is that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we
go away for a little while then come back, the session will still
show as OTR encrypted but typing messages gives the message
"You've sent me an unreadable encrypted message".
Refreshing the conversation seems to fix it.
Show I report this as a bug or is this expected behavior?
I'm not 100% sure, please correct me. I think it's kind of
expected behaviour unfortunately. I would guess it's part of otr4j
(or libotr) because it's the same with all clients using OTR.
That may explain why it happens in multiple clients like another
poster suggested. I think both Jitsi and Pidgin (as well as others)
use libotr or some variant of it. Makes sense.
So when your active chat session expires or is quit by one
participent, the OTR session has to be reestablished. It has
nothing to do with jitsi in particular. What _can_ be done is the
notification about recieving a message that cannot be read: I'd
notify just like an incoming message plus suggesting to reestablish
the otr session with one click if not doing it automatically.
In fact, I believe that this is the behavior that happens with Jitsi.
When you type a message and the session has expired, it is (usually)
automatically reestablished. But not always. Sometimes, you have to
manually re-establish the connection. Not a big deal in and of itself
but one of those 'nice to haves'.
Especially important on mobile, where it shouldn't happen that
someone sends messages to me and my client knows about it, but
doesn't even notify me, just because the otr session has expired
On 08/05/2013 07:04 AM, Martin Kepplinger wrote: