Consider changing the fallback process to opt-out

If we did this, we could rebuild the list by running a script, and occasionally collect opt-outs and add them to the blacklist.

I don't think this would worry anyone too much.

changed milestone to %Tor: 0.3.4.x-final in legacy/trac

added component::core tor/fallback scripts in Legacy / Trac fallback in Legacy / Trac milestone::Tor: 0.3.4.x-final in Legacy / Trac points::1 in Legacy / Trac priority::medium in Legacy / Trac resolution::wontfix in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac labels

I am strongly discouraging this. Distributing the IP address in source code can get them flagged by some "security" software as C&C server (happened to my dirauth, caused a bunch of trouble but people knew to talk to me). We tell non-exits they basically don't have to worry about running a relay and I think that's no longer true with an opt-out process.

Thanks for this feedback, it looks like we will need to continue to find someone to run this process in future.

Trac:
Resolution: N/A to wontfix
Status: new to closed

Un-parenting this ticket because it's done.

Trac:
Parent: legacy/trac#24786 (moved) to N/A

Remove useless CC

Trac:
Cc: teor@torproject.org to N/A

closed

changed time estimate to 8h

mentioned in issue legacy/trac#26502 (moved)

moved from legacy/trac#24789 (moved)

added Bug label and removed 1 deleted label

added Fallback Directories label and removed 1 deleted label