-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 Mon, Aug 20, 2012 at 12:00 PM, vmon wrote:
> Hey Zack,
>
> I just did my last pushes before putting my pencil down for the final
> evaluations. They take care of the followings:
>
> - The remaining of all your comments on the
> github. Except for "always use xalloc instead of new". I have used
On Sun, Aug 19, 2012 at 8:25 PM, vmon wrote:
> Hey Zack,
>
> I know you are super busy packing for your big move, but I thought as
> tomorrow is
> the hard deadline for GSoC, is not a bad ideas to give you some final update.
I appreciate it. I am still in the middle of moving and don't have
the
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
