[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33008 [Metrics/Relay Search]: Display a bridge's distribution bucket
#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:28 karsten]:
> The delay between BridgeDB assigning a new bridge to a distributor and
Relay Search learning about it is roughly linearly distributed from 1 to
25 hours. For example, the bridge pool assignments file written by
BridgeDB at 2020-03-16T00:01:45Z was archived by CollecTor at
2020-03-17T00:09:00Z and would be processed by Onionoo at about
2020-03-17T00:45:00Z. That's the worst case scenario, though. How about
you write something vague like "usually within one day" and keep the "be
patient" part? :)
[[br]]
Perfect, thanks Karsten.
Cecylia, can you please review the following three commits?
https://github.com/NullHypothesis/bridgedb/compare/b39e576...enhancement/33008
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33008#comment:29>
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