#28018: Improve accuracy and usefulness of information reported to controllers
about bootstrap status
--------------------------+------------------------------------
Reporter: nickm | Owner: catalyst
Type: enhancement | Status: assigned
Priority: High | Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor: Sponsor8-must
--------------------------+------------------------------------
Comment (by mcs):
For #27239, I reviewed the child tickets of this ticket and thought about
how Tor Launcher / Tor Browser will be affected. I added a few comments
in other tickets, in some cases asking for clarification about what is
planned. I have a few general comments:
Overall, the direction the Network Team has taken should bring some nice
improvements to Tor Browser users. Some of the tor changes seem to require
a lot of work, and I appreciate the effort that is being put into all of
this.
I already mentioned this briefly in ticket:22266#comment:26, but I want to
also mention it here: tor itself should try to provide status and error
information in a UI-agnostic way. What I mean by that is that tor should
support many kinds of status and error reporting interfaces and not lock
clients into a particular way of doing things. For example, for Tor
Launcher we might implement what is proposed in #23971 (a multi-step
progress bar that includes clearly delineated phases). Or we might build
something that looks more like a series of checkmarks (one for each
bootstrap phase) with some kind of intermediate progress display. But
someone else might want to build something completely different.
Another issue that is related to improved bootstrap status reporting is
improved error reporting. Do we have a ticket or set of tasks that cover
that area? Maybe adding more phases will be enough, but there may be more
that should be done. For example, being able to tell users exactly where a
failure occurred would be very helpful; currently, it is difficult to
distinguish local network problems from a PT problem from a wider Tor
network problem.
We are looking forward to making whatever changes are needed in to Tor
Launcher / Tor Browser to accommodate the improvements. As you proceed,
please help us by being clear about what has changed (hopefully control
spec updates will be sufficient to communicate the changes).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28018#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
