[tor-bugs] #2905 [Vidalia]: Adapt Vidalia UI to allow users to avoid connecting to the public tor network

[Tor Bug Tracker & Wiki]

#2905: Adapt Vidalia UI to allow users to avoid connecting to the public tor
network
---------------------+------------------------------------------------------
 Reporter:  anonym   |          Owner:  chiiph         
     Type:  defect   |         Status:  new            
 Priority:  major    |      Milestone:  Vidalia: 0.2.13
Component:  Vidalia  |        Version:  Vidalia 0.2.10 
 Keywords:  bridges  |         Parent:                 
   Points:           |   Actualpoints:                 
---------------------+------------------------------------------------------

Comment(by chiiph):

 Replying to [comment:17 anonym]:
 > Is there any reason for why you want to stick with the stuff in the
 "else:" part (i.e. "if the user checks 'My ISP blocks...' but doesn't add
 bridges, just ignore this with a warning")? What that suggests is
 precisely going back to the old behaviour you described in #3354, which I
 feel is very confusing and unintuitive. Why should an option that is set
 when you open the Vidalia settings suddenly revert when pressing Ok even
 though you haven't touched itm or any related options?

 Right now it warns about the fact that it's disabling the setting, and it
 can just as easily ask if that's what the user intended to do.
 I want to keep that behavior because the whole situation where tor "just
 doesn't work" because there aren't any bridges configured and UseBridges=1
 is the non-intuitive behavior to me. I want to avoid making it easy for a
 user to be in that situation.

 >
 > My [comment:12 suggestion] captures both the case when you start Vidalia
 and when you reconfigure Vidalia in the settings since both of these call
 ConfigDialog::applyChanges(). My suggestion
 >  * wouldn't add any more complexity to code -- in fact the code would be
 put in the same place (ConfigDialog::applyChanges()) instead of two places
 (one for startup, one for when saving settings).

 This is not about the amount of coding needed.

 >  * has only one prompt dealing with this instead of two, which is more
 consistent for the user.

 It'd need two, one when Vidalia starts and notices the situation, and
 another when the user opens the settings, click "My ISP blocks..." and
 doesn't put any bridges in.

 >  * does not confuse the user as I think #3354's behaviour does.

 I just don't want the unaware user that clicked wrongly in the settings
 end up with a non-working tor.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2905#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online