@[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?
Coming from sh.itjust.works. It seems there is a pattern of some attacks to forcing defederating some lemmy instances. Those threads can be found on both sh.itjust.works and lemmy.world. There are several vocal users dominating those threads (some reaches 20+ comments in the same thread). Those user whose complaining user has total against, and already hostile to the instance they dislike, and interact to the other instances with bad faith, provoking, and insulting those instance. I believe this is some sort of coordinated pattern to break fediverse into echo-chamber.
IMO, defederation should be used as last resort, because normal user, especially seeking small niches, will be affected the most. In case of beehaw, there are tons of factors that are justifiable. I wish this defederation drama is not become the defining feature on both lemmy.world and sh.itjust.works.
I believe individual user can block communities and users, plus block instance feature is in the works. I wish the people who starts those threads can just do that.