I wonder how we could improve the structure of the Web to ameliorate this sort of problem. It seems like Cloudflare is too central to this structure to be able to satisfy everybody simultaneously.
Cloudflare has always sidestepped their responsibility by claiming not to be a "hosting provider". They claim not to host the content, so they claim not to be able to stop any abuse related to it. If the DNS points to cloudflare, if the content to the rest of the world looks and feels like it comes from Cloudflare, then you're responsible for the content whether you consider yourself a "hosting provider" or not. Providing bullet-proof hosting to scammers, spammers, etc. and then ignoring abuse reports and throwing their hands up in the air because it's not their content has left a pretty terrible impression of Cloudflare to me.
> many people did not read or understand the disclaimer and were surprised that we forwarded their full abuse report to the host who then, in some cases, could forward it to the site owner.<p>It's a bad idea to engage in lawfare [1] (in this case, spamming abuse forms to pressure a host/CDN into stopping providing services to a given website) without being familiar with the functioning of the mechanisms one seeks to exploit.<p>[1] I don't use this term pejoratively.