Re: [tor-bugs] #16276 [Onionoo]: bug in onionoo's family set detection

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#16276: bug in onionoo's family set detection
-----------------------------+-----------------
     Reporter:  cypherpunks  |      Owner:
         Type:  defect       |     Status:  new
     Priority:  major        |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by leeroy):

 I didn't say they were better. You said you want to avoid redundancy. I
 merely point out that both a family and effective_family is a
 contradiction of your stated objectives. I'm just trying to make the
 implementation concrete before trying to write any code.

 Detecting misconfiguration can be done with the current system. Ask for
 query by family, then ask for details document for one relay that was
 returned a member of the set. Done. You say you would prefer lack of
 redundancy, the ability to detect misconfiguration, retaining backwards
 compatibility. So I'm trying to understand how family and effective_family
 is better than the current implementation. If Onionoo isn't a service used
 by humans, then why change it at all in this case.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16276#comment:22>
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