The admin of sh.itjust.works has been approached but as of yet has failed to reply to concerned Lemmy users. I’m glad Beehaw admins look out for us by cutting off instances that host communities like this.
this post was submitted on 23 Jun 2023
321 points (100.0% liked)
Chat
7499 readers
23 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's really an issue with how the fediverse handles communities. On Reddit each sub had its own moderation/governance structure which I think fits the role of an "instance" best. Here, each instance has a variety of communities which may overlap with other instance.
I.e. banning an instance for having community X impacts community Z who may also dislike X.
Without ripping up the floorboards, I suspect the answer is instances having community-level granularity in blocking. So one can block: The_Donald@*, *@sh.itjust.works, or most narrowly The_Donald@sh.itjust.works
From a fellow instance administrator; does anyone know if it's possible to block a single community across your whole instance rather than defederating it? E.g., is it possible for me to block "HateSpeechCommunity@*" or "HateSpeechCommunity@domain.ext" as opposed to defederating all of "domain.ext"?
Specifically, we would love to ban "The_Donald@sh.itjust.works" from our instance without having to blanket ban the server, as there are some communities on this server (e.g. gaming@, etc) that we do actually want to interact with.
I'm aware that I can block the community on my own user account, but not sure if I can block just the one community from showing up on my instance altogether.
It is possible. Yes. This was confirmed in the sh.itjust.works thread on the same topic by an instance host. He said that you just have to mark the community as "removed" and then no one in your instance can see it. Except admins, probably.