@JohnDClay
massive database issues - stux gives some explanation in the linked thread
@ernest thank you for all the work you have dedicated to kbin!
i wish you are getting all support needed right now!
@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
@ThatOneKirbyMain2568
given the sheer size of threads, most fedi platforms still lack well-developed moderation tools > this is a tough nut to crack, thus preemptive defederation is a must when it comes to threads
@BiggestBulb
using kbin mostly on mobile devices, i am time and again surprised that kbin works kinda fine > e.g. kbin deals better with bad internet connections than any other fedi software i have come to know so far > given that kbin is still early beta, this is impressive
i think that we should be patient, and keep reporting bugs :)
@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
@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