As I've found with Cloudflare-backed sites: Tor and non-JavaScript tools equals no access.

This includes both console-mode browsers and shell-based tools such as curl or wget.

I find this surprising seeing as cloudflare blocked me on shared wifi while traveling internationally from accessing many sites, claiming it was to prevent email spam. They were blocking more sites than over zealous hotel and government internets. When I started a thread about how they were blocking from a significant percentage of hotel and coffeeshop wifi's in various countries their response was find other wifi. Really seems like you need to turn down the filtering.

Good. Please stop serving captchas to every tor user then.

Not what I was expecting based on the title. But it is an important principle that should be more widely followed. Good on them.

Would it be possible to make options available to customers to select what type of compatibility they would like to strive for?

What if I am okay with not supporting Android 2.x which doesn't ciphersuite Y?

Is this in response to something?

Nice, but what does this mean for CloudFlare specifically? It's usually not CF but their customers who make websites that are heavy to download or render.

Is it things like continue to support HTTP 1.0/1.1 and older ciphers when required?

couldn't help but look at that pic of the Berners-Lee Mosaic and think...this is for everyone, unless you're in places like...India...Eastern China...Australia..actually all of Asia-Pac...haha. ;-) ;-)