• patatahooligan@lemmy.world
    link
    fedilink
    English
    arrow-up
    41
    arrow-down
    5
    ·
    1 year ago

    I see several comments talking about this being a wrong decision, or Beehaw needing to change its attitude etc. I think these opinions come from a misunderstanding of the fundamentals of federation. Federation is not about all the instances coming together to cater to our needs. It’s about each instance doing its own thing, and communities will form around the ones that cater to them. In other words, we don’t need Beehaw to budge on its decision, we need to build the community we want without Beehaw, while Beehaw caters to the users who aren’t in this with us.

    • llama@midwest.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      As long as beehaw is only de-linking these instances rather than actually blocking them, doesn’t that still allow them to pull new posts and comments from beehaw? It’s like the no-participation mode that r/bestof uses.

      • Wintermute@lemmy.villa-straylight.social
        link
        fedilink
        English
        arrow-up
        9
        ·
        edit-2
        1 year ago

        Federation works in the opposite direction. It’s push-based rather than pull-based. To get posts from Beehaw, Beehaw has to actively push those posts to your instance. With this move, Beehaw is choosing to no longer push posts to lemmy.world and sh.itjust.works.

        • llama@midwest.social
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          Got it, this makes sense now. So in the case where I setup myownlemmy.com, I actually won’t be able to get any content to my Lemmy unless I tell other instance admins I exist and they push their content to me. But then let’s say lemmygrad starts pushing me their stuff and I’m like whoa don’t want all that, blocked.