[tor-bugs] #33008 [Metrics/Relay Search]: Display a bridge's distribution bucket

[Tor Bug Tracker & Wiki]

#33008: Display a bridge's distribution bucket
-------------------------------------------------+-------------------------
 Reporter:  phw                                  |          Owner:
                                                 |  metrics-team
     Type:  enhancement                          |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:
Component:  Metrics/Relay Search                 |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  s30-o24a1, anti-censorship-roadmap-  |  Actual Points:
  2020Q1 metrics-team-roadmap-2020Q1             |
Parent ID:  #31281                               |         Points:  2
 Reviewer:  cohosh                               |        Sponsor:
                                                 |  Sponsor30-can
-------------------------------------------------+-------------------------

Comment (by phw):

 Replying to [comment:20 karsten]:
 > But I think we need to consider something else here. Bridge operators
 can request in their torrc file how their bridge is going to be
 distributed. [https://gitweb.torproject.org/torspec.git/tree/dir-
 spec.txt#n655 Recognized methods are: "none", "any", "https", "email",
 "moat".]
 [[br]]
 If a bridge sets `BridgeDistribution none` in its config file, BridgeDB
 will
 [https://gitweb.torproject.org/bridgedb.git/tree/bridgedb/Bridges.py?id=1f614896ed3442c8758e7ea10bef0c1fc366a4c1#n508
 discard the bridge's descriptor]. Bridges may end up in the "unallocated"
 bucket if they set `BridgeDistribution any` (which is the default), in
 which case BridgeDB ''may'' toss them into "unallocated".
 [[br]]
 > But I'm not yet sure why those 76 bridges are not included in any
 distributor, not even the "unallocated" distributor. It could be that
 they're too new (bridge pool assignment files are only synced once per day
 at UTC midnight). It could have other reasons like older tor versions.
 [[br]]
 We encourage people to set `BridgeDistribution none` if they want their
 bridge to show up on Relay Search, but don't want BridgeDB to distribute
 it. Most of our default bridges fall into that category.
 [[br]]
 > In any case it seems possible that a bridge will show up with "none" in
 Relay Search, and we might have to provide information on BridgeDB's
 information page what that means. In a way these bridges are truly
 unallocated.
 [[br]]
 Oh,
 [https://metrics.torproject.org/rs.html#details/53ABAB9A45134DD1D3B3DCF53BFA35BE4E856EC2
 you are right]. That's a great point that I had not considered. Now that
 we have both "unallocated" and "none", it seems more important to rename
 "unallocated" to "reserved". It doesn't seem too difficult to change every
 occurrence of "unallocated" in BridgeDB. How is the Metrics side looking?

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