"Our decision today was that the risk created by the content could not be dealt with in a timely enough matter by the traditional rule of law systems."
Bad example, that was clearly them yielding to a lynch mob in the performance of its duties, as the saying goes. They clearly would've been content neutral in that case too, if the mob hadn't turned against them too.
Reacting to public outcry by cutting off a legal stressor?
I just don't think it's that big a deal.
Being hosted on someone's private server is a privilege, not a right. As far as I know the host is legally responsible for the material they dispense.
In the abstract, I believe everybody should have access to web hosting. But upholding that mission is not the job of one private company.
Anyway, I guess "content-neutral" is an easier sell for most people than "We will 99 times out of 100 let you be even if you're pretty out-there, unless people start suing us about you and it's pretty plain to see you might be a degenerate force on the social internet, in which case yeah we'll tell you to beat it".
Like, it's not a power that should be exercised liberally. But be real. It's Kiwifarms. Businesses have a right to refuse service to recreational gangstalkers
cloudlfare is not hosting - they are DNS against ddos.
Without internet or dns your hosting doesn't matter.
I know they have added additional services and you could say that they offer a type of hosting and domain names and other such stuff.. but generally when place get kicked from cloudflare, it is not their web host.
I would also say that they know pretty well when they kick someone from the dns protection that they are going to be bombarded with ddos and other issues that will take them offline more than likely.