First of all, let me say that while the admins can do what they want, I think it’s pretty unfortunate that beehaw is defederating from .world and shitjustworks. I don’t want to see the fediverse fracture, I want it to encourage conversation with others.

But, beehaw has done what they’ve done. And I must say it’s annoying to be able to see their posts and comments and not engage with them. Plus, I could see their large, still visible communities taking away from ours without people realizing their own posts and comments aren’t working.

So will .world be defederating from beehaw? I don’t have a horse in the race, I’m jw

  • wabafee@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    1 year ago

    To be fair I don’t mind that .world should just keep federate it may be one way but content is content some people just lurk anyway. Its probably what makes .world attractive aside from no requirement in registration.

      • Action Bastard@lemmy.world@lemmy.world
        link
        fedilink
        English
        arrow-up
        21
        ·
        1 year ago

        I think someone else hit it on the head with the suggestion that there should be some sort of warning that the community is essentially view only and cannot be interacted with. If it has that, then everything should be good.

      • FaceDeer@kbin.social
        link
        fedilink
        arrow-up
        11
        ·
        1 year ago

        Maybe a solution would be a user preference, “hide content from defederated instances”. I know I would be very annoyed to keep seeing threads that I couldn’t post in, the whole point of a site like this for me is user interaction.

        • Shortcake@kbin.social
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          Users can block instances without defederating. In kbin you can go to kbin.social/d/fediinstance.domain and block it.

          Idk how it works or the syntax for lemmy though