andyprough wrote: ↑2025-02-14, 05:41
sites that Schestowitz doesn't feel are worthy of getting any traffic at all anyway. He may, in fact, be quite happy that Cloudflare is locking people out of sites and may be hoping that Cloudflare locks a lot more people out of sites until they've destroyed the traffic to all their clients' sites. Which - actually - is kind of hard to disagree with.
Certainly a point to make, but at the same time there's the critical question to ask which is more likely: that people simply stop visiting the sites "protected" by CloudFlare, or that they will use a different browser that "just works everywhere"? Maybe you could find people that will do the former for a few sites that run into the problem, but with CloudFlare being as pervasive as it has become, it'll become a pretty big sacrifice for a lot of people to make -- and the bottom line is some people will, and some people won't; net result being the smaller browsers lose a chunk of the small market share they already have, losing income, and just being squeezed.
andyprough wrote: ↑2025-02-14, 05:41
This entire business model of running a mafia-type "protection" racket at exorbitant fees for websites is quite obscene when you think it over.
I absolutely agree, and they didn't start out that way. This is something from the last few years where they really started clamping down on the "protection" side of things. Their primary reason-to-be was initially proxying and caching for performance reasons, with the "protection" just being inherent for being behind a public-facing proxy IP.
Over time they tacked on more and more and more additional features in the paid tiers that are actually mostly niche use for normally catered installations of big companies, and going big on big traffic data as well. "generating value" is the keyword I think that was driving all this, not "providing a service".
Having run our project servers without their "protection" it does get us the occasional issue with attacks or overloading the servers with automated traffic that require some administration (because I've made it a point to go fully unmanaged VPS so it's all in my own hands, but that was my choice; I didn't have to), but for websites that are using a decent hosting company, that could easily be taken care of by the hosting experts who deal with traffic and abuse daily. I can also say that the abuse has been less than what I saw in their reporting at the end of my usage of them, so I think CF was already starting to block legitimate traffic and misreporting it as "bad", back then. So what I'm saying is,
most webmasters don't actually need all this - and also keep in mind that's not all there is to it. Using CF you are giving them control of your DNS, TLS certificates, and more. Not to mention that all traffic flowing to your websites goes through CF and all data is fully exposed to everyone the traffic passes by in their reverse proxy network.
But on the other side it's "easy" to use CF. And many, many people fall for the "it's free and easy" angle for the lowest tiers CF offers (including the paid "pro" which is more like a "not entirely just a demo" tier). Nothing really to be done about that except inform them of the consequences.