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.
cntd: https://hachyderm.io/@maegul/112358202238795371
1/
Copying the linked thread here (cuz I stuffed it up):
So the basic story would be that mastodon’s dominance is pretty entrenched and the “migration” event is mostly “over” (whatever other “events” are on their way)
But I wonder about the details of the firefish moment
I think it revealed that there are/were plenty interested in novel & different platforms. We’re novelty seekers after all right. Generally, I’d wager any new platform needs some degree of novelty to “make it”.
Further, its collapse showed how hard creating a new platform is.
2/
Firefish did well at presenting itself as “professional”, capable and rich. But these were over-promises, and despite a number of people being involved or contributing, a good deal of user enthusiasm, the whole thing fell into a heap.
And that’s the bit that concerns me. How many people/teams are there both capable and willing to put up a good, successful and sustainable platform?
The #firefish lesson may be that the fediverse just hasn’t attracted a healthy building culture/personnel. 3/3
Thanks for the context.
And yeah - a lot of fedi is built on spur of the moment inspiration without much planning on the long term. Sometimes it works out (like pixelfeed and the other related projects) and sometimes the passion of one (or small group) of devs just isn’t enough.
Lemmy is pretty good example (from the other side of the scale) as well - we’re at version 0.18.4 - and the devs are pretty hostile.
deleted by creator
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.
I’m only vaguely aware of the history here. Any chance you’ve got some links to these PRs? Not sea lioning (or at least that’s not the point) … genuinely curious to see what happened.
There’s a good write-up from the Beehaw admins here: https://docs.beehaw.org/docs/important-questions-decisions-and-reflections/beehaw-lemmy-and-a-vision-of-the-fediverse/
Thanks, but I couldn’t find any links to PRs in there (which is what I was mainly interested in). The rest of the dynamic explained in there I’m roughly familiar with.
To me, FireFish got replaced by IceShrimp. Good looking interface, nice features (Antenna) and regular releases.
Yea it’s descendant too. There’s also sharkey and catodon too.
IIRC, Catodon development is currently halted (https://catodon.social/notes/9rl77swzw25jjq7x).
Sharkey I don’t know
There really is a whole *keys forks lore ha ha
The problem is that Misskey code is bad. This is the main reason the forks exist at all. Iceshrimp is rewriting from scratch in C# and it’s my main hope for the *keys.
I did not know this about iceshrimp and c#! Any links to their reasoning etc?
Sorry anout the delay. The siteis iceshrimp.net
Huh. Thanks!!
Congrats and/or condolences for this “moment”.
I guess I’d have to check mastodon to find the rest of this thread and the context of what it actually references. Posting into Lemmy/Kbin groups from long mastodon threads is quite janky experience, I find.
1/
