<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><div dir="ltr"><font color="#000000"><span style="caret-color: rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);">On 16 Dec 2018, at 17:01, <a href="mailto:starlight.2018q2@binnacle.cx">starlight.2018q2@binnacle.cx</a> wrote:<br><br></span></font></div><blockquote type="cite"><div dir="ltr"><font color="#000000"><span style="caret-color: rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);">The cause is<br><br><a href="https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458f5948275a44766">https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458f5948275a44766</a><br><br><a href="https://trac.torproject.org/projects/tor/ticket/24803">https://trac.torproject.org/projects/tor/ticket/24803</a><br><br>Would be appreciated if the Tor project published outputs<br>of UpdateFallbackDirs.py job runs used when rebuilding<br>the list. Thus operators who have expended effort to keep<br>their relays eligible will know why when dropped.</span></font></div></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br></span><div><span style="background-color: rgba(255, 255, 255, 0);">We usually attach the logs to the relevant ticket.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">This time, I saved the logs, but accidentally overwrote them.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">And I didn't ask Colin to attach his logs.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">We'll try to do better next time: I've added a note on the ticket</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">for 2019.</span></div></div></div><div dir="ltr"><br>On 17 Dec 2018, at 10:45, <a href="mailto:starlight.2018q2@binnacle.cx">starlight.2018q2@binnacle.cx</a> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>Ran the script: output is attached to this message for anyone</span><br><span>interested. Live-network test results will vary by time and by</span><br><span>the location of tester. Attached run was made over Tor</span><br><span>itself using 'torsocks'.</span><br></div></blockquote><div><br></div><div>Thanks!</div><br><blockquote type="cite"><div dir="ltr"><span>I was bit by having disabled the unencrypted DIR port for</span><br><span>one day recently as an experiment.</span></div></blockquote><br><div>We rely on onionoo's last changed field:</div><div><a href="https://metrics.torproject.org/onionoo.html#details_relay_last_changed_address_or_port">https://metrics.torproject.org/onionoo.html#details_relay_last_changed_address_or_port</a></div><div><br></div><div>Changing or removing a published address or port resets the</div><div>last changed date. Adding an IPv6 address does not reset the</div><div>last changed date.</div><div><br></div><div>I realise that it's disappointing for relay operators to lose a flag.</div><div>But we're not too worried if a fallback drops out of the list for a</div><div>release or two: changing the fallback list regularly makes it</div><div>harder to block. And that's good for users.</div><div><br></div><div>T</div></body></html>