[tor-bugs] #6682 [Compass]: merge atlas and compass?
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Mar 17 20:07:41 UTC 2013
#6682: merge atlas and compass?
-------------------------+--------------------------------------------------
Reporter: cypherpunks | Owner:
Type: enhancement | Status: needs_information
Priority: minor | Milestone:
Component: Compass | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Changes (by hellais):
* cc: mo (added)
Comment:
We have discussed this a bit with gsathya, karsten and mo.
I think we have reached a consensus on the fact that compass and atlas
should be merged into one tool in the following way.
Compass + Atlas (Adventurer?) should be only a frontend to onionoo.
What is currently missing inside of Atlas that is part of Compass is the
ability to perform advanced searches for relays. This would be implemented
by making the search functionality support more advanced parameter
searches.
The parameter based filtering logic that is currently part of compass
should end up inside of onionoo.
The currently missing features in onionoo are:
* "select only relays suitable for exit position", this should probably
implement a search parameter based on the value of "flag".
* "select only relays suitable for guard position", this should also be
implemented a parameter on the value of "flag"
* "select relays by AS number"
I would suggest we port Atlas to use angular.js and integrate the parts of
relevant code from Compass.
**Adventurer** should only be a front end written in HTML/JS and not do
any of the heavy lifting of parsing the onionoo responses and extracting
the results (in python). All the necessary filtering and parsing activity
should be done in the browser.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6682#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list