Skip to content
GitLab
Explore
Sign in
This is an archived project. Repository and other project resources are read-only.
Legacy
Trac
Wiki
Org
Meetings
2017montreal
Notes
OONIMetrics
OONIMetrics
· Changes
Page history
Raw import from Trac using Trac markup language.
authored
Jun 15, 2020
by
Alexander Færøy
Hide whitespace changes
Inline
Side-by-side
org/meetings/2017Montreal/Notes/OONIMetrics.md
0 → 100644
View page @
53a16e3a
Recap of yesterday‘s session: Useful metrics for Tor Browser
• information of which transports work in which countries: let users pick a country and then provide transports that likely work
• automated reachability tests of hard-coded default bridges
• OnionPerf vs. OONI throughput test
Add new graphs to Tor Metrics: vanilla Tor
• OONI could add a daily task that produces a CSV file with number of measurements by country and day that worked or timed out; fields may include:
◦ date
◦ country
◦ number of networks as a confidence metric
◦ successes
◦ unknowns (timeouts, failures, other issues)
• Plus a non-aggregated version including
◦ time to bootstrap
◦ ooni report ID
Add another graph to Tor Metrics: Bridge reachability test
• basic connectivity test, not Tor connection
• challenge: default bridges might go down for days
How can OONI make better use of Tor Metrics data
• Look at reported user numbers by single relay/bridge