<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<pre>Nicenstein
7614EF326635DA810638E2F5D449D10AE2BB7158</pre>
<pre>Nicenstein3
FE3E691E5C804CBAB0C491F4365AA6B4267BF86E
</pre>
<pre>BurningMan
3CCF9573F59137E52787D9C322AC19D2BD090B70
AlanTuring
2BB85DC5BD3C6F0D81A4F2B5882176C6BF7ECF5A
torturing
6F647831035CDB891B33103A073AEB9028122129
Nicenstein2
8E52CC35132AC6DF3781F539148781274D150919</pre>
<div class="moz-cite-prefix">Am 08.07.2020 um 19:36 schrieb gus:<br>
</div>
<blockquote type="cite" cite="mid:20200708173657.GB5958@localhost">
<pre class="moz-quote-pre" wrap="">Dear Relay Operators,
Do you want your relay to be a Tor fallback directory mirror?
Will it have the same address and port for the next 2 years?
Just reply to this email with your relay's fingerprint.
Important: you have until July 23 2020 to reply to this message to get
in the fallback directory mirror list.
If your relay is on the current fallback list, you don't need to do
anything.
If you're asking:
Q: What's a fallback directory mirror?
Fallback directory mirrors help Tor clients connect to the network. For
more details, see [1].
Q: Is my relay on the current list?
Search [2] and [3] for your relay fingerprint or IP address and port.
[2] is the current list of fallbacks in Tor.
[3] is used to create the next list of fallbacks.
Q: What do I need to do if my relay is on the list?
Keep the same IP address, keys, and ports. Email tor-relays if the
relay's details change.
Q: Can my relay be on the list next time?
We need fast relays that will be on the same IP address and port for 2
years. Reply to this email to get on the list, or to update the details
of your relay.
Once or twice a year, we run a script to choose about 150-200 relays
from the potential list [3] for the list in Tor [2].
Q: Why didn't my relay get on the list last time?
We check a relay's uptime, flags, and speed [4]. Sometimes, a relay
might be down when we check. That's ok, we will check it again next
time.
It's good to have some new relays on the list every release. That helps
tor clients, because blocking a changing list is harder.
cheers,
Gus
[1]
<a class="moz-txt-link-freetext" href="https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/FallbackDirectoryMirrors">https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/FallbackDirectoryMirrors</a>
[2]
<a class="moz-txt-link-freetext" href="https://gitweb.torproject.org/tor.git/tree/src/app/config/fallback_dirs.inc">https://gitweb.torproject.org/tor.git/tree/src/app/config/fallback_dirs.inc</a>
[3]
<a class="moz-txt-link-freetext" href="https://gitweb.torproject.org/fallback-scripts.git/tree/fallback_offer_list">https://gitweb.torproject.org/fallback-scripts.git/tree/fallback_offer_list</a>
[4]
<a class="moz-txt-link-freetext" href="https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log">https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
</body>
</html>