What defederating would mean:
- We won’t see beehaw.org posts/comments on other instances.
Pros:
- There is less confusion, you can’t respond to a beehaw.org user, thinking they will be able to see your response when in reality they cannot.
Cons:
- We won’t be able to see any beehaw.org comments/posts on other instances, so we will miss out on some comment threads and posts. It could be good to be able to see them and interact with the other users there even though beehaw.org users won’t see any of our content.
Summary
Overall, I think it is better not to defederate, but simply unsubscribe from all of their communities (and as we no longer get posts from their instance, with time these will cease to appear on our ‘front page’).
beehaw.org users already can’t see our posts/comments anywhere so it’s not like defederating would change their experience in any way, so it wouldn’t really be retaliation and would just limit the content available to lemmy.world users.
What do you think?
Yeah, it’s a pity, this is the worst time for defederation, when the userbase is seeing a boom in growth.
Yeah, it seems some are happy to burn down the whole thing if it means they can rule over the ashes.
That’s not what’s happening at all. They have site rules. Remotr users aren’t following them, and aren’t beholden to them. Why should they continue to federated with instances that have incompatible rules?
That’s not “burn[ing] the whole thing down”. That’s community management.
The other side of federation is that instances are communities in their own right. And you don’t get to show up in someone else’s yard, shit in their pool, and then expect to be invited back.
But they can ban those users, exactly the same as they ban users on their own instance.
It’s their own prerogative, but considering their “restrictive” registration process with that application box, I’m not sure Beehaw will grow much in the future.
