Detect captive portals
Blueprint: https://tails.boum.org/blueprint/detect_captive_portals
Minimal implementation
A minimal implementation would be to adapt the error screen of Tor Connection whenever the user choose autoconnect and time sync fails because there might be a captive portal.
That's Case #2 of #19336.
We should display only the following sections of the error screen, in that order:
- Captive portal
- Proxy
- Bridge
The problem here is that people don't know what bridges are yet.
On Mural I wrote "minor for bridge", but let's try something simpler for now:
- Rename the section "Bridge by email" to "Tor bridge by email" everywhere on all screens.
- Add an explanation about what Tor bridges are (only displayed on this screen).
- Improve the "send an email" sentence.
The section on this screen would be:
Tor bridge by email
Tor bridges are secret Tor relays. Use a bridge as your first Tor relay if connections to Tor are blocked, for example in some countries, by some public networks, or by some parental controls.
To get a bridge, send an empty email to...TODO
- Revert 76a3c527
User research findings
-
During #18762 (closed), 3 participants out of 4 thought that they needed a bridge when captive portal was the actual problem. P4 commented:
What I find interesting is that it’s not saying what the error is. And so it’s more difficult to know how to solve it. thought it was the bridge and I solved that.
Flow chart
