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.
@catodon The team that cancel kainoa and firefish instance for a RT ? and declare having a new name and logo is enough to make a drama AND a fork AND after do a logo and a new name ?
@tripop@catodon Iceshrimp isn't lead by the person you're thinking. I was also under the same impression until recently. Iceshrimp's lead dev is @zotan and as far as I can tell she's pretty cool. We're not merging the projects anyway, and I think we've explained "why".
Add comment