#21095: Accept more values for the "order" parameter -----------------------------+------------------------------ Reporter: lukechilds | Owner: metrics-team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Metrics/Onionoo | Version: Severity: Normal | Resolution: Keywords: metrics-help | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------+------------------------------
Comment (by lukechilds): Would `?order=-first_seen&limit=10` not return the 10 most recent relays to join the network? `?first_seen_days=-1&order=-consensus_weight&limit=10` seems like it could definitely be helpful, however the first method would be ideal. If there haven't been many new relays on the current day we might need to go back to yesterday. And for users specifically trying to get a clean IP, age would be more important than performance. If we could get sorting by `first_seen` that would be awesome! I've had a look through the file you linked. I've never touched a line of Java in my life and to be honest I'm kind of struggling to grok it. It looks like I could just copy and past the `orderRelaysByConsensusWeight ` bits for `first_seen` but I'm not quite sure how that wires up with the `order` URL parameter. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21095#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs