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.
Defederation is your instance doing the instance blocking. Regular instance blocking is you doing it from a user level and doesn’t affect other users. There’s many reasons why things should fall under one or the other. If an instance does not defederate, another server’s (potentially illegal) content can get cached on their servers for example, or enable a lot more spam. This also is during the recent CSAM attacks so admins are a lot more wary.
The people hosting the instance are still responsible for the content being on their server, hiding it doesn’t make that go away.
On connect it let’s you ban instances. It will overwrite comments from that instance with 'this is blocked due to use being from instance x. Gives an option to show the comment anyway (if the context is different Fi)
I love that feature
I don’t think it should replace it but it should be an option.
I’m sympathetic to the idea that an individual user should be able to override their instance admins’ preferences on access for content-related reasons, but I don’t think it would be workable from an administrative viewpoint to allow users to allowlist instances that were blocklisted for administrative reasons.
Lemmy.world dealt with (and is probably still dealing with) a series of malicious actions designed to actually bring down the service or otherwise tie up its resources (including moderator/admin attention and effort, and exposure to literal criminal charges), using maliciously crafted requests to bring down servers, literally illegal content posted to their servers, etc. Defederation in response to these types of attacks would be defeated if a user could let the content come through anyway.
I imagine most instances are dealing with similar issues.
So ideally we’d need to be able to create 4 categories of relationships with other instances:
- Blocked no matter what
- Blocked by default for users, can be user overridden
- Allowed by default for users, can be user overridden
- Allowed no matter what (not sure what the use case for this status would be, but seems to be trivial to implement since it already exists as default).
But I think you’d find that the typical scenario that justifies blocking would actually put the typical block into category 1, not category 2.
