Earlier quoted context omitted.
I disagree with this statement. We haven't pushed incompatible standards or any other nonsense. We've literally pushed out the latest standards and enabled more encryption (see Universal SSL making SSL free years before Let's Encrypt; see enabling IPv6; enabling HTTP/2; etc. etc.). As for HTTP/3... so will we. See: https://blog.cloudflare.com/http-3-from-root-to-tip/ , https://blog.cloudflare.com/the-road-to-quic/ an…
Fair point. I especially appreciate that even Workers is based on a W3C standard, when it could have been a proprietary API. However, Cloudflare has also adopted and promoted at least one standard that adds complexity for dubious benefit, specifically DNSSEC, which tptacek has repeatedly criticized (e.g. [1]). Moreover, Cloudflare is encouraging both providers and consumers to bypass the public Internet as much as po…
FWIW, tptacek's argument in that thread seems to be premised on certificate pinning being widely deployed[1], which it's not, and it seems at this point like it never will be[2].
[1]: https://news.ycombinator.com/item?id=10553608
[2]: https://groups.google.com/a/chromium.org/forum/#!msg/blink-d...