I have zero interest in spending that much time wading through crap just so I can have the personal decision to block it.
this post was submitted on 21 Sep 2023
52 points (100.0% liked)
Chat
7499 readers
18 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
I have zero interest in spending that much time wading through crap
I have zero interest in keeping track of several accounts across several instances because someone upstairs doesn't like something posted on one of them.
Make your own instance then. As long as you're using a service someone else provides for you (free of charge at that), you have to play by their rules.
If making your own instance were something common for normal users, then I expect the federation would have to face thousands of single-user instances made by random people without ever being sure which ones are safe and which ones are just bots/spam/illegal-stuff.
A lot of instances would (understandably) want to disconnect from the fediverse if that were a common thing.... or at the very least they would use allowlists for federation instead of blocklists (in fact, some already do). So it would just result in more fragmentation, not less.
This means the process for your instance to initiate federation with all other ones would likely become more complex/inefficient than directly creating one separate user account in each of the instances you want to visit (if it isn't already).
I feel the issue is in the design of how the fediverse places so much responsibility in each individual instance... instances shouldn't be required to mirror third party content just so people can access it. It should be possible for people to simply connect to third party websites if they want to (with their home instance only acting as a sort of identity provider, like OpenID), without the home instance having to proxy/host that content if they don't approve of it.
load more comments
(3 replies)
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.
Flip side: imagine being a new Lemmy user, maybe coming from the algorithmically curated experience of Reddit, and having to learn what instance blocking is, how to do it and who to block. It would be quite overwhelming.
I'm all for user freedom but some users don't want freedom. They want something that works without having to spend 15 minutes configuring it.
How about a compromise? Each instance can define a blocklist of other instances they don't want, which is copied to the user's blocklist when they register to the instance. Then you give an option to the user to edit the blocklist.
This way you have the curated experience, but users have freedom to change it for themselves if they want to.
Totally agreed on that, it's actually a feature I'm working on adding to the UI fork I'm going to use for my instance.
It uses the admin-defined Fediseers preferences of an instance and hides content from users according to them.
Very good.
Also I checked fediseer.com, it's an almost perfect website, congrats.
Ahaha thanks but I can't take any merit for the Fediseer, that's @db0@lemmy.dbzer0.com's baby. It also has a nice GUI that - despite not being the "best motherfucking website" - is pretty cool to look at.
For some reason I thought your thing was part of Fediseer, but now I see it just uses it.
Good luck with your UI fork, I'll keep an eye out on it to see how it turns out.
Looks nice!
I’m all for user freedom but some users don’t want freedom
also that's what facebook is for.
I'd rather have that than massive instances with communities for things like fantasy sports and every possible country on earth and not have a way of curating that properly while also being subject to the whims of a few powerhungry admins.
It's why a lot of people praised the fediverse instead of reddit yet we're facing the exact same problems.
It is the virtue of the federation system that defederating does not deplatform or silence people. If you want to read content from a server that a server you use defederated from - it's still there. Just go make an account somewhere more open or directly on whatever instance you feel you're missing.
load more comments
(3 replies)
load more comments
(2 replies)
I chose my instance partly because of their anti-spam and defederation policy, so I don't have to do it myself. Imo instance blocking would be a nice feature on top, but not as a replacement. You can always switch instances or create your own if you don't like what your current instance is doing. I think we should rather improve that part of the system, so being able to easily move accounts and communities between instances.
Also, your instance hosts the content of federated instances for you (excl. images), and there is some stuff they just can't or don't want to have on their servers. That's just something you have to respect when using a service they provide to you imo.
Then you fundamentally don't agree with the principles behind federation, and the fediverse might not be for you. It's funny that you are mad and "want to curate your own browsing experience", but aren't willing to put in the effort to run a simple script (https://github.com/wescode/lemmy_migrate), pick an instance or a few that match your stance (they're out there and much more common than the niche Beehaw serves), or start your own instance.
Do you know how much effort being federated with spam factories / outrage machines generates for the mods and admins? When you depend on individual blocking, you get to click and forget about every bad actor or community. You don't see the ongoing hours that mods and admins have to pour in to dealing with that actor or community as they keep spitting out garbage.
Also, good thing you're on a very unlocked instance then. If you're mad about your instance doing whatever, then take it up with your admins, not Beehaw. Beehaw is a uniquely curated instance primarily intended to serve as a space where queer people don't have to get bombarded with non-queer people being ignorant. We deal with that enough in real life.
It's honestly more about the reddit-like drama it seems to create.
Funnily enough, this post kind of does the same and I am well aware of the irony in that.
Is that the fault of the admins, trying to stem a tide of reports and problems, or is that the fault of some users, not being willing to open a second tab in their browser? It sucks to have to maintain different accounts, but it's a lot less deleterious than the alternative.
I think if there were strong mod tools, your argument would make more sense (though I'd probably still disagree), but especially with the utter lack of mod tools, it just isn't feasible.
I don't see why those two features should be exclusive; both should exist and have their own purposes.
Defederation is for nasty instances whose users violate basic etiquette such as exploding-heads or hexbear. No tolerance for the intolerant.
Instance blocking should IMO be reserved for potentially disagreeable instances that aren't degenerated shitholes. Places that can behave themselves but are about topics a large portion of users might personally not like or aren't interested in such as feddit.de/nl/uk/it/..., programming.dev, startrek.website or lemmygrad.
Edit: Grammar.
load more comments
(10 replies)
I think one big reason for defederating is that a specific instance is creating a lot of work for the mods/admins because its users keep breaking rules. Instance blocking doesn't really help there.
listen, imagine a world where random people don't roll up on beehaw and tell them how to run their shit. just imagine!
Sounds like this whole Federation thing is going well huh
I don't like your idea because it defeats the purpose of picking an instance (and you could just run your own if you want to be in control) but yeah that was uncalled for. If this is the attitude of the instance maybe they should just defed. (If restricting posting isn't possible.)
The people hosting the instance are still responsible for the content being on their server, hiding it doesn't make that go away.
Pretty sure kbin has this feature.
It does but it's broken currently. If you block an instance yourself you'll find entire threads where none of the comments are visible to you, regardless of where those users are from. Not every thread, but enough.
The all feed would then be crap. I think you would have to filter or drop it.
Like the more control. You could never get rid of blacklisting or white listing as some stuff simply cannot be allowed on the node. On the other hand it could allow for more options in the gray area.
You may not want to under estimate the magnitude of the moderation issue too or the number of improvements needed or the lack of developers to address them. Lack of moderator actions federating is a good example and is just nuts. Frankly some sort of collaborative moderation would be great too.
This is like, my fourth account on Lemmy. Had to switch instances several times because they were defederating too much and I couldn’t get an unbiased all feed.
load more comments
(7 replies)
There are some instances which are better to block.
The only thing we cannot tolerate is intolerance.
See that's why it would be nice to be able to block them and not have to rely on those above to decide that for us.
When it comes to instances that are unmoderated and full of spam or oriented towards questionable porn, it's a better idea to defederate. Lemmy admins could face legal jeopardy for CSAM, spam bullshit can be a security risk. No reason at all to help host or spread that. As far as trolls/politics, I think it's reasonable for instance admins to decide whether they want to amplify and serve people say, some hateful content about hating minorities or accusing people of being "groomers" or whatever bullshit. If I ran an instance I'd have those people off my site pretty quickly. As far as instances that are just sort of provocative or have questionable political views, sure. Instance blocking (which is in the works, I believe) would take some pressure off the admins to defederate entirely.
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.
I love beehaw. It would be a shame for it to leave the fediverse and I believe it will fall apart if that happens.
load more comments
(1 replies)
Agreed, curious to see when it will be implemented.
view more: next ›