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"
If we're losing our minds over ~20 active users, then we have way bigger problems than that instance.
EDIT: Just to be clear, I have no issues defederating with an instance like that. I just don't think it matters much either way.
Let's wait for per-user instance filters to be implemented, then everyone can block instances to taste. As long as their users don't cause trouble in our communities, there's no need for our instance to act as a moral guardians and decide what our users can and cannot see. Defederation is a nuclear option that should only be done if their instance is disrupting our instance's operation (spamming and breaking rules while in our communities).
I like that sh.itjust.works currently federates with almost everyone, and I can see a big part of the fediverse from here. It would suck having to visit multiple instance to see the whole fediverse.
Don't de-federate unless they're allowing the planning of violence, CSAM material, or actual abuse.
As a leftist I see it like this:
Blocking someone is: "I don't want to see this"
De-federating is: "I don't want you to see this"
Blocking someone is: Ignoring a person saying bigoted things.
De-federating is: Jailing a person saying bigoted things.
If you can't handle people saying shit you don't like then you need thicker skin. If you can't engage in a conversation with a person who shares an opinion that you fine distasteful then you need to seek maturity.
If you can't disagree with someone without physically attacking them, then you don't deserve to be part of a community. If you can't exist without abusing another person, then you don't deserve to be part of a community.
I’m as leftist as they come and I do not support this action. If you don’t want to see it, mute the instance rather than creating an echo chamber.
No, don't defederate. Just because an instance doesn't align politically with your views doesn't mean that they have to be gone. And we should definetly avoid a mastodon blocklist situation.
If you refuse to meet someone on level ground because you consider them intolerant of your own ideas, you're the one being intolerant.
@[email protected] 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?
Their answer is full of demagogia ... Its scary how its good...
If they start raid, or to be meaningful we can ban the specific communities or users instead of unfederate.
I really want to be able to read them (curiosity, see the new words their using etc ).
For now we should use reports functions and see how its going ?
