We'd obviously lose some connections if we lost MyFamily. And I'd prefer
not to lose them. However, if there's other needs which require the nuking
of MyFamily, my/Roster's world would not end.
-V
On Sunday, 17 April 2016, Tim Wilson-Brown - teor
wrote:
>
> > On 16 Apr
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> On 16 Apr 2016, at 17:13, Virgil Griffith wrote:
>
> 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
On Sat, 16 Apr 2016 20:30:29 +0300
s7r wrote:
> I agree that teor's O(Kn) is the best approach from performance (no
> additional memory allocations), simplicity and efficacy point of view.
> O(Kn) algorithm will clear the entries only based on their expiration
> time, it won't
Hello,
On 4/16/2016 4:11 PM, David Goulet wrote:
[snip]
>>
>>
>> A third alternative is that we can iterate through each time period:
>> Set K to the oldest expected descriptor age in hours, minus 1 hour
>> Deallocate all entries from Cache A that are older than K hours
>> Deallocate all entries
On 16 Apr (12:49:44), Tim Wilson-Brown - teor wrote:
>
> > On 16 Apr 2016, at 05:47, David Goulet wrote:
> >
> > Hi!
> >
> > (For the following, I'm only talking about HS directory.)
> >
> > Here is my conundrum. I was working on plugging the new cache for proposal
> > 224
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