Reflecting on the firefish/calckey “moment”

which was about a year ago now, I can’t help but suspect it was a small event with wider implications on the dominance of #mastodon in the #fediverse

I think it was the last chance to direct the twitter migration energy into discovering new/different fedi platforms.

And it was blown, with alt-social in a weird steady/waiting state that’s smaller I suspect, than what many hoped for.

@fediverse
#firefish #calckey

cntd: https://hachyderm.io/@maegul/112358202238795371

1/

  • Skull giver@popplesburger.hilciferous.nl
    0·
    6 months ago

    As far as I can tell, Lemmy was just a bad choice for Beehaw. The people maintaining Beehaw don’t have the knowledge or skills to maintain the software themselves (as Lemmy us written in Rust), but they also don’t want to update their software at the moment.

    I’m not sure of the reasons why Beehaw decided not to bother updating, but trying to run a stable platform on decidedly unfinished software (note the 0 in the version number) written by a tiny group probably wasn’t the best choice.

    However, Beehaw also doesn’t seem to have found an alternative, nor do they seem interested in building something themselves, so I guess Beehaw will have to linger in limbo for a while.

    • 0xtero@beehaw.org
      0·
      6 months ago

      Yeah, as a beehaw user, I’m pretty familiar with the situation. I’m not going to re-hash the whole thing here (and I don’t represent the instance), but let’s just say PR’s for features were offered, but not accepted. Discussion was attempted but it resulted in Lemmy devs asking beehaw to fuck off - so that’s the end of that.

      There’s an alternative being tested. I believe we’re going to Sublinks, but there’s still active development going and sizeable migration. So we’re still here. For the time being.