this post was submitted on 15 Jun 2023
345 points (99.1% liked)
sh.itjust.works Main Community
7730 readers
1 users here now
Home of the sh.itjust.works instance.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Read access should be managed on the user level, not the instance level imo. I don't want to inherit some collective blacklist, I want my own.
For write access, it's more complicated and I'm not sure what to think.
Kbin (I'm on kbin.social) allows users to block entire instances, rather than leaving that entirely up to admins.
When an instance has a specific rule, no NSFW for instance, it can't be receiving that content from other instances and serving it to its users because it breaks its own rules. You might want NSFW content but your instance's users agreed to that rule, probably because that's what they wanted out of the instance.
The problem is that read access for a user means the content is cached on the instance of that user, making the instance owner potentially liable if we are talking about content illegal in their jurisdiction.
Good point, I hadn't considered that. But an instance can still strive to keep its blocklist as small as legally possible. This wouldn't be a big issue in most liberal countries anyway I think.