<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div>On 9 Jun 2018, at 22:12, Cristian Consonni <<a href="mailto:cristian@balist.es">cristian@balist.es</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hi,</span><br><span></span><br><span>due to the new DigitalOcean billing terms for bandwidth (see this other</span><br><span>thread [1]), I have limited my relay bandwidth to be sure I will stay</span><br><span>withing the limits:</span><br><span>```</span><br><span>RelayBandwidthRate 360 KB # Throttle traffic to 100KB/s (800Kbps)</span><br><span>RelayBandwidthBurst 720 KB # But allow bursts up to 200KB/s (1600Kbps)</span><br><span>```</span><br><span></span><br><span>This is the relay:</span><br><span><a href="https://metrics.torproject.org/rs.html#details/1211AC1BBB8A1AF7CBA86BCE8689AA3146B86423">https://metrics.torproject.org/rs.html#details/1211AC1BBB8A1AF7CBA86BCE8689AA3146B86423</a></span><br><span></span><br><span>The relay is also a Fallback Directory Mirror. I plan on keeping the</span><br><span>relay running, but I was wondering if the new limits disqualify it or if</span><br><span>they are a problem to let it be a fallback directory mirror.</span><br></div></blockquote><br><div>The minimum bandwidth for a fallback directory mirror is currently 500 kBps:</div><div><a href="https://gitweb.torproject.org/tor.git/tree/scripts/maint/updateFallbackDirs.py#n241">https://gitweb.torproject.org/tor.git/tree/scripts/maint/updateFallbackDirs.py#n241</a></div><div>And if we have extra fallbacks, we choose the fastest ones.</div><div>We choose fast relays so clients can bootstrap quickly.</div><div><br></div><div>Next time we rebuild the list, your relay will probably not be chosen as a fallback.</div><div><br></div><div>But it's still helping the tor network.</div><div><br></div><div>Thanks for running a relay!</div><div><br></div><div>T</div></body></html>