[tor-bugs] #10218 [Tor]: Provide "users-per-transport-per-country" statistics for obfsbridges

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Feb 16 00:31:54 UTC 2016

#10218: Provide "users-per-transport-per-country" statistics for obfsbridges
 Reporter:  asn                                  |          Owner:
     Type:  enhancement                          |  joelanders
 Priority:  Medium                               |         Status:
Component:  Tor                                  |  assigned
 Severity:  Normal                               |      Milestone:  Tor:
 Keywords:  tor-bridge tor-pt bridgedb-dist      |  0.2.8.x-final
  028-triage                                     |        Version:
Parent ID:                                       |     Resolution:
  Sponsor:                                       |  Actual Points:
                                                 |         Points:  medium

Comment (by dcf):

 Replying to [comment:20 karsten]:
 > The bad news is that I don't have the time before the dev meeting to run
 this analysis, and I can't even say whether the weeks after the dev
 meeting will be any better.  That's why I
 uploaded the data] for somebody else to do the analysis and publish
 results here.  Any takers?

 Here is my try: attachment:ptcc.R.

 The blue lines show the lower and upper bounds according to the formulas
 in comment:20. The heavy gray lines go from 0 to the total number of
 responses for the transport across all bridges.

 == obfs3 ==

 The obfs3 graph shows that the ranges can actually be fairly tight.


 == meek ==

 In the meek graph, the ranges are super small (almost too small to see);
 in other words we know the number very precisely. That's because all the
 existing meek bridges only run meek and nothing else (just a negligible
 number of <OR> connections).


 == fte ==

 Most of the lower bounds for FTE bottom out at 0 because PT + CC < 1.


 There are a couple of anomalies if you look at the full graphs, caused by
 rows with duplicate fingerprints. There are just a few of them. I didn't
 bother to clean them up. For example,
 00:00:00,2016-02-01 03:38:47,1.8
 11:41:28,2016-02-02 00:00:00,14.4
 00:00:00,2016-02-01 03:38:47,0.9
 11:41:28,2016-02-02 00:00:00,4.8

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

More information about the tor-bugs mailing list