344
Beehaw* defederated us? (sh.itjust.works)
submitted 3 years ago* (last edited 3 years ago) by to c/main@sh.itjust.works
400 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 3 years ago (6 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 18 points 3 years ago (4 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent