It seems like there's a rivalry brewing between #Sharkey and #Iceshrimp on which one's gonna be the definitive "Western #Misskey" of the #fediverse :sagume_think:
One could even say that there's a.. cold war going on between them 🥁:laughing_cirno:
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.
@lewiscowles1986 only trying to give the facts =) Any popular open source project is rarely the result of the work of just its founder(s). It's fair to give credit to all the projects, forks and upstream, and to the wider community that helped in one way or another! @box464@blake
@panos@box464@blake
At no point have I been anti what came before; but I am reading a lot of these replies; like "this person did not do the work, don't thank them". I'm sorry if that is not what you intended, but I can't fathom why else you feel I'd need to know more about this.
If Firefish is going to come back, Kainoa won't have a hand in it. They quietly handed over the keys to the repo to a maintainer... who has publicly stated they aren't a programmer and are just looking after commits. Not exactly a signal things are starting back up.
Unless there is an announcement soon about someone taking up development again, I think it's safe to say Firefish is over as a Fedi platform.
Optimism wants to say that someone will, but at this point even if someone does it'll be playing catch-up to the current state of affairs. It isn't possible for someone to come off of the street and say "I'll do it" and go back to the pace that was happening last summer immediately. (But it's not impossible for me to be wrong and six months from now someone does. I'm just not banking on it happening. Even the Firefish name itself might be too damaged in reputation to even take back up.)
#Iceshrimp, #Sharkey, and #Catodon are #Misskey derivatives who are continuing onward with things. All three of them have disassociated with FF completely so it seems Misskey still has a future with non-Japanese users. (Iceshrimp even spent time on a new non triangular logo to further separate from Firefish.) Server admins who wanted to consider a Firefish instance but shied away from the drama last fall may want to follow those projects instead.
If your fedi server is still on Firefish, don't be surprised if an announcement "were taking signups on our new Plombus server, in X months Fleeb will be decommissioned" comes down sometime soon. Internet services without recent updates are asking for trouble from exploits and vulnerabilities. Also, without an active FF developer to fix standing issues (or a skilled DB admin on your instance's behalf to whittle the database and schema to fit the new system as well as possible) a cut-over migration where users don't lift a finger isn't in the cards like the Calckey to Firefish migration last September. It likely will be up to you to decide to either move your account Mastodon style (no post migration, just your follower lists and a link back to the prior server) or to just start fresh.
I completely missed that #IceShrimp was doing a .NET rewriting. That's quite exciting, there wasn't a lot of .NET #ActivityPub implementation so far, and I'm curious to see how they will tackle some of the tricky parts of the protocol.
Recently I've seen posts that #Firefish project is in trouble? Its flagship server being unavailable, and people are impatient about new releases. Sad if true, though I hope its death is slightly exagerrated. Anyhow, I've learnt that people are migrating to other Misskey forks (mainly #IceShrimp, #Sharkey, and #Catodon) And Iceshrimp devs are rewriting the JS backend on C# 😯
It's almost time. We're super-excited. #FediGroups is entering public testing now, before a full live launch.
Many of us have used other Boosting Groups, but they only work well if you follow from Mastodon accounts. We know there is a wider fediverse. FediGroups works with all the favourites, including #Mastodon, #Firefish, #Iceshrimp, #Catodon, #Sharkey, and more. One big happy family 👪
@hello
Cool! Most ppl who want to check out source code dont want to tear it apart, but to see how youre doing things, share ideas, etc. as part of a social process of programming. Ppl get works in progress arent finished. You'll get there! Good luck until then
Kinda big day tomorrow as catodon.social's getting updated to our latest dev version, since our announced rebase to #Iceshrimp is finished, which means that, if everything goes well, after tomorrow catodon.social will have all of the performance improvements of Iceshrimp, including full Mastodon API support. It took us back a few weeks but we think it was worth it, and now we can resume development towards our first release. #Catodon
I can't see some of other people's posts from mastodon.social of the same hashtag. I checked the visibility and they're public but I can't view it here on fedia. I had to copy the post link of the post to be able to see and interact with it.
@mesdoigtsmaladroits someone on Fedia.social has to be following the people making those posts on other instances in order to show up for anyone on fedia.social. Mastodon.social has them because it’s so large that the posts are either being made by people on mastodon.social, or followed by someone on mastodon.social. I attempt to mitigate this by using an activitypub relay to force feed posts into fedia.social, however only about 500 out of the over 20,000 instances participate in the relay, and mastodon.social isn’t one of them.
Sadly it looks like #firefish is going to die a slow unmaintained death now, and I need to pick a successor to run.
#iceshrimp and/or #catodon appear to be the spiritual successors, but I think I'll be waiting to see who publishes and maintains a public Docker image first.
Bon visiblement les réglages fait dans PostgreSQL pour les workers semblent avoir résolu le problème, ça fait un peu moins d'un mois que tout tourne nickel du coup sans que la RAM pète un câble et que PostgreSQL ne se vautre 👍
Just learned about the demise of #Firefish (head is M.I.A.). It's unfortunate for the thousands of instances running it, but with that comes #IceShrimp, #Sharkey, and #Catodon. All of them (I think) are being developed by former Firefish devs. Options.
Hopefully, current FF users are all, if they want to, able to move to another actively-developed community easily.
@luthien1126 firefish.social, their flagship instance hasn't been working for a while now, from what I read. I have a Firefish account on fedia.social as my backup. I try to sync up all that I'm following on that account whenever I remember or have the time.