Announcement: Firefish will enter maintenance mode
For those who have been supporting Firefish and me, I can’t thank you enough. But today, I have to make an announcement of my very difficult decision: As of today’s release, Firefish will enter maintenance mode and reach end-of-support at the end of the year. The main reasons for this are as follows.
In February, Kainoa suddenly transferred the ownership of Firefish to me. This transition came without prior notice, which took me aback. I still wish Kainoa had consulted with me in advance. At that time, some people were already saying that “Firefish is coming back”, making it challenging to address the situation. Also, since there were several hundred active Firefish servers at that point, I could not suddenly discontinue the project, so I took over the project unwillingly.
Over the past seven months, I have been maintaining Firefish alone. All other former maintainers have left, leaving me solely responsible for managing issues, reviewing merge requests, testing, and releasing new versions. This situation has had a significant impact on my personal life.
Frankly speaking, there are numerous bugs and questionable logic in the current Firefish codebase. While I attempted to fix them, balancing this work with my personal life made it clear that it would take ages, and I’ve started thinking that I can’t manage this project in the long run. Additionally, vulnerabilities have been reported approximately once a month. Addressing vulnerabilities, communicating privately with reporters, and testing fixes have proven overwhelming and unsustainable. Moreover, a certain percentage of users have made insulting comments, which have severely affected my mental well-being and made me fearful of opening social media apps.
I will do my best to refund the donations made to Firefish via OpenCollective, but that’s not guaranteed.
firefish.devandinfo.firefish.devwill remain operational until the end of February 2025, after which they will return a 410 Gone status.Server admins may downgrade Firefish to version
20240206/1.0.5-rcand migrate to another *key variant, or may fork Firefish to maintain.Downgrade instructions: https://firefish.dev/firefish/firefish/-/blob/downgrade/docs/downgrade.md
Thanks,
naskya
I was on firefish’s previous instance, known as calckey, before I migrated back to Mastodon.
There were definitely warning signs that the project was facing maintenance issues in those days as well, and it felt that the Firefish rebrand was an attempt to “start a new”.
But just like my post on KBin’s demise, it should be a warning to those who want to make the software and host a “big” instance: Don’t do it. I think it’s smart to host your own mini instance for testing, but you should probably solely focus on the code development side of things to make sure that you aren’t over burdening yourself with managerial tasks. If your software is good, people will make spins inevitably. If people use it, then you will probably have enough people contributing that you can scale up your mini-instance if needed. But don’t jump in without the finances in place, because you’re essentially taking on two jobs.
counterpoint: If developers aren’t forced to “eat their own dogfood” it becomes difficult to see some issues and know what to prioritize.
I do agree that developers should use their own software, but doing so on a smaller instance with strict active user limits is probably the right call – at least until you are certain the software has a “stable” version, but even then you probably will want to run a master branch instance that is much less stable and prone to errors. Until you can afford it, it’s probably not a good idea for developers to be spending a huge amount of time debugging in-progress features (which IIRC, firefish had a lot of those.)