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

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

#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 karsten):

 Replying to [comment:24 phw]:
 > Replying to [comment:23 karsten]:
 > >  - "None": either not distributed by BridgeDB as requested by the
 bridge operator, or distributed via one of the four other mechanisms but
 too new for Relay Search to know. (The info page should probably mention
 both possibilities.)

 Your latest screenshot doesn't say anything about that second possibility
 of assignment information not being propagated between services yet. I
 could imagine that impatient new bridge operators will ask why their
 bridge ended up in the None bucket. If you left this note out on purpose,
 maybe in order to keep things short, that's fine by me.

 > > If this makes sense, we can tell Relay Search to display these terms
 (using this capitalization) rather than the raw strings it receives from
 bridge pool assignment files.
 > [[br]]
 > Yes, this sounds good to me. BridgeDB's new info page will have anchors
 for all (https, moat, email, reserved, none), for example:
 bridges.torproject.org/info#https. Does this work for you?

 Yes, this works. I have a patch here that I can deploy when that page
 exists. Please let me know when that is the case, and I'll deploy it.

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