#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:26 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. [[br]] Yes, that's an oversight. How about this: [[br]] > Bridges whose distribution mechanism is "None" are not distributed by BridgeDB. It is the bridge operator's responsibility to distribute their bridges to users. Note that on Relay Search, a freshly set up bridge's distribution mechanism says "None" for a while. Be a bit patient, and it will then change to the bridge's actual distribution mechanism. [[br]] Do we have an approximate time frame within which Relay Search should go from "None" to the bridge's actual distribution mechanism? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33008#comment:27> 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