Looks like the admin for kbin.lol has some pretty valid gripes with the current status of Kbin. I have to agree, you can tell the platform is not up to speed at all.

Kbin looks visually great but the backend just isn't there. Check out his statement, it's worth the read.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 1 year ago (3 children)

Yes, definitely problems federating, kbin.social is under quite some load and I made a new kbin instance (I'd previously only been testing). It's been up over 2 days and not received a single thread or comment from kbin.social. In the meantime it's filling with content from lemmy instances, like this thread for example.

But, I'm sticking with kbin for a few reasons. First as you say it's a younger project and things will only get better, and as a software developer maybe I can help with that some. But, also because I like how it looks and prefer it over others.

I think there's a lot of functionality missing, but it's going to come over time. For people not prepared for this kind of bleeding edge operation I'd certainly not blame them for wanting to use a more established project.

[–] [email protected] 2 points 1 year ago

I'm surprised you're having trouble federating with kbin.social- that's always been working for me from my personal instance. I have trouble federating with a few lemmy instances though. Lemmy.ml is still blocking the kbin useragent. And the communities of infosec.pub, sh.itjust.works, sopuli.xyz, among others- cannot be discovered from kbin.

[–] [email protected] 1 points 1 year ago

Actually- scratch that. updates from kbin.social are definitely slowed to a crawl right now.

[–] [email protected] 1 points 1 year ago

As long as you're happy with it, it's best if there's a diversity of projects each trying to do a different thing. That's one reason why I stuck with lotide as long as I did (and I didn't stop hosting it)