Hacker News new | ask | show | jobs
by Shank 140 days ago
It is academically very interesting to think about this in light of their long-standing dispute with Cloudflare (https://community.cloudflare.com/t/archive-is-error-1001/182...) over EDNS, which could have privacy implications attached.

I think no matter how you slice it though, it's unethical and reprehensible to coordinate (even a shoddy) DDoS leveraging your visitors as middlemen. This is effectively coordinating a botnet, and we shouldn't condone this behavior as a community.
1 comments
qmarchi 139 days ago
It's definitely interesting to see this roll around since the only individuals that see the CAPCHA page mentioned, are users of Cloudflare's DNS services (knowingly or not).

P.S. Shout-out to dang for dropping the flags. I have a small suspicion that their may be some foul play, given the contents...

link
greyface- 139 days ago
> the only individuals that see the CAPCHA page mentioned, are users of Cloudflare's DNS services

I don't think this is true. I run my own recursive DNS resolver, and get a CAPTCHA when visiting archive.today.

link
k33l0r 139 days ago
I use my ISP's default DNS servers and have consistently gotten the CAPTCHA page for weeks now. The CAPTCHA seems to be broken too, rendering archive.today entirely inaccessible.
link
Hamuko 139 days ago
Someone has suggested that CAPTCHA is broken for everyone in Finland.
link
cluckindan 139 days ago
Not surprising considering the service is operated by Russia.
link
Zanfa 139 days ago
Seems to be the case in Estonia as well.
link
mhitza 139 days ago
I see the captcha all the time for the Tor onion website as well.
link