Hi Karsten,
just wanted to let you know that the delta between
relays_published and current time is unusually high.
https://onionoo.torproject.org/details?limit=0
{"version":"4.2",
"build_revision":"bce585f",
"relays_published":"2017-10-25 04:00:00",
(please let me know if you have automated m
> On 26 Oct 2017, at 06:36, nusenu wrote:
>
> teor:
>> We would like to make Tor relays report their bandwidth statistics
>> every 24 hours, rather than every 4 hours.
>
> How has the new time period been decided on?
> Is one day the upper bound for some use-case?
> If longer periods (2, 3 or 7
> On 25 Oct 2017, at 14:35, teor wrote:
>
> This change removes 2-50 bytes from the microdescriptors of relays that
> have an IPv6 ORPort, and adds them to reachable IPv6 relays' microdesc
> consensus entries.
For the record, the byte figures here is wrong, it should read "7-50 bytes"
or
teor:
> We would like to make Tor relays report their bandwidth statistics
> every 24 hours, rather than every 4 hours.
How has the new time period been decided on?
Is one day the upper bound for some use-case?
If longer periods (2, 3 or 7 days...) are safer: why not increase it
even more?
--
h
Hans-Christoph Steiner:
>
>
> Nick Mathewson:
>> On Wed, Aug 10, 2016 at 5:01 AM, Hans-Christoph Steiner
>> wrote:
>>>
>>> FYI I registered https://gitlab.com/torproject to claim the name in the
>>> gitlab namespace. I'm happy to hand it over to a more official Tor
>>> person if anyone wants.
On Tue, Oct 24, 2017 at 11:35 PM, teor wrote:
> Hi all,
>
> We would like to move IPv6 ORPorts from microdescriptors to the
> microdesc consensus. This makes it easier for IPv6 clients to bootstrap
> and choose reachable guards.
>
> The proposal is inlined below, it is also available with the cor
