3 ms·
Cloudflare should take action on reported domains and their owners, especially if those domains are malicious. However, I don't want Cloudflare to preventative
by jeroenhd 4y ago
Cloudflare should take action on reported domains and their owners, especially if those domains are malicious.
However, I don't want Cloudflare to preventatively police what is and isn't a bad website. When these scam sites go live, they can quite easily contain real content (say, a blog, with articles written by AI good enough not to be immediately obvious) and then change into malware on a schedule.
Cloudflare can't see what code customers run on the backend and that's probably a good thing. They're already holding too much power over the internet and requiring the backend to be transparent would only make them more in control of the web.
Any registrar hosts thousands if not millions of spam sites because every single one of the billion registrars have DNS set up in some way.
Despite being almost exclusively used for spam and amateur projects, the .TK TLD barely shows up in Google. Spam sites are a symptom of other services linking to them and making them worth the investment. If Google, Bing, Qwant and Yandex weren't falling for the SEO scams these scammers use, we wouldn't have this problem.
Hosters have some immunity by design, and that's very much a good thing. They have to respond to abuse complaints, but they're not responsible for filtering out all of their customers. Requiring them to do so is exactly what the EU is trying to force upon the internet, which is terrible for online freedom.
- RockRobotRock 4y agoYou make some good arguments, but if a site is caught in the act of hosting obvious malware, Cloudflare should make a reasonable effort to suspend their activity.