this post was submitted on 21 Sep 2023
52 points (100.0% liked)

Chat

7499 readers
8 users here now

Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
remington@beehaw.org
52
Instance blocking should replace defederation (lemm.ee)
submitted 1 year ago* (last edited 1 year ago) by HerbalGamer@lemm.ee to c/chat@beehaw.org
64 comments fedilink hide all child comments
 

Think about it; instead of those in charge or the instances deciding who they don't want to be federated with and thus restricting content for the users, it would be better if users were able to block entire instances instead.

We'd be able to curate our own browsing experience so much better without admin/mod drama influencing the rest of us.

Edit: Alright so maybe not exactly replace defederation, but it should still be an option available to us, and in general should become the default action before defederation IMHO.

you are viewing a single comment's thread
view the rest of the comments
[–] Ferk@kbin.social 2 points 1 year ago* (last edited 1 year ago)

I mean, federating with an instance doesn't necessarily mean you NEED to have it added to the default feeds.

It could theoretically be done in such a way that it only shows content from the communities you are subscribed to, and never show content from that instance in general feeds, for example.

Or it could even be done in such a way that instance blocking is enabled by default for every user, and each user has to opt in to see content from other instances outside of maybe a selected curated few that might be allowed by default.