You are viewing a single thread.
View all comments
31 points

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.

permalink
report
reply
12 points
*

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.

permalink
report
parent
reply
12 points

Kbin (I’m on kbin.social) allows users to block entire instances, rather than leaving that entirely up to admins.

permalink
report
parent
reply
7 points

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.

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply

sh.itjust.works Main Community

!main@sh.itjust.works

Create post

Home of the sh.itjust.works instance.

Community stats

  • 963

    Monthly active users

  • 432

    Posts

  • 11K

    Comments