[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #16276 [Onionoo]: bug in onionoo's family set detection
#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 karsten):
Replying to [comment:16 leeroy]:
> When you say,
>
> > As long-term fix, let's think about adding separate field
"effective_family" or similar for the sake of backward compatibility and
to enable clients to detect misconfiguration.
>
> is that in favor of both keys proposed? Something like an
effective_family ''and'' a key indicating problems with family, like the
diff key, ''or'' only the key for effective_family? Just checking first. I
have to wait on archive data importing, so this would be good for testing
the addition of new tracked OR data.
Well, do we need another field like `"ineffective_family"`, if we keep
both `"family"` and `"effective_family"`? In theory, if those two arrays
don't have the same length, there's something wrong, and every entry
that's missing in `"effective_family"` is something for the relay operator
to look into; unless I missed a case. I'd rather not want to add
redundant data but rely on Onionoo clients to be smart enough to display
information in a way that's useful to users. Onionoo is not meant to be
used by humans. What do you think?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16276#comment:17>
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