I’m happy that I made the move to @Sharkey in late November as I was not really confident in the direction Firefish is heading. It was evident with the slow performance and local timeline would fail to load. Activity was decreasing on Sakurajima Social before the move because of how bad of an experience it was.
After the move, activity started to pick up again thanks to the improved performance. Misskey 13 resolved all the issues Misskey 12 forks are facing that caused Foundkey to go EOL with Firefish in the mess it’s currently in (Iceshrimp has the same scaling issues, but at least from what I heard, that team is at least responsive.
With Firefish Social in a worse mess as there are reports no new posts are being fetched, making the timeline 5 days old and the admins completely unresponsive. At this point, I don’t know if it’s even possible to migrate the account off Firefish Social if federation is not working on that server. This is why we dumped Firefish for Sharkey.
With that, besides our server, a handful of established Firefish servers are starting to jump ship to IceShimp or Sharkey. Infosec Exchange’s Firefish server transitioned to IceShimp. It should be even easier to migrate to Sharkey as there are documentation on how to do it.
I do recommend Sharkey over IceShrimp since it has a public timeline view (for visitors), more moderation tools and performance. The Sharkey Team is very responsive and helpful. Of course, they are adding back features that are in Firefish.
But I have a feeling that at the rate things are going for Firefish, it may have a bleak future ahead unless it can turn things around.
It’s unfortunate to see Firefish turn out like this, but it’s not surprising.
