5 ms·
They could run their own stackoverflow .onion service and advertise it in the site headers [0] (including on the block page). Then the onion traffic can be han
by snthd 5y ago
They could run their own stackoverflow .onion service and advertise it in the site headers [0] (including on the block page).
Then the onion traffic can be handled differently (maybe DDoSing the .onion will only affect Tor users, or the resulting .onion resource usage is throttled). Worst case a readonly version of the site would be better than nothing.
Something similar could be done with the existing tor exit node blocklist, but maybe this is easier to separate from existing infrastructure.
[0] https://community.torproject.org/onion-services/advanced/onion-location/ https://community.torproject.org/onion-services/advanced/oni...
- admax88qqq 5y agoYes they _could_ do a bunch of engineering and infra work to support a niche use case.
- YesThatTom2 5y ago(Your sarcasm may have been too subtle for the average reader.)
- BatteryMountain 5y agoWhat do you mean?
- z3t4 5y agoAt stack overflow scale a "niche" use case could mean more users then your average web site.
- soheil 5y agoWhatever is deciding if the traffic is tor or not can get ddos'd too.
- junon 5y agoEh? That's not how hidden services work.
- soheil 5y agoIt's pretty trivial to find the list of running tor exit nodes.
- boring_twenties 5y agoExit nodes are not used to connect to hidden services.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]