Firefish has been abandoned.
Firefish has been abandoned.
Ugh, I really tried to stay out of #fediverse drama but I guess I have to say a few things. Most of you know me as a #firefish core team member, so I think I owe it to the admins of almost 500 firefish servers out there and to the almost 5000 members of firefish.social. So, yeah, if you haven't not...
Just a headsup for any server admins running Firefish, apparently it is no longer being maintained. One of the core developers of Firefish has written about the situation in the link provided.
-
Not to downplay all the blood, sweat, and tears that have been shed while making the fediverse work, but if I may offer some unsolicited advice to the author of the linked post: Publicly airing out a team’s dirty laundry tends to be… counter-productive. Usually it’s best to “keep it in the family.”
In this case, we don’t know what’s going on in the original project owner’s life right now. The author of this post could have just said “hey all, we apologize for the inconvenience, but the original project appears to be abandoned, so we’ve forked the project with the intention of patching some of the known issues and adding some new features.” (insert GH link here)
Although the original project dies, this new project is born, and who knows—the original project’s owner might even show up again someday and start making meaningful contributions to the new project (or not).
I say all this without knowing the full history of this project, and I don’t mean to downplay the author’s frustration, just my two cents.
All of that said, in my mind this situation makes for an interesting case study on the pros and cons of different ownership structures for public/open projects.
-
In this case, we don’t know what’s going on in the original project owner’s life right now.
I had a quick look at the repository and the last commit was three weeks ago: https://git.joinfirefish.org/firefish/firefish/-/commit/db604b8f466e826fd8c93d3519898c8ab236a2ed
Freaking out over three weeks of silence during Christmas season is so weird.
-
I'm fairly certain they're a college student also.
-
I think firefish.social (the "flagship" Firefish instance) cratering at roughly the same time the dev went AWOL is more what prompted this.
-
-
Usually I would agree but in this case it's important to provide context for people using the platform. According to the post Firefish's admin practically abandoned it for months now and was radio silent and now hasn't replied to the core team in over a week, someone had to say what's going on.
Everyone knows how hard managing these things are, and it's often a thankless job, but this sadly seems like another example of someone taking on a leadership role then bailing for whatever reason. The owner should've let someone else handle firefish.social if they didn't have the time.
-
I'd like to add from a user's point of view. Firefish.social was advertised as the flagship instance and in the beginning everything was fine and nice on there but then they started to implement new stuff and this broke something leading to the flagship instance being down or unusable for most of the time. Days turned into weeks with the server not running or at least not without problems (only talking about timelines, not to mention other features like antennae or lists which wouldn't work at all) without any communication from the admins and no replies to direct inquiries. I eventually moved to another instance running a stable firefish version. But our admin also complains about being ignored by the dev team, so they decided we will be moving to Sharkey. And we all know that Kainoa is young, started uni last year and a new job - that's all fine and understandable but maybe not compatible with running such a big project. Which again is fine but also means that -for now- the project is not being worked on while in a broken state. I think this is valuable information for users and admins and it was good to hear this from someone in the core team.
-
-
Open source devs being in a parasocial relationship with their projects uwu
-
-
this seems to be a trend playing out.
i hope instances can come up with a more standardized methods of control that dont leave all the keys in a single humans hands. we know how unstable humans are.
-
i hope instances can come up with a more standardized methods of control that dont leave all the keys in a single humans hands
Yeah like we could have a shared legal entity, say a corporation, controlling the servers 🤔 And they could instead of a single decisionmaker have a board. 🤔
Jokes aside, wouldn't this go against the federated idea? anyone can go and roll their own instance. Or take it down. Control is in the user's (of the software, that is, the instance owners) hands!
-
Yeah like we could have a shared legal entity, say a corporation,
You mispelt coöperative.
-
Even at its smallest form, a federated instance hosting a community likely needs more than one person acting as admin and mod. It may not be a for profit corporation, but there needs to be some kind of collective organization.
-
-
Meanwhile the original software of which Calckey/Firefish was forked from, Misskey, continues along nicely: https://github.com/misskey-dev/misskey
-
I'd love to move to mainstream Misskey, but there's a core reason why I'm using Firefish at the moment, namely the ability to actually import my old posts from Mastodon. To my knowledge, pretty much nothing supports importing posts in the Fediverse, except for Firefish and forks, Friendica and forks (to an extent), and PixelFed.
-
there’s a core reason why I’m using Firefish at the moment, namely the ability to actually import my old posts from Mastodon.
Do you know if the Misskey maintainers are actively refusing that feature or has it just never been proposed in a pull request?
-
-
-
blahaj.zone moved to ice-shrimp too but honestly calckey/firefish (HATE the name) always left a bad taste in my mouth.
i've always loved misskey above all else.
-
We partly moved to ice shrimp, but it was quite divergent from Hajkey, and after being burnt by our Calckey experience, we lost a lot of momentum and energy, so it's sort of sat there in a mostly working state, not ice shrimp and not Hajkey for a while now.
Once we're both back from South America though, we'll do a migration to Sharkey (a direct soft fork of Misskey). After that, Kaity will look at gradually adding our Hajkey specific features directly in to Sharkey where possibly.
-
-
Damn, that repository and its forks really know how to crash and burn. I'm glad to see it's being given more life with another fork. That said, with a name like Catodon, I can pretty much guarantee it won't be a resounding success 🥺
-
with a name like Catodon, I can pretty much guarantee it won't be a resounding success
Pfft, are you kidding me?? I’ll take the other side of that bet any day!
-
Just incase, we should probably start workshopping some similar names for the next forks.
Batodon, Ratodon, um Gatordon
-
-
-
Long live IceShrimp!
-
Was on it for a few months but jumped ship after bugs went unfixed. Can't fault the owner personally. It's a stressful, thankless job. Hope he finds happiness in 2024
-
The power of opensource.
-
...is that it can be picked up and continued by anyone rather than lost forever, right?
-
-
Oh wow. And I was suggesting Firefish to my wife to get her off twitter because it looked “fancier” than Mastodon. Glad she hasn’t switched over yet, and I’ll probably just get her on Mastodon instead. I wish catodon success though, and I hope it’s a better replacement for Firefish.
-
Mastodon is like the boring solid mainstay that will always be there and keep the fediverse alive. There are tons of other fedi projects that are more exciting, but they burst into flames way too often for my taste lol
-
There's Sharkey, which is also a fork of Misskey like Firefish
-