this post was submitted on 01 Sep 2024
326 points (99.1% liked)
Fediverse
28489 readers
768 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's gotta be some kind of limited liability for this kind of thing. I mean, banks wouldn't be liable if someone put csam in a safe deposit box or (assuming they don't x-ray packages) UPS shipping csam in a sealed package. I think there just needs to be reasonable safeguards against it but I don't know if any of that is built into the software.
Issue here is that what’s in a safe deposit box isn’t also being shared/distributed. It is locked away.
If, however, they made copies of the contents of a box and put it in other boxes … and it came out somebody used that for CSAM then there probably would be some kind of liability.
Besides CSAM there’s also copyrighted material, etc which section 230 kind of covers but even then gets tricky since there’s a duty to respond to DMCA takedowns in order to get safe harbor protections.
It'd be a little more like someone going to a Kinko's (or whatever like that exists anymore) and using their copiers to copy CSAM.
Exactly. And in such a scenario it becomes an issue for Kinkos
I could also see this turning into a form of DoS attack. I'm sure there's very little leeway in ignoring "bad faith" reports so if you have an instance you could be responsible for investigating thousands of reports per day. And if you take the safe route and remove anything that's reported, until deemed safe, you might as well turn off your instance.
Unfortunately we are at a point where Cisco Cloudflare and Google are held liable for filesharing-related domains their DNS relays are resolving IPs for...