Re: [tor-bugs] #12777 [meek]: Decide how to handle multiple meek backends in Tor Launcher

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#12777: Decide how to handle multiple meek backends in Tor Launcher
------------------------+----------------------------------
     Reporter:  dcf     |      Owner:  dcf
         Type:  task    |     Status:  needs_review
     Priority:  normal  |  Milestone:
    Component:  meek    |    Version:
   Resolution:          |   Keywords:  TorBrowserTeam201408
Actual Points:          |  Parent ID:
       Points:          |
------------------------+----------------------------------
Changes (by bastik):

 * cc: bastik.public@â (added)
 * type:  defect => task


Comment:

 >What I'm worried about is a user looking at this list of weird names and
 not knowing which to pick. Adding more meeks isn't going to help things.

 One might wonder what the difference between meek-abc, meek-aaa and meek-
 any would be.

 I don't know how to educate people properly or in this case make it
 obvious what they should select. I like structured things. Once Alice
 selected meek as her transport she could be presented with a new drop-down
 menu to choose the backend. Maybe with the description "Please choose the
 backend you are most likely to connect to."

 This makes it more complex, but for me more structured. (I have to pick
 the transport, whatever this is. And when selecting meek I have to choose
 a backend, whatever this is.

 Possibly there should be a default backend, one that does work for most
 people.

 My geo-location biases me towards knowing Google and Amazon. I feel most
 people know Google. I'm sure the more meek backends exist the more
 difficult it will be to guess whenever the will for for me or not.
 Assuming users are able to check if they can reach Google, I assume it is
 more difficult to check the other options.

 > Maybe we ship one default and return other backends through BridgeDB?
 and/or support request? I think it would be possible to ask questions like
 if someone is able to visit Amazon and give out those backends on positive
 answers.

 How does BridgeDB know what works for the requesting user?
 Having him ask for a specific backend requires additional knowledge.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12777#comment:3>
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