this post was submitted on 15 Jun 2023
348 points (99.2% liked)
sh.itjust.works Main Community
7584 readers
1 users here now
Home of the sh.itjust.works instance.
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
But that is an issue too. Why would other instances allow them full access while being prevented from collaborating in theirs ?
I'm not really keen on their reasons for defederating, but this makes no sense to me. What do I care if a beehaw user is posting good content on my community but I can't go to their instance? It's still more content and engagement for my community.
problem is you don't have to start slinging slurs to troll people. People can still be nuisances and say bigoted things.
I see your point. I was seeing it from the perspective of discouraging stuff to be shared on other communities because it's already in beehaw, but you'd need an account to participate there.
But I see what you say, allowing them to contribute to other instances isn't bad even if they don't allow those instances to contribute on theirs.
That's each instances choice to make I guess, and it's part of the freedom of the platform.
beehaw would be within their rights to do it (effectively going read only to the outside, not currently possible but a requested feature is to have private or invite only communities), and if they are intending to be the clean family friendly option, it would be a valid choice to make if it were possible.