Yes.. 'this'.. where the arguments from censorious retarded faggot Matthew Prince are refuted like
a page down.
The simple fact is that Cloudflare's DNS is yet another trojan horse in their stable of trojan horses. In order to sabotage more trustworthy CDNs, they remove essential information from what is passed to archive.today's DNS servers. By removing that essential information, they can make it impossible for anyone hosting content outside of Cloudflare to do their own geographic loadbalancing. This is a deliberate, malicious choice by filthy shyster Matthew Prince.
The operator of archive.today inquired about this malicious blocking of essential information, and, after they stonewalled him, simply blocked Cloudflare's broken DNS servers.
Note that the privacy 'argument' that Prince gives for this deliberate breaking of DNS standards is 100% specious. If your computer is sending DNS requests to figure out what is the appropriate IP to communicate with 'archive.is' on, what is the exact next thing that you are going to be doing, 99.99999999999999999999999% of the time? Oh yeah, communicating directly with whatever IP it is that you get back.
Is delaying the crazy Russian from learning what subnet you're on by 50 milliseconds a 'privacy gain'? Noone in their right mind could honestly suggest that. Of course, if Cloudflare were considering launching some kind of 'service' where all your traffic went through their servers to be backdoored, rather than just most of it, that would make a lot of sense. Then you just have to trust Cloudflare to keep you safe! (If you trust Cloudflare to keep you safe, you are retarded)
And that's how we know that censorious monopolist Matthew Prince (@eastdakota) is a lying piece of shit.