[OTR-dev] Conversion of unencrypted messages to system-messages
michael_zanetti at gmx.net
Sun Feb 21 18:08:30 EST 2010
its me again. I decided to divide my requests into different mails to keep the
The current implementation of kopete's otr plugin uses a message type called
"Internal" to display messages generated in display_otr_message(). Those
internal messages fit perfectly into Kopetes design, indicating encryption
state changes and other notifications of the lib to the user in a way that
they do not disturb the user but are definetly noticed. Such messages (also
used for other types of notifications like online status changes) do neither
produce system notification events nor get logged in chat history.
The problem now is, that incoming unencrypted messages during an established
otr session are transformed into such messages because they are delivered
using display_otr_message(). This leaves kopete users often in the situation
that they do not notice such incoming messages or loose them in chat
Could you think of a way to change that in future versions of libotr to keep
the actual message as a normal message but informing the user in some other
way of the unencrypted state of this message? Perhaps just leave it as a
normal message, but prepend the usual warning. Or maybe better, split the
warning message and the actual message into two, leaving the warning as an
internal message, but delivering the actual message as a normal one?
This is one example bug-report I get for this issue:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the OTR-dev