Does anyone have any ideas on how we can get in contact with Kainoa or someone, because I really want to move instances and keep all of my account stuff.
The server has been going down time and time again and I just want to move to something that isn’t as likely to just not exist one day out of the blue.
@RustyOperator@sopuli.xyz I haven’t been able to export my notes (posts) out of #firefish.social for over a month now, and all attempts to contact @kainoa@firefish.social and to report the issue on their GitLab have been ignored. I hope y’all migrating out of firefish.social or stop.voring.me are luckier than me and are able to backup and export your notes out.
So it’s run by the firefish lead dev, and it’s been well known for a while that they don’t have much time anymore for Fedi stuff, at least not as a full time commitment. I think/suspect they were getting paid by some people before but that’s now run dry. So they’re working full time and studying it seems.
Firefish dev seems to have slowed and their flagship instance is dying a slow but sure death.
To anyone who knows this it’s not surprise that stop.voring.me is down too.
I’d recommend you move one and forget about the instance. Maybe later you can pull your stuff out, but for now that account is stranded on a dead instance and dying platform.
@maegul
it’s sad to see that, and all of it was foreseeable in april 2023 already …Yea … I’ve said it elsewhere … in hindsight it’s fairly clear to me that some people with an excessive marketing and growth mindset and their own agendas got involved with Firefish/calckey and burnt it out from the inside with excessive hype and ambition rather than letting it grow organically.
From what I’ve gathered, that’s more or less what happened.
@maegul
when i saw all that happening, i was sure that firefish won’t swim, but die soon > the rebranding happened behind closed doors, only to claim that ff was a community project > then, april got kicked out of the dev team, and there was no one else at firefish anymore to do serious backend work > firefish felt like a sect, consumed by its own hype
@maegul@lemmy.ml @RustyOperator@sopuli.xyz as far as i heard the firefish devs just don’t have alot of time atm, and one of the lead devs seems to have a bit of personal issues and thats the reason dev is slow and why the instance is down so often.
i can recommend looking at instances that use community projects that are based of misskey such as Sharkey (misskey softfork) or IceShrimp (hard fork of firefish) well unless u would like to completely jump ship on *key
(As u can see Sharkey can also somewhat communicate with lemmy unlike firefish and co)
@Amelia
all the *keys can communicate with lemmy as long as the lemmy post is not a link type post, and firefish users can take advantage of this rather rare event to chat with lemmy and kbin users, tooThat’s a bit sad to hear, but it’s understandable. I guess the only thing that would have been nice was more communication from the devs/moderators.
Thank you for the suggestions! I’ll look into them. Do you know any similar projects to Akkoma? Because Firefish never had any well working Android apps and using something related to Mastodon might work better with them?
Both Iceshrimp and Sharkey should have better compatibility with Mastodon clients
@Kierunkowy74
i thought that the iceshrimp devs had rewritten their mastodon api compatibility layer, and that iceshrimp works fine with masto clients … it doesn’t?I didn’t know. But perhaps it works.
@Kierunkowy74
i use hajkey and iceshrimp, too > but i am not drawn to mastodon clients because they do not offer many *keys features > for the time being, i stick to the pwa
