@ThatOneKirbyMain2568
moreover, i would love to see kbin and mbin devs joining forces, thereby reducing each other’s workload :)

@ThatOneKirbyMain2568
can’t tell how much i enjoy kbin fr 😊

i hope that the project itself will become more stable, and that ernest will find someone to admin kbin.social, so that ernest can focus on software development

@itsaj26744
misskey and its cutlery set of forks all have rss support > among them, rss support of firefish and iceshrimp could easily be labeled “rss eye candy of the fediverse”

rss feeds on the *keys follow the model:

https://instance.name/@user.rss

atom feeds are also available:
https://instance.name/@user.atom

@Chozo
this is the english machine translation of naskya’s post:

Even if you ask me when the next version will be out, I don’t know.

one week ago, naskya stated in another post:

Firefish v1.0.5 を出すために必要にゃ雑用は 2 日くらい前に睡眠時間を捧げてほとんど片付けたのであとは Kainoa さん次第です

english machine translation:

I devoted my sleep time to do most of the chores needed to release Firefish v1.0.5 about 2 days ago, so the rest is up to Kainoa.

source: https://post.naskya.net/notes/9n8d2h0qq12bdzm1 #firefish

@ThatOneKirbyMain2568
i hope so, too!

if mod tools worked better, the microblogging sections could become even more interesting in terms of content, and less of a hassle for moderators 🙏

@ThatOneKirbyMain2568

1. microblog posts: rarely, but once in a while
2. microblog replies: don’t work atm, but i like it!
3. microblog tab: depending on whether i have to micro-manage or not:

• kbin’s mod tools are buggy, e.g. an account banned from a magazine can still spam the microblogging section > mods better look inside the microblog tab …
• otherwise depending on my mood

1. viewing microblog posts in my home feed: all the time - i like it even more on kbin than on specific microblogging fedi platforms tbh
2. aggregated view is great! i keep boosting loads of microblog posts via kbin ✨

@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

@RustyOperator

@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

@RustyOperator @maegul @Amelia

@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?

@RustyOperator @maegul @Amelia

@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, too

@RustyOperator @maegul

@ThatOneKirbyMain2568
defederate!

@maegul
it’s sad to see that, and all of it was foreseeable in april 2023 already …

@RustyOperator

sharkey test instance at blahajzone also down

The instance has clearly communicated that it primarily serves as a test instance, i.e. it does not strive for or want to guarantee stability.

that’s just not true > when c.s switched over to dev branch in april 2023, this was not motivated by wanting to become a “test instance” > rather, this was a desperate move to keep the instance afloat which by then had been become quite wonky > afterwards, things got even worse, so the transpicuous idea to rebrand the whole project

noting, absolutely nothing about f.s is about being a test instance > see also atomicpoet’s post about movin away from f.s - f.s was supposed to be a flagship instance, but only evolved into a shipwreck

the biggest disadvantage of firefish: its community which has become like a sect - but that had been going on for a very long time already …

even weirder if it’s a Mastodon fork such as Glitch-soc, Hometown, Fedibird,… since they use older Mastodon versions as base

i myself have been active on calckey/firefish, hajkey and iceshrimp instances, and never had a problem interacting with people on mastodon forks > there had been some backfilling issues, but they got solved > but federation problems do exist: so far, it is not possible for *key users to interact with lemmy instances; also link posts from kbin do not show up on *key timelines

since you are on a lemmy instance: be aware that people on the *keys cannot interact with lemmy instances

firefish is rebranded calckey, a misskey fork > project has been in trouble since, hmmm, may 2023 > the *keys offer a very different interface, emoji reactions and lots of other features which mastodon does not have > *keys ui is pretty nice compared to mastodon - in the end, this is a matter of taste > but other than that, particularly firefish and its forks do not scale well: there is a reason why former firefish.social admin atomicpoet chose to migrate to another instance, though atomicpoet’s post tries to hide the reasons for moving > note: firefish.social is a special case - this instance is a lost cause with outages beyond comparison > instead of building up a community at firefish.social, the admins effectively destroyed the community by introducing new experimental features instead of focusing on stability