[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #27103 [Core Tor/Tor]: report initial OR_CONN as the earliest boostrap phases
#27103: report initial OR_CONN as the earliest boostrap phases
-------------------------+-------------------------------------------------
Reporter: | Owner: catalyst
catalyst |
Type: defect | Status: assigned
Priority: Medium | Milestone: Tor: 0.3.5.x-final
Component: Core | Version:
Tor/Tor | Keywords: usability, ux, ux-team, bootstrap,
Severity: Normal | 035-roadmap-subtask, 035-triaged-in-20180711
Actual Points: | Parent ID: #22266
Points: | Reviewer:
Sponsor: |
-------------------------+-------------------------------------------------
We should always make the earliest bootstrap phases be our first
connection to any OR, regardless of whether we already have enough
directory info to start building circuits.
When starting to boostrap with existing directory info, there might not be
a need to make an initial connection to a bridge or fallback directory
server to download directory info. This means that the initial OR_CONN to
a bridge or guard displays on a progress bar as 80%, when in fact a fairly
"early" dependency (the initial connection to any OR) could be failing.
Intuitively, starting Tor Browser and seeing the progress bar hang at 80%
for a very long time is frustrating and misleading. A user who sees the
progress bar hang at at 5% or 10% has a much better idea of what's going
on.
Existing directory info can be reflected in the progress bar as a rapid
jump after the initial OR_CONN succeeds. This seems less likely to
frustrate users.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27103>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs