[tor-relays] confirming onionoo/CollecTor issues vs. Happy Family relay misconfiguration

[nusenu via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>]

Hi,

I've been contacting relay operators to
verify suspected CollecTor/onionoo issues that appear since CollecTor got replaced in early April.
To scale a bit better I'm sending this email to the tor-relays list + BCC instead.

In most cases so far it turned out to be an onionoo issue but I see some slow improvements.

If you are one of the operators listed below it would be great if you could
help verifying your config and confirm if
- this is indeed an onionoo issue (all your relays found by the onionoo URL below should have the same Happy Family configuration but according to onionoo do not)
- or an inconsistent Happy Family configuration on your side: not all your relays have Happy Family configured (not an onionoo issue)
- they are not actually your relays - in this case you can report them for removal to the bad-relays team if they use your contact information

With your help we can get a better overview of the current onionoo / CollecTor situation.

I noticed unexpected (missing) family_ids on relays using this CIISS url value:

alxu.ca
doedelkiste.de
germancraft.net
torix-relays.org
tuxli.org
for-privacy.net
emeraldonion.org
www.1aeo.com

example onionoo URL for doedelkiste.de:
https://onionoo.torproject.org/details?contact=doedelkiste.de&fields=family_ids,nickname,as_name,fingerprint

You can simply replace the contact parameter value with your domain.

You should be able to spot suspicious lines in the output because these lines are shorter (no family_ids string included).

thanks for your help!
nusenu

--
https://nusenu.github.io

_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx