I'm not wholly in favor of keeping MyFamily in its current form.  In Roster we simply need a way to identify when two relays are owned by the same operator.  Worst comes to worst we could use the email address in the ContactInfo, or some such.

There have been proposals to do more creative signature schemes for MyFamily ownership.  This would also be a satisfactory solution.

In summary, my world would not end if MyFamily ceased to exist----we'd simply use the ContactInfo for family membership.  Obviously family membership then becomes spoofable, but perhaps who cares?

-V

On Sunday, 27 March 2016, nusenu <nusenu@openmailbox.org> wrote:
One year after my last thread on that topic [0] I'd like to move forward
on the question whether tor should have a MyFamily functionality or not,
because it seems to be a blocker of prop242 (#5565) and it is clear that
the current MyFamily design is not practical for many - given the amount
of improper or undeclared families [6].

prop 242 is also relevant in the context of Sibyls because if MyFamily
becomes trivially easy for everyone to configure one might even start to
use it to tell "good" and "bad" apart.

If you have an opinion on that topic please reply.

I tried to collect opinions on that from past threads and trac.

When Nick asked "So, what do we think?" last year only people in favor
of keeping it replied.

In favor of keeping it:
        Nick [1]
        Teor [2]
        Virgil [3]
        Griffin [4]
        Moritz [5]

In favor of nuking MyFamily:
        rransom
        anyone?
        Please speak up.

Tools that use/display/process/depend on MyFamily:
- tor-roster.org
- onionoo
- atlas
- others?

Can we close #6676 if no one is in favor of removing MyFamily?
https://trac.torproject.org/projects/tor/ticket/6676



[0] https://lists.torproject.org/pipermail/tor-dev/2015-March/008516.html
[1] https://lists.torproject.org/pipermail/tor-dev/2015-March/008517.html
[2] https://lists.torproject.org/pipermail/tor-dev/2015-March/008531.html
[3] https://lists.torproject.org/pipermail/tor-dev/2015-March/008527.html
[4] https://lists.torproject.org/pipermail/tor-dev/2015-March/008529.html
[5] https://trac.torproject.org/projects/tor/ticket/6676#comment:8
[6]
https://raw.githubusercontent.com/nusenu/tor-network-observations/master/tor_families_master.txt
https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dangerous_relaygroups.txt