Opened 15 months ago

Last modified 6 months ago

#27691 new enhancement

reset bootstrap progress when enough things change

Reported by: catalyst Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: usability, ux, ux-team, bootstrap, bootstrap-arch, network-team-roadmap-2019-Q1Q2, ex-sponsor19, ex-28018-child
Cc: brade, mcs, antonela, isabela, iry, intrigeri, torproject@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now, setting DisableNetwork=1 doesn't reset the bootstrap progress indicator. It probably should, because all network connections to bridges or relays will close. This will improve the user experience once we have #27103 in place, because then the earlier progress shown will be the initial network connection that everything else depends on.

We probably also want to reset the bootstrap progress when a configuration change causes us to disconnect from all our guards.

Child Tickets

Change History (16)

comment:1 Changed 15 months ago by catalyst

Upon reviewing the comments in #22266 some more, it seems like users may be upset by seeing progress reset to zero after making a configuration change.

I think it's an accurate reflection of what's going on. Going to the config dialog sets DisableNetwork=1 and tears down the circuits and TCP connections, which have to be set up again.

Maybe if there's additional UI in Tor Launcher to show the existence of cached directory info, that will make it less likely for users to be frustrated by apparently negative progress? That's a longer term change, though.

comment:2 in reply to:  1 Changed 15 months ago by mcs

Cc: antonela added; linda removed

Replying to catalyst:

Upon reviewing the comments in #22266 some more, it seems like users may be upset by seeing progress reset to zero after making a configuration change.

I think it's an accurate reflection of what's going on. Going to the config dialog sets DisableNetwork=1 and tears down the circuits and TCP connections, which have to be set up again.

I think the progress displayed by Tor Launcher should be an accurate reflection of the internal tor state. If that means resetting to zero, so be it. That said, the nature of the network is that sometimes progress occurs more quickly than at other times, which can be confusing. For example, if someone makes a configuration change in the hope of improving things but progress is slower than before due to other factors the user may incorrectly conclude that the new configuration is worse. I am not sure how to address that though.

Maybe if there's additional UI in Tor Launcher to show the existence of cached directory info, that will make it less likely for users to be frustrated by apparently negative progress? That's a longer term change, though.

Agreed; exposing more details about what is going on inside tor would be interesting and helpful for advanced users (and support people) at least.

comment:3 Changed 15 months ago by nickm

Keywords: 035-deferred-20180930 added
Milestone: Tor: 0.3.5.x-finalTor: 0.3.6.x-final

Deferring several items from 0.3.5. I think these are features, not bugfixes, and therefore no longer great for 0.3.5. Please let me know if I'm wrong.

comment:4 Changed 14 months ago by nickm

Parent ID: #22266#28018

comment:5 Changed 14 months ago by catalyst

Type: defectenhancement

comment:6 Changed 13 months ago by catalyst

Sponsor: Sponsor8Sponsor8-can

comment:7 Changed 13 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:8 Changed 12 months ago by catalyst

#2878 is a duplicate.

comment:9 Changed 12 months ago by catalyst

Keywords: bootstrap-arch added

comment:10 Changed 11 months ago by gaba

Sponsor: Sponsor8-can

comment:11 Changed 11 months ago by nickm

Keywords: 040-deferred-201915 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring some tickets from 0.4.0 without proposing them for later. Please tag with 041-proposed if you want to do them.

comment:12 Changed 11 months ago by ahf

Sponsor: Sponsor19

comment:13 Changed 10 months ago by hefee

Cc: torproject@… added

comment:14 Changed 7 months ago by gaba

Keywords: network-team-roadmap-2019-Q1Q2 added; 035-roadmap-master 035-triaged-in-20180711 s8-bootstrap 035-deferred-20180930 040-deferred-201915 removed
Sponsor: Sponsor19Sponsor19-can

comment:15 Changed 6 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Moving all new, assigned, accepted, reopened, need_information tickets from sponsor 19 into the unsponsor land. Added keyword ex-sponsor19 to track and check later if we had something that can be added to new sponsors.

comment:16 Changed 6 months ago by catalyst

Keywords: ex-28018-child added
Parent ID: #28018

Unparent remaining open children of #28018.

Note: See TracTickets for help on using tickets.