[meguest]

Is this sarcasm?

[dogecoinbase]

Presumably, but they have a poorly-articulated point -- Cloudflare has an incredible potential for (even unintentional) destructive effect based on their extreme consolidation and centralization of internet technologies. I think a terrific example of this is when they put a DNS server on 1.1.1.1 (in historically unused address space which was assigned to APNIC for research purposes), got a certificate for the IP address, then added that certificate to the Chrome HSTS preload list, meaning people who ended up on captive portals on 1.1.1.1 (and there are a _lot_ of them) couldn't access the internet, because instead of observing what people _actually_ do and paving the cowpaths, they took the point of view that acting against the standards was punishable, and the people being punished are nontechnical folks visiting hotels and airports who are using a modern browser (it has since been removed from the preload list, but if you're foolish enough to visit the site you'll still get HSTS-poisoned).

An even better example, of course, is Cloudbleed, but I guess we've all agreed to pretend that never happened?

[bogomipz]

Thank you for articulating these points, agreed. They seem to have an insatiable desire to "become" the internet. I also find it bazaar that their CTO submits every single one of their blog posts to HN. This is the 16th Cloudflare blog post they've posted to HN this week. You would think they might have a marketing budget.

[wink]

Yeah, that's also why I don't like this. Cloudflare showed a lot of positive things, but also what you just mentioned. Centralization and the 1.1.1.1 preload thing. Cloudbleed was bad, but I'm not sure it wasn't just "a bug" like every big company had, this just happened to have a big fallout.

[Operyl]

On the other hand, 1.0.0.0/8 is routable ip space on the internet. I get that it sucked, but, would people have stopped "squatting" for lack of a better way to say it had they not added 1.1.1.1 to the preloaded list?