Comment by rafram
20 days ago
Remember when Archive.is/today used to send Cloudflare DNS users into an endless captcha loop because the creator had some kind of philosophical disagreement with Cloudflare? Not the first time they’ve done something petty like this.
It wasn't a philosophical disagreement, they needed some geo info from the DNS server to route requests so they could prevent spam and Cloudflare wasn't providing it citing privacy reasons. The admin decided to block Cloudflare rather than deal with the spam.
Had nothing to do with spam, the argument by archive.today that they needed EDNS client subnet info made no sense, they aren't anycasting with edge servers in every ISP PoP.
They use EDNS for regional compliance, not for bandwidth optimization.
6 replies →
That's still a thing. Happens to me as we speak.
For me it just doesn't resolve at all on Cloudflare dns. So annoying.
[dead]