this post was submitted on 15 Jun 2023
350 points (100.0% liked)

sh.itjust.works Main Community

7584 readers
4 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS
350
Beehaw* defederated us? (sh.itjust.works)
submitted 1 year ago* (last edited 1 year ago) by can@sh.itjust.works to c/main@sh.itjust.works
 
you are viewing a single comment's thread
view the rest of the comments
[–] inventa@lemmy.fmhy.ml 19 points 1 year ago (2 children)

But that is an issue too. Why would other instances allow them full access while being prevented from collaborating in theirs ?

[–] socialjusticewizard@sh.itjust.works 18 points 1 year ago (2 children)

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.

[–] inventa@lemmy.fmhy.ml 5 points 1 year ago

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.

[–] Faceman2K23@discuss.tchncs.de 7 points 1 year ago

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.