Project

General

Profile

Feature #7226

Document the "New identity" feature in the browser

Added by BitingBird almost 6 years ago. Updated about 5 years ago.

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

100%

Feature Branch:
doc/7226-torbrowser_new_identity
Type of work:
End-user documentation
Blueprint:
Starter:
No
Affected tool:
Browser

Description

https://tails.boum.org/doc/anonymous_internet/Tor_Browser/index.en.html doesn't mention this option, while many users ask what is does.


Subtasks

Feature #7709: Document browsing clipboard erasure on "New identity"Resolved

Bug #7470: Update warning on new identity now that this feature exists in the browserResolved


Related issues

Related to Tails - Feature #7471: Display a warning notification if the new identity feature is used Rejected 06/29/2014

Associated revisions

Revision 7a662ebc
Added by Tails developers about 5 years ago

Merge remote-tracking branch 'origin/doc/7226-torbrowser_new_identity'

Closes: #7470, #7709, #7226

History

#1 Updated by sajolida almost 6 years ago

Sure. It's not mentioned in the browser doc.

Maybe we could copy the warning from the Vidalia doc:

https://tails.boum.org/doc/anonymous_internet/vidalia/#index4h1

#2 Updated by intrigeri almost 6 years ago

Maybe we could copy the warning from the Vidalia doc:

On the one hand, I'm inclined to trust the Tor Browser's new identity
feature to separate web contextual identities. And I would hate it
to see people think that with TBB, they're safe to use this feature,
while in Tails, they have to bother rebooting. So, copying the
Vidalia's warning feels just wrong.

On the other hand, if we don't want to dive into the complexity of
explaining that this feature only affects web contextual identities,
copying the warning is the right way to go.

I'm torn.

(Note that the web identities are already isolated from the non-web
ones, thanks to our stream separation setup.)

#3 Updated by BitingBird almost 6 years ago

  • Status changed from New to Confirmed

#4 Updated by BitingBird over 5 years ago

  • Status changed from Confirmed to In Progress
  • QA Check set to Ready for QA

#5 Updated by BitingBird over 5 years ago

  • Target version set to Tails_1.2.2
  • Feature Branch set to bitingbird:doc/7226-torbrowser_new_identity

#6 Updated by BitingBird over 5 years ago

  • Assignee set to sajolida

#7 Updated by sajolida over 5 years ago

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed

Thanks for the patch.

First, I had the same Git problems as with #7118. So please do reset your branch in the same way.

Then, it is not clear to me how your patch answer intrigeri's concern from comment #2. You are not refering at all to browser state in your patch (cookies, cache, history, etc.) but merely to Tor connections.

I think that it is good to link to the "new identity" section of the TBB design document but it's pretty hard to read and I'd rather explain what it does to the user in simple terms as well. As we are quite often answering questions about cookies for example, so this is something that people understand and wonder about.

#8 Updated by sajolida over 5 years ago

  • Related to Bug #7470: Update warning on new identity now that this feature exists in the browser added

#9 Updated by sajolida over 5 years ago

Ah, and I also wonder how this relates to #7470.

I'm wondering whether we should move the paragraphs that explain the "New identity" features of Vidalia and Tor Browser respectively to the Vidalia and Tor Browser documentation directly. And then have the warning page point there (instead of having it the other way around).

If you think that this is a good idea, please either do it straight away in this branch or create a ticket about it.

#10 Updated by sajolida over 5 years ago

  • Feature Branch changed from bitingbird:doc/7226-torbrowser_new_identity to doc/7226-torbrowser_new_identity

#11 Updated by anonym over 5 years ago

  • Target version changed from Tails_1.2.2 to Tails_1.2.3

#12 Updated by BitingBird over 5 years ago

Yes, it's probably better to document the "new identity" in the Vidalia and Tor Browser documentation directly. I would like to keep it in the warnings though, but I know that duplicating information is not good, so a link might be good enough. I'll go back to it.

#13 Updated by BitingBird over 5 years ago

  • Related to Feature #7471: Display a warning notification if the new identity feature is used added

#14 Updated by BitingBird about 5 years ago

  • Target version changed from Tails_1.2.3 to Tails_1.3

#15 Updated by BitingBird about 5 years ago

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Dev Needed to Ready for QA
  • Feature Branch changed from doc/7226-torbrowser_new_identity to bitingbird:doc/7226-torbrowser_new_identity

My new commit improves things. It only documents TBB's new identity feature, in the TBB-dedicated doc page.

Vidalia's new identity feature will be documented in vidalia's doc page, see #7470

#16 Updated by BitingBird about 5 years ago

Built the wiki, everything works - i added a commit on top to change "reboot" to "restart Tails". Including the image of the "new identity" feature would be great, but i won't be the one to do it.

#17 Updated by BitingBird about 5 years ago

  • Related to Feature #7709: Document browsing clipboard erasure on "New identity" added

#18 Updated by sajolida about 5 years ago

  • Related to deleted (Feature #7709: Document browsing clipboard erasure on "New identity")

#19 Updated by sajolida about 5 years ago

  • Related to deleted (Bug #7470: Update warning on new identity now that this feature exists in the browser)

#20 Updated by sajolida about 5 years ago

  • Tracker changed from Bug to Feature
  • Assignee changed from sajolida to BitingBird
  • Target version changed from Tails_1.3 to Tails_1.3.2
  • Feature Branch changed from bitingbird:doc/7226-torbrowser_new_identity to doc/7226-torbrowser_new_identity

I pushed fd7437d..06d3f8b on top of that.

That's too much work for me to merge it without you having a lot at the result first. So postponing to 1.3.1, but we're almost there!

#21 Updated by BitingBird about 5 years ago

  • Target version deleted (Tails_1.3.2)
  • QA Check changed from Ready for QA to Pass

I had a look at all your commits. I think you really improved what I did and that would be great to merge.

#22 Updated by Tails about 5 years ago

  • Status changed from In Progress to Resolved

Applied in changeset commit:44b8986096ba4816d20bbd310ecf4cc9f29d853e.

#23 Updated by BitingBird about 5 years ago

  • Target version set to Tails_1.3

Also available in: Atom PDF