[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6730 [Compass]: A way to see changes in datasets over time
#6730: A way to see changes in datasets over time
-------------------------+--------------------------------------------------
Reporter: mo | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Compass | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by karsten):
Replying to [comment:3 gsathya]:
> Moritz made https://github.com/moba/tor-fast-exits-tracker to track
changes. Maybe integrate this into compass?
No. That script seems like a fine hack, but not like a good design. We
should not integrate it into Compass. Compass should not create an
archive of Onionoo documents. In fact, no Onionoo client should be forced
to do that. Such a history based on Onionoo documents starts on the day
when you set up the script, and there's no way to import past history.
Also, whenever the script fails, there will be missing data that cannot be
recovered.
I guess what we should do instead is generalize the desired feature as
much as possible and put that into Onionoo itself. Onionoo has access to
the last 72 hours of Tor data, so can recover from failures up to 72 hours
without missing any data, and it's easy to import descriptors from the
past weeks, months, or even years. What's the exact feature here? Maybe
we can integrate that data into Onionoo somehow.
Note that this discussion is not quite what this ticket is about, which is
to detect newly added or recently disappeared relays or bridges. Please
open a new ticket.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6730#comment:4>
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