Hi,
I don't have the entire problem space in mind, so here are just my
2cts, on a tiny part of it:
anonym wrote (27 May 2015 15:31:01 GMT) :
> I just realized that we may need to modify this page even if we do 1. If
> we are on a network with a captive portal, start the Tor Browser despite
> the warning that Tor isn't ready, and then enter the URL of our favorite
> non-LAN web site, e.g. http://www.asdf.com, then we will still get the
> "Unable to connect" page, but for a completely different reason, namely
> that Tor was blocked from creating a circuit.
> So, perhaps we should skip 1 and instead focus on a complete rewrite of
> the "Unable to connect" page for all cases, and try to make it stand out
> so users will not ignore it. Perhaps it would help if we changed the
> header to "The Tor Browser was unable to connect", which is a bit less
> generic; hopefully the words "Tor Browser" will be less easy to ignore.
> And perhaps it could show the Tor onion (like in about:tor).
> On this new page we would mention all common reasons for us getting
> here, e.g.:
> * Captive portal. In Tails we would also refer to the Unsafe Browser for
> dealing with captive portals. Actually this whole bullet is only
> relevant in Tails since "normal" Tor Browser users wouldn't even get
> here since Tor Launcher would fail.
Maybe cases when Tor fails to bootstrap (captive portal, Tor being
blocked in some way => need PT, etc.) would be better addressed by
#7437: ideally, the user should not need to start Tor Browser and read
a generic error page to learn about a Tor bootstrap failure.
Cheers,
--
intrigeri
