Opened 4 years ago

Last modified 4 months ago

#11071 new enhancement

Change PT type dropdown to "China" and "Other"

Reported by: mikeperry Owned by: brade
Priority: High Milestone:
Component: Applications/Tor Launcher Version:
Severity: Blocker Keywords: tbb-usability, ux-team
Cc: mcs, arma Actual Points:
Parent ID: #11180 Points:
Reviewer: Sponsor:

Description

At the dev meeting, we discussed making both BridgeDB and Tor Launcher maintain a table of country to disallowed PT types. Right now, we only have one country that blocks PTs based on DPI of their transport format: China. They only do this with vanilla bridges and obfs2 at the moment.

The idea is if the user seltects "China", Tor Launcher will pick a PT type at random from everything but the types that "China" excludes, and use default bridges from that type from then on. For "Other", it would select a type from all types, with no exclusions.

Unfortunately, this is tricky because we still want to expose the selected PT type so the user can at least easily click on a bridgedb link for that type. It is also tricky in that we probably need to localize the country names, as well as "Other".

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by mcs

Cc: mcs added

comment:2 Changed 4 years ago by mikeperry

This approach does have the downside that if DPI appears, the user will be unable to change their PT type from the one Tor Launcher chose..

Perhaps this is a suboptimal solution then.. Unless we solve #11069 and change the bootstrap fallback UI to allow a type selection, or to automatically try a new type.

comment:3 Changed 4 years ago by mikeperry

Cc: arma added

You know, instead of all of this complexity, we can still just add a different set of PT types and default bridges to only the zh-CN bundles, since that is the only one that differs in terms of PT type availability at the moment. We deliberately designed #10418 for that to be both possible and easy to do.

comment:4 in reply to:  3 Changed 4 years ago by arma

Replying to mikeperry:

instead of all of this complexity, we can still just add a different set of PT types and default bridges to only the zh-CN bundles, since that is the only one that differs in terms of PT type availability at the moment.

I don't mean to be ornery, and I haven't followed all the discussions here so please carry on without me, but I should point out that "is using the Chinese-language bundle" overlaps only somewhat with "is in China". I've heard from many users who avoid the translated Tor bundles because the translations sometimes mangle complex phrases beyond recognition (remember the classic espanol "throw out the cakes when you leave" for "discard cookies on exit"?)

comment:5 in reply to:  description Changed 4 years ago by asn

Replying to mikeperry:

At the dev meeting, we discussed making both BridgeDB and Tor Launcher maintain a table of country to disallowed PT types. Right now, we only have one country that blocks PTs based on DPI of their transport format: China. They only do this with vanilla bridges and obfs2 at the moment.

The idea is if the user seltects "China", Tor Launcher will pick a PT type at random from everything but the types that "China" excludes, and use default bridges from that type from then on. For "Other", it would select a type from all types, with no exclusions.

Unfortunately, this is tricky because we still want to expose the selected PT type so the user can at least easily click on a bridgedb link for that type. It is also tricky in that we probably need to localize the country names, as well as "Other".

With regards to the bridgedb link, I think that TBB should suggest BridgeDB URLs to users. For example, for Chinese users it will point them to the page with obfs3 bridges, whereas for 'Other' it will send them to a more general page. The user shouldn't really understand the URL schema anyway.

If we want to avoid exposing transports to users at all costs, we can customize BridgeDB so that it supports country-specific URLs: https://bridges.torproject.org/china .

comment:6 Changed 4 years ago by mikeperry

Parent ID: #11180

comment:7 Changed 4 months ago by linda

Severity: Blocker

We're discussing this on #23261

comment:8 Changed 4 months ago by cypherpunks

Keywords: ux-team added
Note: See TracTickets for help on using tickets.