-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Just stumbled upon Mike's trac entry to change MyFamily too, I'm
adding it to this thread as a ref:
https://trac.torproject.org/projects/tor/ticket/5565
-BEGIN PGP SIGNATURE-
iF4EAREKAAYFAlA3ZOMACgkQyM26BSNOM7aYXwEAm6a0ZWf5nrFDpRzMLkRsTeS1
On 8/23/12 10:12 PM, tagnaq wrote:
>> True, but: If one relay disappears for a while then the family may
>> break into two if it was the only joint.
>
> For the family (see #6662):
> 3cce3a91f6a625~8DE5 bc1245cbe16d5ee9b2~2D25
>
> the connecting relay was down since 2012-04-04 and still karsten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> True, but: If one relay disappears for a while then the family may
> break into two if it was the only joint.
For the family (see #6662):
3cce3a91f6a625~8DE5 bc1245cbe16d5ee9b2~2D25
the connecting relay was down since 2012-04-04 and still karste
On Thu, 23 Aug 2012 19:03:06 +, tagnaq wrote:
...
> Why?
> This would reduce the configuration effort required when adding a new
> relay to *two* relays regardless of how many relays are in your family.
True, but: If one relay disappears for a while then the family may
break into two if it was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
when requesting a new group by feature for compass [1] (#6662 [2]) I
discussed with Karsten about how to handle asynchronous/overlapping
families:
karsten:
> Here's an example. Assume we have three relays: A, B, and C. These
> relays state the
