[tor-bugs] #18113 [Tor Launcher]: Dynamically allocate clients to default Tor Browser bridges of a certain type

[Tor Bug Tracker & Wiki]

#18113: Dynamically allocate clients to default Tor Browser bridges of a certain
type
--------------------------------------+------------------------------
 Reporter:  isis                      |          Owner:  brade
     Type:  enhancement               |         Status:  needs_review
 Priority:  Medium                    |      Milestone:
Component:  Tor Launcher              |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-bridges tor-launcher  |  Actual Points:
Parent ID:                            |         Points:
  Sponsor:                            |
--------------------------------------+------------------------------

Comment (by yawning):

 Replying to [comment:2 teor]:
 > Over the longer term, should we patch tor to pick a random bridge from
 its list as well, or do we want to preserve the in-order behaviour?

 Our load balancing when we have multiple bridges on the tor daemon side is
 subopotimal/non-existent, and that's where I'd rather see this addressed.
 What I view as the ideal behavior would be to pick at random, and persist
 the chosen bridge to minimize churn.

 > Would we need to store state somewhere on which ones were previously
 tried?

 Yes, if we're solving this from the tor-browser side, then Tor Browser
 should persist the first working bridge it encounters.

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