Cloudflare and co offer some of the only real solutions to that.
If you snap your fingers and Cloudflare disappears, you aren't left with a decentralized wonderland but rather the status quo where $5 of booter time can take most websites offline for the lulz, and all of your human users have to compete with infinite automated AI traffic (basically an amplification attack every time someone prompts an agent and it does a web search).
So, there's a third option where you like Cloudflare's services as a solution to flaws in the internet that led to the need for these services.
- The workers platform is quite pleasant to work with compared to competitors. - Globally deploying edge workers which have access to their many services (D1, R2, DO, etc) - Having the ability to assemble globally distributed workers using bindings is dead simple - Their CI pipeline, while limited, is easy to setup and run and keeps improving - Their pricing is extremely competitive
For your second:
- That's my biggest conflict with using any service (Cloudflare, AWS, Azure, etc). Don't have a good answer with what to do about it considering for many projects I don't have the time/energy to fully self host everything.
Absolutely, makes blocking stuff so much easier!
Cloudflare has some big misses in it's history, like deciding to takedown a social media site for sex workers while defending a decision to provide services to Nazis at length, but in comparison to the alternatives it makes more decentralization practical than might be otherwise.