[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13137 [Onionoo]: Historical data



#13137: Historical data
---------------------------+-----------------
     Reporter:  Sebastian  |      Owner:
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:
    Component:  Onionoo    |    Version:
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |
---------------------------+-----------------

Comment (by karsten):

 Thanks for the suggestion!

 Can you provide more information what you're looking for?  We already
 provide historical data based on what's written about a relay in the
 consensus.  Example, here's what a recent consensus says about gabelmoo:

 {{{
 r gabelmoo 8gREE9rC4C49a89HNaGbyh3pcoE 5KFudVCmNLttd+m4hgbJjZLquYA
 2014-09-16 04:09:24 212.112.245.170 443 80
 s Authority HSDir Running Stable V2Dir Valid
 v Tor 0.2.6.0-alpha-dev
 w Bandwidth=20 Unmeasured=1
 p reject 1-65535
 }}}

 We already provide the following historical data:

  - `details` documents contain fields `"first_seen"` and `"last_seen"`,
 telling you when the relay was first and last seen in a consensus.
  - `details` documents further contain a field
 `"last_changed_address_or_port"`, indicating when the relay changed its
 primary OR address or port.
  - `weights` documents contain a field `"consensus_weight"` that is a
 history object with absolute consensus weight of the relay over time.
 This history is available for the past week, month, 3 months, year, and 5
 years.
  - `uptime` documents contain a history object telling you what fraction
 of consensuses contained a given relay.  This history is available for the
 same time frames as histories in `weights` documents.

 (Note that your favorite Onionoo client may not display these fields yet,
 but that's a task for the client author, not a feature request for
 Onionoo.)

 What specifically are you interested in, in addition to the existing
 histories?

 For example, do you really care whether a relay was contained in a
 specific consensus three weeks and two days ago at 16:00 UTC, and which
 relay flags and consensus weight it had?  (It's not likely that we'll be
 able to provide this amount of detail, so I hope the answer is no.)

 Or would it already help to know when a relay first got certain relay
 flags assigned?  I'm thinking of `Guard` and `Stable` here, so I could
 imagine two new fields `first_guard` and `first_stable` for `details`
 documents.  (Are there more relay flags that you care about in the context
 of historical data?)

 And for consensus weights, if the history in `weights` documents is not
 sufficient, what are you missing?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13137#comment:1>
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