commit faacf026eba54ad7e29278cb379c7fd92a212025 Author: juga0 juga@riseup.net Date: Mon Jun 4 07:24:50 2018 +0000

Include uptime in bandwidth changes event

The descriptor would be updated on bandwidth changes only when the uptime is less than 24h. --- dir-spec.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt index 5f2a713..e44052f 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -352,9 +352,9 @@

- A descriptor field other than bandwidth or uptime has changed.

- - Bandwidth has changed by a factor of 2 from the last time a - descriptor was generated, and at least a given interval of time - (20 mins by default) has passed since then. + - Its uptime is less than 24h and bandwidth has changed by a factor of 2 + from the last time a descriptor was generated, and at least a given + interval of time (20 mins by default) has passed since then.

- Its uptime has been reset (by restarting).

@@ -365,6 +365,9 @@ if none of the above events have occurred and not much time has passed (12 hours by default).

+ Tor versions older than 0.3.5.1-alpha ignore uptime when checking for + bandwidth changes. + After generating a descriptor, ORs upload them to every directory authority they know, by posting them (in order) to the URL