47
Programming.Dev Feature Requests
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Aug 2023
47 points (100.0% liked)
Programming.dev Meta
2466 readers
5 users here now
Welcome to the Programming.Dev meta community!
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
Links
Credits
founded 1 year ago
MODERATORS
I've always felt like the blocking should happen at the user level and muting should be at the instance-level. Feels odd for admins be able to prevent users from seeing content.
My understanding is those admins aren't just allowing users to view it but also allowing copies of the federated data to be stored on the server those admins are responsible for, so for certain types of content it seems really important to be implemented in this way.
We're talking about blocking all content on an instance though--not necessarily a few nasty communities or posts or users. Blocking an instance blocks all content, including non-offensive content that may be posted by legitimate users.
For an admin to block everyone on an instance from all of their users just because of a few bad actors still seems weird to me. It's just gonna lead to every instance blocking each other, which destroys the experience for users and defeats the point of federation.
Good point and I agree with the downsides. Giving admins more granular ways of hiding content sounds healthy.
There’s also the important distinction between admins finding opinions on the other instance “disagreeable” and muting vs. illegal content in the instance server’s jurisdiction and those of the admins. Defederating the whole instance does seem harsh if the problem is within specific communities only and doesn’t deal with illegal content.
Difficult problem!