[tor-bugs] #10418 [Tor Launcher]: Make a "Use Default Bridges" Radio button in the Tor Launcher Bridge UI

[Tor Bug Tracker & Wiki]

#10418: Make a "Use Default Bridges" Radio button in the Tor Launcher Bridge UI
------------------------------+-------------------
     Reporter:  mikeperry     |      Owner:  brade
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:
    Component:  Tor Launcher  |    Version:
   Resolution:                |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+-------------------

Comment (by mikeperry):

 Replying to [comment:19 dcf]:
 > Replying to [comment:18 mikeperry]:
 > > dcf: What if we just didn't include flashproxy in the default bridge
 prefs? Also, is UPNP likely to remain off or insufficient? If so, should
 we just provide these instructions from BridgeDB, and require that
 flashproxy remain a custom bridge type only?
 >
 > Not including flash proxy in the default bridges is a good idea. I
 recommend it. Now that we know !LearnCircuitBuildTimeout is not needed,
 the only torrc changes needed to activate flash proxy are Bridge lines,
 and those can be edited in Tor Launcher. We can document how to do it in
 FlashProxyHowto.

 Ok, this sounds fine.

 > Putting instructions in BridgeDB may not make sense because you don't
 use BridgeDB with flash proxy. I guess if you think of a beginning user
 who doesn't know where to look, so they look at BridgeDB, it would make
 sense to include some instructions like "this may work for you if you turn
 it on." For people who don't need it, it's a lot of extra information
 though.

 Well, I really think BridgeDB will be heading in some form of "Pick your
 pluggable transport type" anyway as well, with separate landing pages for
 each bridge type. The "Get FlashProxy Bridges" page could just include the
 entirety of the FlashProxy HOWTO (but hopefully a simpler form of it once
 we solve the port forwarding problem).

 > I don't know whether tor-fw-helper is going to be turned on. I don't
 think I have any say in that. My guess is it would greatly increase the
 number of people who are able to use flash proxy automatically. I'm sure
 there will still be a lot of people (behind two NATs, behind institutional
 NATs) for whom it won't work. Activating flash proxy's support for port
 forwarding, assuming tor-fw-helper is included in the bundle, is a matter
 of adding an option to the !ClientTransportPlugin command line. It might
 be nice to build a test bundle including tor-fw-helper and ask people to
 test it.

 Since this decision is effectively mine, I can tell you that you do in
 fact have a say in that, and indeed I think you just proposed a viable
 plan! ;)

 If tor-fw-helper actually ends up working out in a test bundle, and if we
 can limit its execution to people who actually try to use flashproxy, it
 seems like a no-brainer to me to include it in the default bundle.

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