You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I got it right, this plugin indicate that OTR is used by adding stars (*) around the username of the other party in the chat window. While the python OTR plugin available from https://github.com/SpiralP/HexChat-otr indicate active OTR by adding [OTR] in front of the username. I find the [OTR] flag easier to understand than the nick flag. Would it be interesting to change the way active OTR is flagged in this plugin?
The text was updated successfully, but these errors were encountered:
Whether or not the suggestion is adopted, I feel that sent/outgoing messages should also be flagged as secure similar to incoming/received messages. It isn't always completely clear whether sent/outgoing messages are secure/encrypted, such as after key generation begins, but before it finishes. Currently, one must pay close attention to the "gone secure" and other similar messages.
In addition to showing whether a chat is encrypted (OTR active) it's also necessary to show whether the other party is verified with a trusted key. A secure man-in-the-middled chat is not where we want to be.
Hi.
If I got it right, this plugin indicate that OTR is used by adding stars (*) around the username of the other party in the chat window. While the python OTR plugin available from https://github.com/SpiralP/HexChat-otr indicate active OTR by adding [OTR] in front of the username. I find the [OTR] flag easier to understand than the nick flag. Would it be interesting to change the way active OTR is flagged in this plugin?
The text was updated successfully, but these errors were encountered: