Home of the sh.itjust.works instance.
The instance seems to be mostly right wing trolls. I know defederating is unpopular but I don't think much is to be lost in this case and it can save the mods some headaches.
Edit: the response on exploding-heads.com to my reporting of transphobia. Courtesy of the "second in command"
@Alue42@kbin.social I can't reply to kbin.social users so I will say it here.
For your information. If sh.itjust.works defederates from exploding-heads, only those users on those communities will be affected.
Kbin.social won't. The users there still can see both sides and interacting with both sides regardless sh.itjust.works and exploding-heads defederates or doesn't. A simple example, kbin.social people can still interact with beehaw.org, right? We here can't interact with them at all. Some already made another account on another instance.
So, people on Kbin.social should not having voice on dispute between these two communities because it has no impact on them.
Why NOT kbin.social that defederates from exploding-heads then? Why MUST sh.itjust.works? Yet I see four or more accounts from kbin.social try to do discuss this thing. Why you guys from kbin.social try to do this?
I was also kinda surprised that sh.itjust.works doesn't block exploding-heads as most instances I'm aware of do. That coupled with the fact that the instance doesn't block them but blocks lemmygrad made me think at first sh.itjust.works was going to be some far-right instance, but from what I've seen it isn't. Though, I don't understand why sh.itjust.works would want to federate with them, considering their content often violates the rules of the instance.
I personally think defederating shouldn't happen generally. I'd rather there be customizable user filters for either words, subjects, etc.
Like I'm not really into their content (or that of some other instances) but defederating at an instance level is kind of a giant hammer for the few folks who may (for better or worse) be interested in both instances.