News for hackers. Stuff that matters.
Re:1.1.1.1 for Families by fragmede on Thursday October 28, 2021 @12:20PM (#29027801)
Yes. From a technical standpoint, archive.is' stance is that it's actually important useful data that, more importantly, isn't a privacy violation. How much you agree with archive.is depends on a very technical understanding of the subject, or barring that, it depends on how much you buy Cloudflare's reasoning. Cloudflare's business would prefer you pay for Cloudflare (at large but specifically their anycast) instead of using an optimization available to you as a Internet business to route clients to a more optimal/closer server.

As far as the privacy implications, remember that the site you visit needs to know your IP address in order to respond to your request, so while there are some issues to be aware of, it's kind of hard to see it as a privacy violation and not Cloudflare trying to squash the little guy, imo.

Re:1.1.1.1 for Families by tomklein on Thursday October 28, 2021 @12:39PM (#29028029)
I coded a GeoDNS for a couple of my sites and Cloudflare‘s IPs are always geolocated to the nearest datacenters and works great in a GeoDNS setting.

Also, what about DNS resolvers that don’t support EDNS at all?

Re:1.1.1.1 for Families by tick_tock_tick on Thursday October 28, 2021 @01:45PM (#29028862)
The check archive.is uses to return garbage is specifically for cloudflare's IPs all other non-EDNS works fine. You can dig to there authoritative DNS server yourself to see.