[OTR-users] Pidgin-OTR Logging Behaviour

[Byrd, Brendan]

Hence, we should be careful on our wording.

––
Brendan Byrd <byrd.b at insightcom.com<mailto:byrd.b at insightcom.com>>
System Integration Analyst (NOC Web Developer)

From: otr-users-bounces at lists.cypherpunks.ca [mailto:otr-users-bounces at lists.cypherpunks.ca] On Behalf Of Ben Bridts
Sent: Thursday, February 02, 2012 4:27 AM
To: Rob Smits
Cc: OTR-users at lists.cypherpunks.ca
Subject: Re: [OTR-users] Pidgin-OTR Logging Behaviour

On Wed, Feb 1, 2012 at 16:57, Rob Smits <rdfsmits at cs.uwaterloo.ca<mailto:rdfsmits at cs.uwaterloo.ca>> wrote:
Here are some possible changes:
-Keep current default behaviour, but always output a message like the following when an OTR conversation is started:  This conversation is being saved/not being saved (depending on current settings).
-Change current default behaviour to explicitly disable logging for OTR conversations, and output the above message.
-When an OTR conversation starts, explicitly ask the user whether they wish to log OTR conversations (if no Pidgin-OTR logging preference is found), and perhaps output the above message. Once the user provides an answer, future OTR conversations will not trigger this prompt.
I don't think outputting a message like "this conversation is not being saved" is a good idea, because it gives a false sense of security. We don't know the client that is used by the chat partner and whether he is logging the conversation or not.
Saying it is not logged would make a lot of people assume that it isn't logged anywhere, not that it isn't logged on their PC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20120202/1fcf6944/attachment.html>