Threat/abuse tracking, History/Geopolitics thonking, Misinfo/Grift fan, PDX based
openpgp4fpr:EC93911D412ACAE8779B8222588C793376B5F13C
Will this stand up to the death of Chevron deference? Or are we 3 weeks away from a judge throwing the rule out unless congress passes a specific law.
I think this is squarely in the charter of the FTC but who knows with the courts any longer. We just saw them strike down a ruling by the EPA to enact health measures under the requirements of the Civil Rights Act.
There’s a balance to be struck here but Cloudflare is truly the most miserable entity I have to work with from an abuse perspective. They’re not necessarily “ignoring” warrants but most phishing doesn’t get reported with a legal takedown request. In those cases, Cloudflare will be almost intentionally obtuse. I’m happy to outline the misery of a host working with Cloudflare but it’s not necessarily important to this. TLDR; Cloudflare takes steps that don’t make sense for its “we’re not responsible” stance while also having zero automation in the year of our lord 2024.
I suppose everything could be a legal request but that just makes the whole process so infinitely worse for NGOs like Spamhaus and only serves to make lawyers excited that their consultation fees are going up. I see that the laziest pathway is “Youtube-like strikes” which is misery as well but they could just shift to investigating accounts receiving a high volume of reports as potential fraud or abuse actors since it is a drag on their services and these accounts are not paying or are paying with stolen credit cards.
Ultimately, I don’t disagree with you that much but there’s a lot of room for CF to improve their management of fraud & abuse without becoming a trash platform or invalidating legal protections. Happy to get into the weeds on this a bit more since it’s a lil’ bit close to home. 😅
It’s a bit more about how miserable it is to work with Cloudflare and their unwillingness to remove abuse in general, opting to say they’re “not the host” and that they cannot tell you where it is but they cannot do anything. It’s hardly an ethical decision to say that phishing and bulletproof hosting aren’t the bedfellows you want.
I don’t really disagree with you at all but repeatedly reminding us all that you’re “not surprised” isn’t the savvy commentary you think it is. Especially since it’s historically been the case that any service you pay money to has said “no, you own your content”.
The marker has just moved gradually on this with companies slowly adding more ownership clauses to their Terms of Service in ways that aren’t legible to average consumers. Now they’re cashing in on that ownership.
While you’re not wrong, the social contract we’ve adapted to is that paying means you have some sense of ownership. It’s unreasonable to expect folks to read every Terms of Service with their legalese. Perhaps the new reality we need to accept is that there is no such thing as a good actor on the internet.
You pay for WordPress.com though. That’s crazy to offer a paid service and use that data in AI training.
I think you’re mostly right but there’s a host of nuance and legalese that muddies this up. Social media is always in a conflicted relationship with speech, wanting to have no culpability over what’s posted while also making decisions over what to feature/restrict/etc. They’re actually really cautious to not position themselves as the “town square” for that reason since it does channel a sort of legal definition of such.
Having worked at a cloud provider for awhile and also done support, the reasoning is generally that Ubuntu is the “path of least resistance” to getting running. They have a super engaged community and the market share leads to a lot of guides across the web being primarily made for Ubuntu.
To be fair, it also helps that their LTS support is really nice and their repos are a lot closer to up-to-date than a bunch of others.
Such a strange feud. Aren’t there a bunch of WordPress hosts that are given usage of the software name? It sounds like there’s just something specifically about WPengine’s deployments that are changing the formula, creating a sticking point.