#18113: Dynamically allocate clients to default Tor Browser bridges of a certain type -----------------------------------------------+--------------------------- Reporter: isis | Owner: brade Type: enhancement | Status: Priority: Medium | needs_revision Component: Applications/Tor Launcher | Milestone: Severity: Normal | Version: Keywords: tbb-bridges, TorBrowserTeam201604 | Resolution: Parent ID: | Actual Points: Reviewer: | Points: | Sponsor: -----------------------------------------------+---------------------------
Comment (by isis): Replying to [comment:19 arma]: > (Except the bandwidth weighting stuff -- either Tor chooses from all of them equally because it doesn't have any descriptors at the time it chooses which one will go into the state file first, or it does have the descriptors so it weights by the self-advertised bandwidths in the descriptors. I'd have to check, but my guess would be the former. Still, I think that is better solved inside Tor, where Tor Browser's job would be to add a weight to the bridge line.) So you mean we would add a parameter to bridge lines that specifies weight? Or another optional line underneath it like {{{ Bridge 1.2.3.4:5555 0123456789abcdef0123456789abcdef01234567 BridgeWeight 8 Bridge 5.6.7.8:4545 f0123456789abcdef0123456789abcdef0123456 BridgeWeight 2 }}} Changing the bridge lines once we're taking PTs into account starts to get super ugly… I think if we're going this route we'd need to add something like the BridgeWeight lines. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18113#comment:20> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs