@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
zu testzwecken > this is my favorite alt acc on the fedi
@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 🙏
@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
@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
@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?
@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
@ThatOneKirbyMain2568
defederate!
@maegul
it’s sad to see that, and all of it was foreseeable in april 2023 already …
The solution, however, is not to reduce the number of instances, but rather to provide more tools for instances to group communities together.
kbin collections are grouping together communities, but unfortunately, collections themselves do not federate
@gicagaf805
@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
@feditips @fediverse @FediFollows @mention @masimatutu @HamSwagwich
@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
deleted by creator
@indigojasper
wholeheartedly agree!
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
@ThatOneKirbyMain2568
moreover, i would love to see kbin and mbin devs joining forces, thereby reducing each other’s workload :)