Then turn off nsfw content.
Or turn off media displaying.
You have options that aren't thinking you can dictate how people use instances. Or join/host one that outright bans porn if you want.
conciselyverbose
joined 1 year ago
Why would you need to go to a NSFW focused instance? I could see complaining about the sub, but the server? That's nonsense.
There are reporting features. In most jurisdictions, accepting reports and acting on them is plenty sufficient to meet any legal obligations, and many consider scanning every message unnecessarily invasive.
I don't, and literally everything on here is public, so it's not identical, but look at the response to Apple's proposed (otherwise privacy preserving) CSAM scanning on cloud photo backups.
The protocol and software don't. It's open source and anyone can use it.
Instance admins can block servers that allow anything that's illegal (or they otherwise believe is inappropriate) .
It's not. There's no evidence for any harm of any kind from THC or the other psychoactive ingredients in adults.
Smoking, specifically, yes, but there are many, many other ways to ingest it, and smoking is most common in large part because of the backwards ass laws.
It's not like alcohol, where the desired altered state is exchanged for fucking up your liver, kidneys, etc. It doesn't do any of that, even with extremely heavy use.
I'm assuming this one is because he's just going to tell them to fuck off.
There's no legal basis to take it down.
The only thing that matters is that (in adults) it's very clearly demonstrated by abundant research to be perfectly harmless.
In and of itself, the lack of harm makes it impossible for you to be a redeemable human being if you want to tell a consenting adult that they can't have it.
That's ignoring all the evidence supporting benefits.
It kind of looks like his point was the dozens of forks and that even if the devs get harassed into stopping, there are alternatives sources for the same app.
GitHub (and everyone else) is required to follow the process laid out DMCA takedown requests. The uploader just has to submit a counterclaim, and they can put it back unless they actually go to court and file a lawsuit.
The whole process is dictated by the DMCA.
GitHub didn't do anything. This isn't because the code was taken down (it's still there, as are all the forks that are also perfectly legal); it's because the maintainers decided it wasn't worth putting up with big pocketed harassment to keep doing it.
It's not copyright infringement, so you can just tell them to fuck off and make them sue you. If they submit DMCA, you (and because it's open source, that means anyone, today) can counterclaim and it will get put back up until they actually go to court.
It's just a lot to deal with harassment from a motivated company's resources.
It's a reader app that supports extensions.
These extensions can be used to parse piracy sites, among other things, so a publisher went apeshit and harassed them into saying "fuck it".