Even if it’s just a recommendation on a different group in which to ask the question, I’m curious how Lemmy combats criminal activity and content like human trafficking, smuggling, terrorism, etc?
Is it just a matter of each node bans users when they identify a crime, and/or problematic nodes are defederated if they tolerate it?
And if defederated, does that mean each node has to individually choose to defederate from the one allowing criminal activity?
to clarify, regular users cannot block other instances-- they can only block posts from other instances. users and their comments from those instances are still visible on federated posts/comments from other instances and must still be blocked individually. i have no idea why this feature was implemented this way, as it’s pretty much useless.
some 3rd-party apps provide better instance-blocking functionality that will block an instance’s users and their comments, too, but lemmy-ui doesn’t.
Nope, instance blocking was added with the last update.
Anyone can block whole instances for themselves.
sadly, this doesn’t seem to be the case. i have hexbear blocked, but i still see hexbear users and comments.
“instance blocking” should block everything from an instance. not just the posts, but also users, their comments, and their votes. just the same as defederation. since i already don’t see any hexbear posts because i’m not subscribed to any hexbear communities, this feature is useless.
Ah, yeah it only blocks the posts. Users still have to be blocked individually.
I don’t think that’s an issue really. Just because I don’t want to see the content posted there doesn’t necessarily mean I don’t care what they have to say on/about other peoples content.
You can still block problematic individuals, and if it’s bad enough your instance can defederate from theirs.
and we’re back to square one with why people wanted a “block instance” feature in the first place-- because many instances don’t want to defederate, even when one instance or another has toxic users. the answer was a “block instance feature” that does nothing. People want a way to block ALL users from an instance at once without having to deal with an instance admin who refuses to defederate or having to hunt down an instance that already has, forcing them to migrate. and not everyone has the resources and technical know-how to spin up their own instance.
a “block instance” feature that only blocks posts is useless since i wouldn’t ever see them anyway, as i’m not subscribed to any of those communities in the first place.
Speak for yourself.
The only thing I ever wanted block instance for was so my ‘all’ feed isn’t 90% porn from lemmynsfw.
Beyond that I’ve only ever blocked an instance to avoid its content. I don’t care about the users.
This current implementation is exactly what I wanted. TBH I think blocking the users as well should be seprate, for the reasons I described earlier.
Seems like we’d need both a way to block an instance posts only, and a way to block all posts, comments and users from an instance. Is it too much to ask? Did somebody open a feature request in github already (and has it been accepted or ignored)?
as you go on to speak for yourself… i’m just describing what a lot of people had been asking for (not just myself) as opposed to what’s been implemented. no need to get hostile.
Yes, exactly. I’ve expressed only my own opinion and been clear in that point, instead of presuming or implying that what I want is also what others want.
What I wanted has been implemented, and I don’t think it should be modified to include what you want. Instead I think blocking all users on an instance should be a separate feature/option as I wouldn’t use it myself, preferring to block the posts/content only.
I agree with your thoughts, that would be nice.