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:          |
------------------------+----------------------------------

Comment (by bastik):

 > Also, instead of ordering the elements alphabetically, maybe it would be
 better to put obfs3 on top (since it's recommended). Then put fte, and
 then meek and finally flashproxy? I'm suggesting this because putting
 obfs3 on top might be more intuitive to users, and also because that's the
 order I would probably want to try my transports if I was censored.

 I think it is reasonable to list the most likely working solution topmost,
 followed by what's next likely to succeed. I agree that if I don't have a
 clue about any transport I would pick the one that is recommended first.
 If that fails or there is no recommendation I would go to that list from
 top to bottom. Flashproxy requires port-forwarding, still, so it is least
 likely to work for most people.

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