No. It's a long annoying dickfight between the two. And the reason it's annoying is they are both right, ish.
Actually Cloudflare is solidly more right, both because of what they are doing, why, and how they are open to finding some sort of compromise, and it's Archive.is who both have the weaker case to justify what they want, and explicitly give no fucks and unwilling to bother working with the other party on any sort of solution, and also what they are doing at the technical level is just technically wrong violating specs vs what cloudflare is doing is not.
archive.is wants the users ip for geo load balancing, cloudflare does not supply the users ip for privacy. archive.is returns intentionally and artificially incorrect results to lookups that come from cloudflare.
It's been the same for years now.
I am no Cloudflare fanboi even though I am using their dns obviously. It's just how all the factors shake out as far as I can tell.
This is told by Cloudflare ceo from their side, but it is also sort of the definitive explaination of the situation. But if you google cloudflare archive.is you can find countless other discussions and explainations.
Surely somewhere archive.is must have written up a version that paints themselves as righteous and blameless, but in the end I don't see how you can get around the base facts of who is doing what. The actions are how you tell the difference between the two sides.
No. It's a long annoying dickfight between the two. And the reason it's annoying is they are both right, ish.
Actually Cloudflare is solidly more right, both because of what they are doing, why, and how they are open to finding some sort of compromise, and it's Archive.is who both have the weaker case to justify what they want, and explicitly give no fucks and unwilling to bother working with the other party on any sort of solution, and also what they are doing at the technical level is just technically wrong violating specs vs what cloudflare is doing is not.
archive.is wants the users ip for geo load balancing, cloudflare does not supply the users ip for privacy. archive.is returns intentionally and artificially incorrect results to lookups that come from cloudflare.
It's been the same for years now.
I am no Cloudflare fanboi even though I am using their dns obviously. It's just how all the factors shake out as far as I can tell.
https://news.ycombinator.com/item?id=19828702
This is told by Cloudflare ceo from their side, but it is also sort of the definitive explaination of the situation. But if you google cloudflare archive.is you can find countless other discussions and explainations. Surely somewhere archive.is must have written up a version that paints themselves as righteous and blameless, but in the end I don't see how you can get around the base facts of who is doing what. The actions are how you tell the difference between the two sides.