testing

@YugiohMaster88
not at all tbh

when firefish was still calckey, it was a thing > but for a variety of reasons, the project came to a standstill, and two other misskey forks took the lead: iceshrimp and sharkey > as strange as it seems, firefish has already become some kind of legacy ware

moreover, the *keys have federation issues, especially when it comes to lemmy, but kbin is also heavily affected
@hellfire103

@Masimatutu
i agree, and i also recommend friendica!

@YugiohMaster88

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