Opened 8 years ago

Last modified 12 days ago

#5294 new task

Make human summary of Tor Browser design doc

Reported by: mikeperry Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: SponsorO, ux-team
Cc: nickm, runa, adrelanos@…, michael@…, pili, antonela, ggus Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We should create a brief human-readable summary of the privacy properties of TBB, based on the Design Requirements.

We should probably include this in the short user manual, or on the download page, or both.

See also

Child Tickets

Change History (29)

comment:1 Changed 8 years ago by arma

Yes please. This would be great.

comment:2 Changed 8 years ago by mikeperry

The short manual lives in #4983 is the ticket to include it in TBB.

comment:3 Changed 8 years ago by mikeperry

Priority: normalmajor

comment:4 Changed 8 years ago by mikeperry

#5721 also wants us to mention New Identity. Dupping it here.

comment:5 Changed 8 years ago by mikeperry

Component: Firefox Patch IssuesCompany
Owner: mikeperry deleted
Status: newassigned

Taking me off of this. I don't speak human.

comment:6 Changed 8 years ago by arma

Milestone: TorBrowserBundle 2.3.x-stableSponsor Z: March 1, 2013
Status: assignednew

Now that the ticket has fallen into the "important thing that nobody is working on" category, I'm giving it a milestone that will help Karsten keep track of it.

comment:7 Changed 8 years ago by mikeperry

I finally took a look at the TSUM, and I think it has a lot of problems (#5811). We probably need someone dedicated to testing our documentation in front of normal people...

comment:8 Changed 8 years ago by mikeperry

Here's a direct link to the TBB privacy properties that need to be translated from mentat to human:

comment:9 Changed 8 years ago by mikeperry

Parent ID: #5811

comment:10 Changed 8 years ago by nickm

Cc: nickm added

mikeperry: if you can write up (or point to) a summary of attacks in mentat, I think that'd be an easier way to explain why you need TBB than trying to translate its privacy properties per se. Probably, a partial list of attacks could be inferred from the torbutton/tbb design docs. Alternatively, if somebody writes such a list as a set of bullet points, a humanese speaker might be able to expand them.

This would be a good project for somebody who wants to come up to speed on TBB design.

comment:11 Changed 8 years ago by mikeperry

Hrmm.. Well, a root issue here is that most of these "attacks" are actually considered features by other browsers. In particular: the ability to track users across different sites is totally awesome from the perspective of browser makers.

I think we'll have the best results somehow contrasting the cross-site unlinkability properties/goals of TBB ( with the cross-site tracking features provided by other browsers, but at a very very high level.

I think most normal people might actually be pretty ignorant of how Google can for example track their activity across the whole web, not just on Google's sites.

I think specific attacks is of course way too low-level for the output. I think it's even way too low level for the input, because it probably will bias thinking away from simplicity.

Now, in interest of full disclosure, one of the reasons I am not running at this task personally is because I feel slightly guilty communicating these high level ideas to the general public while we still have quite a few known direct violations of them open in our bugtracker:

comment:12 Changed 8 years ago by runa

Cc: runa added

comment:13 Changed 8 years ago by karsten

Keywords: SponsorZ added
Milestone: Sponsor Z: March 1, 2013

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

comment:14 Changed 7 years ago by proper

Cc: adrelanos@… added

Related to #6567: TorButton FAQ outdated

Related to #6563: List of recommended Firefox extensions - time to take it down?

comment:15 Changed 6 years ago by lunar

Keywords: SponsorO added; SponsorZ removed
Parent ID: #5811#10974

This should be part of the introduction of the Tor Browser User Manual.

comment:16 Changed 6 years ago by lunar

Component: CompanyTor bundles/installation

comment:17 Changed 6 years ago by michael

Cc: michael@… added

comment:18 Changed 6 years ago by erinn

Keywords: needs-triage added

comment:19 Changed 6 years ago by erinn

Component: Tor bundles/installationTor Browser
Keywords: needs-triage removed

comment:20 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:21 Changed 6 weeks ago by gk

Cc: pili added
Priority: HighMedium
Summary: Make human summary of TBB design docMake human summary of Tor Browser design doc

I think that's still something that could be useful and included somewhere on our website and once we revive the idea of a short user manual. (Or maybe we could include it into our current user manual)

comment:22 Changed 6 weeks ago by pili

Cc: antonela added

I wonder if this could be something for the OTF Learning Lab... what do you think antonela? I'm thinking of again... :)

comment:23 Changed 6 weeks ago by antonela

When we talked about the Learning Lab scope we fixed it to Onion Services. This is something the UX team can have in their roadmap for 2020 given that we already got :P

comment:24 Changed 6 weeks ago by antonela

Keywords: ux-team added

comment:25 Changed 5 weeks ago by pili

I was thinking about an additional request separate to Onion Services. Great to hear that we have the bandwidth to do it "in-house" ;)

P.S Sounds like a great project for a volunteer...

Last edited 5 weeks ago by pili (previous) (diff)

comment:26 Changed 2 weeks ago by gk

Owner: set to tbb-team
Status: newassigned

comment:27 Changed 2 weeks ago by gk

Status: assignednew

comment:28 Changed 2 weeks ago by gk

Parent ID: #10974

comment:29 Changed 12 days ago by pili

Cc: ggus added

I wonder if this is a session we could brainstorm/crowdsource/test-drive at IFF this year with attendees?

Note: See TracTickets for help on using tickets.