Matthew John Toseland writes:
> Specifically, the process for a scarce *insert* will be:
> 1) Is the key popular?? We can tell this from how many peers are
> subscribed to it in the ULPR table. If not, kill the request; we only
> provide protection for popular
On 14/09/17 22:18, Arne Babenhauserheide wrote:
>
> Matthew John Toseland writes:
>> On 14/09/17 17:33, Arne Babenhauserheide wrote:
>>> I think the core problem is that I don’t quite understand what you’re
>>> proposing. Bundles I understand, but I don’t understand how
On 15/09/17 20:51, Arne Babenhauserheide wrote:
>
> Matthew John Toseland writes:
>> Specifically, the process for a scarce *insert* will be:
>> 1) Is the key popular?? We can tell this from how many peers are
>> subscribed to it in the ULPR table. If not, kill the