[tor-bugs] #6947 [Metrics/Onionoo]: Allow filtering relays by version ranges

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Jul 24 13:58:20 UTC 2018


#6947: Allow filtering relays by version ranges
-----------------------------+------------------------------
 Reporter:  rransom          |          Owner:  metrics-team
     Type:  enhancement      |         Status:  assigned
 Priority:  Medium           |      Milestone:
Component:  Metrics/Onionoo  |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------------

Comment (by karsten):

 Replying to [comment:10 irl]:
 > Replying to [comment:9 karsten]:
 > > However, I'm not sure what the most intuitive interface is. Maybe it's
 something else, like a different character for ranges, such as
 `/details?version=0.3.2.1:0.3.2.5`. (If so, we should consider changing
 `first_seen_days` and `last_seen_days`, too, for consistency.)
 >
 > I think using `:` for ranges is better, as long as we can be certain
 that we'll never see a `:` in a released Tor version. We should probably
 require this in torspec somewhere. If we do a major version change, which
 I think we should for this, then we would also change
 `{first,last}_seen_days`.

 Hmm, on second thought, `:` wouldn't work so well with qualified search
 terms. Imagine a search for `version:0.3.2.1:0.3.2.5` (for versions
 0.3.2.1, 0.3.2.2, 0.3.2.3, 0.3.2.4, and 0.3.2.5) or even
 `version::0.3.2.5` (for everything ''until'' 0.3.2.5) or
 `version:0.3.2.1:` for 0.3.2.1 or newer).

 New idea (sorry for the brainstorming, I'm just trying to find the best
 solution): `..`, as in `version:0.3.2.1..0.3.2.5` or `version:..0.3.2.5`
 or `version:0.3.2.1..` for the examples given above. Yet unimplemented, so
 no guarantee that it will work well in all cases. We'd only have to
 require that versions don't contain two consecutive `.`, but that should
 be a safe assumption. What do you think? Are there better alternatives?

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


More information about the tor-bugs mailing list