[tor-bugs] #7895 [Onionoo]: Add new Onionoo document type containing fast-exit history

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Jan 9 08:11:16 UTC 2013


#7895: Add new Onionoo document type containing fast-exit history
-------------------------+--------------------------------------------------
 Reporter:  karsten      |          Owner:     
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:     
Component:  Onionoo      |        Version:     
 Keywords:               |         Parent:     
   Points:               |   Actualpoints:     
-------------------------+--------------------------------------------------
 Moritz wrote a small [https://github.com/moba/tor-fast-exits-tracker
 script] that keeps track of all "fast exits" as defined in #6498.  The
 hourly updated output is [https://www.torservers.net/tor-fast-exits.html
 here], where mouse-over shows timestamps.

 #6730 discusses integrating this script into Compass, but as I
 [https://trac.torproject.org/projects/tor/ticket/6730#comment:4 argue]
 there, we should rather think about integrating it into Onionoo and
 providing fast-exit history documents, and then visualize the data in
 Compass, Atlas, or whichever visualization tool we want.  That would be a
 much better design, because Onionoo can import past history and compensate
 for temporary downtime much easier than Compass or this script can.

 What data would we expect Onionoo to provide here?  I could imagine a
 format similar to
 [https://onionoo.torproject.org/bandwidth?lookup=F2044413DAC2E02E3D6BCF4735A19BCA1DE97281
 bandwidth documents] but with fractions of being considered a "fast exit"
 in the given "interval" lengths.  For the "3_days" graph with a detail
 level of 1 hour this is easy, because it's just 0 or 1.  For "1_week",
 "1_month", etc. it would be some value in [0..1] saying what fraction of
 the displayed detail of 4 hours, 12 hours, etc. the relay was a "fast
 exit".  What we can't do is keep hourly detail for older data, because
 that simply wouldn't scale.  Would this be helpful?

 This ticket is currently blocking on pyonionoo, because we shouldn't make
 too many changes to Onionoo while pyonionoo is trying to catch up.

 Once this ticket is implemented, we'll have to open a new ticket for using
 the new documents in Compass, Atlas, or wherever we want.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7895>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list