Conversation

Notices

1. Zergling_man (zergling_man@sacred.harpy.faith)'s status on Monday, 05-Feb-2024 02:01:50 JST Zergling_man

   in reply to

   • Cefr
   • :verified_2:防空識別區𝒔𝒐𝒄𝟶
   @adiz @Cefr For misskey, I can't say. I haven't even used it, myself (still need to get on starnix's misskey instance, whenever I figure out how the fuck registration works on it). I've heard other people complaining about the documentation.
   In general Japanese devs are nutcases, their software works but it's always in the weirdest fucking ways.
   • New Janny in Town likes this.
   • :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Monday, 05-Feb-2024 02:01:51 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶

     in reply to

     • Cefr

     @Zergling_man@sacred.harpy.faith How is that a bad thing? @Cefr@beige.party

   • Zergling_man (zergling_man@sacred.harpy.faith)'s status on Monday, 05-Feb-2024 02:01:52 JST Zergling_man

     in reply to

     • Cefr
     • :verified_2:防空識別區𝒔𝒐𝒄𝟶
     @adiz @Cefr But it is extremely Japanese software.
   • :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Monday, 05-Feb-2024 02:01:53 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶

     in reply to

     • Cefr

     @Cefr@beige.party so it seems Misskey still has a future with non-Japanese usersWhy is "Misskey having a future with non-Japanese users" contingent upon the existence of forks like IceShrimp, Sharkey, and Catodon? People can just use Misskey. It's not as though Misskey is "off-limits" to Western users. Rofl :no_misskey_no_life:

   • Cefr (cefr@beige.party)'s status on Monday, 05-Feb-2024 02:01:54 JST Cefr

     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.

     https://git.joinfirefish.org/firefish/firefish/-/issues/10847

     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 are disassociated with FF completely so it seems Misskey still has a future with non-Japanese users. 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.

     #Firefish #Calckey