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

  • WinterBear@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I dont think this is quite right - lemmy.world can’t listen to Beehaw either, it just still has the synced copies of the Beehaw communities loaded on it. So lemmy.world users can still see posts and comments from before the defederation and can even comment themselves but nothing gets synced between the two instances. Effectively there are separate instances of those communities now, one on Beehaw and one on lemmy.world. To be honest this way of managing defederation feels a bit misleading as it gives the impression there is still a connection, IMO when you browse a community that originated on a defederated instance it should be something really obvious and upfront.

    • thedarkfly@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Ah sorry for my misunderstanding. So, instances actively send their fresh data to the other instances; it’s not a passive thing like one instance that looks at another (like we do through a browser)? What prevents the lemmy.world server to access fresh data from Beehaw? It’s public after all.