Which is what exactly? The default being to have a uniform service across all asset types seems sensible enough to me. It's either that or everything is off by default and you manually include paths/expressions that are included. The latter seems more of a hassle for most people.
> Isn't "this stuff is hard, let us figure it out for you" CloudFlare's entire value proposition?
I'm not sure what their angle is. As far as I can tell it's to re-centralize the internet so they can be the single tap point where SSL is added and removed[1]. Once they've got a sizeable chunk of the world funneling through them, they could make some decent coin giving direct access to the feds.
Until then, it's just free SSL and DDOS protection. Can't really complain against free either. Heck just don't use it.
[1]: http://www.newyorker.com/wp-content/uploads/2013/11/nsa-smil...
That really is not a viable option when you want to access content which happens to (now) be behind Cloudflare.
Sure it does. Vote with your bytes and move along.
Odds are the nntp client in question should customize the user-agent, and a request made to Cloudflare to improve the ranking for that agent... that's about the best that can be expected here.