Comment on Firefish is entering maintenance mode
MoogleMaestro@lemmy.zip 2 months ago
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.
db0@lemmy.dbzer0.com 2 months ago
counterpoint: If developers aren’t forced to “eat their own dogfood” it becomes difficult to see some issues and know what to prioritize.
MoogleMaestro@lemmy.zip 2 months ago
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.)