New #Firefish release! And this is the new official account for the project, under naskya's leadership, give them a follow if you want to stay updated. Best of luck in the new beginning! 🚀
Alright, I think we now have a better idea of what's happening with #Firefish, so I might as well give a small update. Kainoa quit, and left the project to naskya, who is a person I appreciate very much, as they've always been kind and polite and willing to help. I also think they're very devoted to Firefish, and basically were the last person actively caring about the project. As far as I know, they intend to keep maintaining and developing Firefish, and a new stable version will finally soon be released. This is great news, as you don't need to worry that your server is running unmaintained and vulnerable software. So, alarm off everybody, no need to abandon ship.
As for us, we're standing by our decision to rebase #Catodon to #Iceshrimp. The changes we want to do are long term plans, but we've started redesigning some things and, whenever we are ready, I hope we'll show you something worth your attention. So yeah, firefish, iceshrimp and catodon are all alive and valid options (the first two to be precise, for the time being). All projects share code fixes and I think we're on very good terms, here in our corner of the fediverse. Enjoy the ride.
@erua И? В чём проблема? #Firefishне портит картинки, в отличие от #Mastodon / #Pixelfed. И особо без разницы, будет там 200 гигов или 10 — для картинков достаточно.
@andreclaassen das #fediverse ist so voller verschiedener sachen, #firefish#gotosocial#castopod da kann man soviel ausprobieren von motivierten leuten programmiertes, da hab ich persoenlich gar keinen bedarf zu schauen, was die milliardaere des planetens so programmieren lassen.
wir sind zwar nicht mehr, aber vielleicht genug ;)
An #Android#fediverse app I would love to have: A common place for notifications/feeds across Fediverse accounts, but interactions happen in native #Firefox PWA views of the sites rather than a custom homogenous UI. IOW, I still want #Firefish, #Pixelfed, etc to look and feel like they natively do on the server, but have a common aggregated launching point for interactions.
After giving this a lot of thought and discussing with the wonderful people that build Iceshrimp, #Catodon will rebase to #Iceshrimp. We feel that it's the right decision for the road ahead, as Iceshrimp is another #firefish fork that focuses in improving performance and they have already done some amazing improvements, like full Mastodon API support. With Firefish's future uncertain, we think it's better to stay closer to an actively maintained project. The two projects will stay distinct, as we have different design goals, but we have a common codebase so we feel this makes sense.
Just to be clear on all fronts and to answer the obvious question in advance, yes, Iceshrimp is also currently doing a full rewrite in C#, which is a few months away, and we haven't decided if we'll adopt this yet - it's a strong possibility, but we're keeping our options open. We're confident they're doing a great job, still, we'll weigh what the best decision for Catodon is on this when it's ready and the time comes.
Just wanted to let you know that this might push Catodon's development back a little, as it's sort of a structural change, but we feel that it's worth it, and that it might be better for the broader community. Catodon development will resume once rebasing to Iceshrimp is finished, and then we'll have better foundations to build this on.
Great to read that someone has taken the reigns of the #Firefish code. A new release today too.
Some of the comments on the release are interesting around how this all came to be, and the future. It may not be forever, but at least FF is for now and will hopefully settle FF admins until they have a plan and more info.
Good to hear that #firefish is still alive and in good hands. They released a new version. I wish them luck with their future developments, even if we aren’t using FireFish anymore.
Firefish isn't dead!! 😃 This is great news. Not sure if this means I will be able to use my firefish.social account, but I'm glad Firefish will be maintained and be updated.
Sad to hear about #Firefish, but it's something to keep in mind.
If one person is keeping a project alive and is unable to build a long term, sustainable team around the project, relying only on that individual, that project is fragile.
Apropos of nothing, I'd love if I could build a long term, sustainable team around #owncast, if this sparks your interest at all! If I get hit by a bus tonight, Owncast is dead tomorrow.
We finally have a statement from the former Firefish owner/lead Developer. It seems that the Firefish site and Gitlab is given to one of the maintainers. Still, I kind of consider it EOL as the new person in charge isn't a programmer. It's pretty much doesn't change anything unless a new lead developer decides to take on the project. I do wish Kainoa the best in his future endeavors.
There are other options, such as Sharkey, IceShrimp and Catodon. However, IceShrimp is doing a rewrite in C#, so it's basically going to be it's own thing, which might be interesting to try, but not something I would use outside of personal use. Same with Catodon, which might use IceShrimp's C# rewrite.
I have a lot of trust in Sharkey's team in making sure something like this doesn't happen while making it community driven. Taking the Glitch-soc approach like with Mastodon will make Sharkey a more viable option since it’s just Misskey with extra features, some making it to mainline Misskey like with some things from Glitch-Soc making it to vanilla Mastodon.