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
    4
    ·
    edit-2
    8 months ago

    I thought they had posted that they’d already made the decision of what platform to switch to, but weren’t announcing it yet (which seemed weird to me). Sublinks honestly would make some sense given the Lemmy-compatibility and emphasis on mod tools, which I know was a constant pain point for them… but IDK if it’s mature enough. But yeah if you told me they were waiting for it to mature so they could switch over, that would make sense.

    I’m also very curious to see how (if at all) you migrate an existing server with all its existing ActivityPub keys and subscriptions to a new piece of software, on the same domain, without unfixably breaking its federation with every other instance. My guess is that they will switch to a different beehaw.(whatever) domain but I’m curious if there’s a good solution I’m not aware of.

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

      I’m also very curious to see how (if at all) you migrate an existing server with all its existing ActivityPub keys and subscriptions to a new piece of software, on the same domain, without unfixably breaking its federation with every other instance. My guess is that they will switch to a different beehaw.(whatever) domain but I’m curious if there’s a good solution I’m not aware of.

      Tha’ts probably how it’s going to happen.

    • kopper [they/them]@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      8 months ago

      I’m also very curious to see how (if at all) you migrate an existing server with all its existing ActivityPub keys and subscriptions to a new piece of software, on the same domain, without unfixably breaking its federation with every other instance. My guess is that they will switch to a different beehaw.(whatever) domain but I’m curious if there’s a good solution I’m not aware of.

      If the software you’re migrating to is built to allow that to happen, it’s absolutely possible. In the microblogging side of the fedi migrating between software isn’t uncommon, though in nearly all cases they’re forks from the same “family tree” so things work out mostly due to that, (Misskey is infamous for having a LOT of forks with most being capable of migrating to most, Mastodon can migrate to/from it’s forks Glitch-soc/Chuckya/Hometown, and Pleroma and Akkoma can migrate between each other…).

      There are software being built from-scratch to be migratable from other software (aside from Sublinks, Iceshrimp.NET comes to mind as a total rewrite of Iceshrimp, which started out as a fork of Firefish and therefore is in the Misskey family tree, but found the existing codebase to be un-salvagable) but it’s definitely a rare case.

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

        Misskey is infamous for having a LOT of forks

        Seems like at some point they wanted a fork for every letter of the alphabet ha ha

        • kopper [they/them]@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          3
          ·
          8 months ago

          I mean, there’s only so much you can do when your upstream is developed exclusively in Japanese (to the point the code comments are also in Japanese) with a focus on adding Reversi and a Suika Game clone into the software instead of refactoring so the same piece of code isn’t duplicated in 10 different files split across the frontend and the backend and refuses to implement editing because they find it too hard when both major fork families (Firefish/Iceshrimp and Sharkey) have it and it works fine enough (alt text edits don’t federate, but that’s comparatively rare)