@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
@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
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
@skullgiver
when it comes to creativity, mastodon ui is a pre-emptive strike against creativity vanilla mastodon does not support emoji reactions, and damn!!!!!!! mastodon ui hides that there are other platforms on the fedi than mastodon mastodon is perfectly fine for all those who want to see mastodon content, and nothing else creativity? no! creativity starts with openness, and mastodon surely has a rather isolating approach
@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
@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
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
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
@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.rssatom feeds are also available:
https://instance.name/@user.atom