Probably a very polarizing question.

On the one hand, having most of the users and communities on LW causes technical issues (see this post), and also gives the LW staff too much power over Lemmy as a whole.

On the other hand, with 18k MAU on LW out of 47k (https://fedidb.org/software/lemmy/), every community listed there has a much higher chance of visibility compared to an alternative hosted on another instance

History of LW controversial decisions

  • mozz@mbin.grits.dev
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Every time I want to post a politics article, I have to decide whether to post @lemmy.world (and exclude the Beehaw people and include the trolls and reach more people) or @beehaw.org (and exclude the World people and help the growth of a community that seems better, but reach a lot less people).

    IDK what the answer is

    • Blaze@lemmy.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      Hello, good to see you here!

      I completely get what you mean. Beehaw creates its own kind of situation. For a long time I was hoping they would refederate with SJW and LW, especially after 0.19.X where users could block instances on their own, but I guess that’s never going to happen.

      It’s really a shame, because people and communities on Beehaw are really valuable

      • Blaze (he/him)
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        To be fair, I cross post a lot, but over time I gets a bit annoying, especially when you know that today with user-level federation maybe Beehaw could consider refederating with LW and SJW

        • Die4Ever@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Beehaw has given up on Lemmy (Or just given up in general? They aren’t taking care of what they have nor have they moved to something new).

          They’re still on v0.18.4 despite v0.18.5 being an extremely easy and safe update with a hotfix for an issue they were specifically complaining about. Literally takes like a couple minutes to do that update but they never did it. They’re also keeping themselves open to at least 1 security issue by being on such an old version.