[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18967 [Metrics/Onionoo]: Add UUID to families in Onionoo
#18967: Add UUID to families in Onionoo
-----------------------------+---------------------
Reporter: seansaito | Owner:
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Metrics/Onionoo | Version:
Severity: Normal | Resolution:
Keywords: persistence, | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------+---------------------
Comment (by seansaito):
Hi Karsten,
I'm wondering whether it's possible to create a Family Document scheme for
Onionoo. This Document will aggregate every relay within an extended
family, including stats such as bandwidth, consensus weight, country, etc.
It will also be able to fetch Family Documents from the past (where the
largest / oldest fingerprint becomes the identifier). This way we don't
need family IDs at all, though we still need to decide how to deal with
the issues you mentioned above.
A sample implementation of aggregating relays can be found here (it's a
script I use for Roster):
https://github.com/seansaito/Roster/blob/master/app/models/family_aggregator.py
Basically each family will be stored in a JSON dictionary, where the key
is the oldest/largest fingerprint.
If a creation of a Family Document seems too time/effort consuming, I can
first implement a similar scheme specifically for Roster and see how it
goes. What do you think?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18967#comment:11>
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