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

@livus
compared to other *keys, sharkey development is rapid atm, but so far, @Amelia and @Marie have not put federation issues with kbin and lemmy into focus - this is why i tagged them

@Vej @scrubbles @Blaze @brome

@livus
accs on misskey and its cutlery set (firefish, foundkey, iceshrimp and sharkey being the most important among them) are mostly unaware of what is happening on the threadiverse

mostly using a hajkey acc myself, i agree with @brome - although i tend to use kbin more frequently now, as kbin development regained steam

if sharkey were able to federate better with both kbin and lemmy, this would be a giant leap @Amelia @Marie

@Vej @scrubbles @Blaze

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 …

@fox yup