Feature #7348

Improve OTR user experience

Added by Anonymous 2014-05-31 06:50:42 . Updated 2015-01-03 00:22:06 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2014-06-01
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Instant Messaging
Deliverable for:

Description

On https://tails.boum.org/doc/anonymous_internet/pidgin/index.en.html there are two things which are not mentioned neither in the Tails documentation nor in the external doc at security in a box.

1. OTR is not activated by default nor forced.
I think it is worth mentioning this as users tend to think that with Tails they are secure without needing to configure anything.

In Tails the “Private/Unverified” buttons are missing/deactivated. This distinguishes use of Pidgin/OTR in Tails from use on another system and unfortunately also from the documentation at securityinabox.

So, 2. We should mention how to activate OTR on a conversation in Tails (use the menu) or eventually reintroduce that button area that will at least give some visual feedback to the user, green for private, grey for unverified, red for not private.

I understand that this has been deactivated because it might be confusing. But having no feedback at all seems even less appealing to me i have to say.

What do you think?


Subtasks

Feature #7355: Document that OTR is not activated by default Resolved sajolida

0

Feature #7356: Enable formatting toolbars in Pidgin Resolved

100


History

#1 Updated by sajolida 2014-06-01 05:43:09

  • Subject changed from Improve Pidgin/OTR Documentation even more to Improve OTR user experience

I agree with stating in the doc that OTR is not activated by default. That’s Feature #7355 now.

The OTR button appears otherwise in what is called the “Formatting Toolbars”, it has been deactived with commit c4a2668. So I think it’s worth reopening the debate. That’s Feature #7356 now.

Just out of curiosity, is that an outcome of the user testing session?

#2 Updated by Anonymous 2014-06-01 14:02:10

sajolida wrote:
> I agree with stating in the doc that OTR is not activated by default. That’s Feature #7355 now.
Thanks.

> Just out of curiosity, is that an outcome of the user testing session?
No. I realized this while talking with some users on the IRC channel in private.

#3 Updated by BitingBird 2014-06-09 15:22:16

  • Status changed from New to Confirmed

#4 Updated by BitingBird 2015-01-03 00:20:49

  • Category set to 213

#5 Updated by BitingBird 2015-01-03 00:22:06

  • Status changed from Confirmed to Resolved

Both children tickets are resolved, nothing more here -> marking as resolved.