[tor-bugs] #6662 [Compass]: group by family

[Tor Bug Tracker & Wiki]

#6662: group by family
-------------------------+--------------------------------------------------
 Reporter:  cypherpunks  |          Owner:  karsten 
     Type:  enhancement  |         Status:  accepted
 Priority:  normal       |      Milestone:          
Component:  Compass      |        Version:          
 Keywords:               |         Parent:          
   Points:               |   Actualpoints:          
-------------------------+--------------------------------------------------

Comment(by cypherpunks):

 Hi Karsten,

 Replying to [comment:5 karsten]:
 > Maybe you want to have a look?


 Looks good.

 I did some manual checks of your results, because the lines with only two
 family members were not clear to me,
 but after checking them manually it was clear that the "overlapping node"
 was down and therefore not showing up in the second part (merged families)
 of the txt file.

 {{{
 3cce3a91f6a625~8DE5 bc1245cbe16d5ee9b2~2D25 overlapping node:
 A0EA6A3D1B4D30F5005E89501DB68D4E14A0E183 (down)
 AMORPHIS~4B47 KAMAGURKA~4045   overlapping node:
 30CC8E08C1B2B40B37A6FAF0E1DF08C007138135 (down)
 }}}

 I'm also going to contact these relay operators, so they can fix their
 family settings.

 Configuring families with a high number of relays that are regularly
 extended is a PITA, why not using this definition of families for Tor
 directly? This would reduce the number of nodes to reconfigure to 2
 regardless how many nodes you have, but I would be surprised if no one
 else had that thought already. Anyway I'll propose it on tor-dev.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6662#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online