Hacker News Reader

the opposite is the case. from your link: "Archive.is’s owner is intentionally blocking 1.1.1.1 users"

The archive owner wants takedown requests to be forced to be cross-border, so he wants to know where the request is coming from so he can serve from a server in a different country.

Cloudflare blocks the extension to DNS that allows that. If you don't care, you can set your DNS to bypass Cloudflare for those domains only.

I’ve known this for a while now but it never ceases to amaze me. This must be up there with “no copyright intended” in terms of misguided compliance strategies.

It's always appeared to be a matter of perspective, to me.

That being said, by "Cloudflare has issues with archive.is" I very literally meant that they have issues with the DNS records served to them by Archive.is. (i.e. They do not support EDNS.)

Reply on news.ycombinator.com