-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi,
I like prop242 [1] because it doesn't "Nuke MyFamily" [2] but replaces it with a better approach. "Better" in terms of scalability and maintainability.
I don't know of any current 'tools' (except the tor client itself) that use MyFamily data but Virgil's [3] gamification website and compass group-by family feature [4] would depend on it.
So before spending time on features that depends on an uncertain descriptor field, it is probably better to wait till the fate of that property (MyFamily) has been decided.
The reason for this email is to find out when that fate will be decided upon? (expected answer: before tor 0.2.7.x-final is released)
Nick's statement:
Having some paths with all three nodes in the same family scares me
gives me some hope that it won't go away completely and will allow me to group relays to an operator (as long as the operator decides to configure it).
Even in the unlikely event of MyFamily being nuked completely (with no replacement) - I guess it will be some years(?) till you deprecate pre tor 0.2.7 clients?
[1] https://trac.torproject.org/projects/tor/ticket/6676 [2] https://gitweb.torproject.org/torspec.git/tree/proposals/242-better-families... [3] https://lists.torproject.org/pipermail/tor-dev/2014-June/006975.html [4] https://raw.githubusercontent.com/nusenu/misc-files/master/biggest_tor_relay...