Hacker News Reader

Comment by nullindividual | Hacker News Reader

> thank you for your willingess to upset some customers and potential customers

Or, thank you for wasting your customers time attempting to figure out why one or more sites aren't responding appropriately on your network while they work on other networks.

Not everyone is clued into EDNS or why archive.is doesn't function with CF.

CF is wasting everyone's time.

View on HN

I mean, it's archive.is that is intentionally serving an incorrect DNS record (pointing back at Cloudflare's IPs) when it gets a DNS query that every other resolver handles just fine. They may have legitimate grievances with the info being dropped, but in the end they're the ones breaking their own traffic.

That seems like your much stronger older brother hitting you with your own arm and asking "why are you hitting yourself" over and over again though. Cloudflare is standing their ground with their morals, and Archive is standing their ground with their morals. Which one is right is for you to decide.

Easy choice: the one that’s protecting me, rather than themselves.

Without protecting themselves, archive.is wouldn't exist.

And given it is the subnet number being sent, NOT the IP address that people here claim, the privacy concern is fairly low (CF knows your IP address in order to deliver the DNS answer back to you and archive.is knows your IP address when you request resources).

I'll take the performance improvement that EDNS client subnet can provide.

Reply on news.ycombinator.com