It has a cleaner interface, and some nice features. I really like tags (what am I saying? I love tags, everything and everyone should have tags!) for posts, where Lemmy doesn’t even have flairs.

Annoyances (excepting the current overloading) are:

• keeps resetting me to all instead of subscribed magazines
• Different nomenclature, Lemmy upvotes are boosts, upvotes are something else, then there’s the different community search, instead of !com@instance it’s @com@instance
• Randomly showing me unrelated tweets or whatever mastodon calls them

I haven’t really used it, so this is all second-hand:

As far as I understand, it’s a younger project with more papercuts than Lemmy, but more features. Instead of just being a link aggregator like Reddit/Lemmy, it’s also got microblog functionality so it plays better with Mastodon. For users of Mastodon, having a one-stop-shop for both services is pretty handy.

It’s much harder and more problematic to set up kbin instances, so almost everyone just uses kbin.social. This means it’s a very centralized fediverse platform compared to Lemmy, but that might be seen as an advantage to some.

The only reason federation wasn’t working was because they had to turn on CloudFlare protection just to keep the site from crashing. That interfered with federation. Assuming they’re able to upgrade enough to handle the traffic, they’ll federate as easily as lemmy does.

It has excellent potential. It has only been around about a month and has quickly received a lot of interest and, from what I’ve read, there has been a surge in code contributions. I think it will be the preferred platform alt-Reddit platform once Kbin resolves its more significant issues and starts adding some QoL features.

@nlm @Barbarian Yes, me and @sj_zero have been having lots of trouble getting #Kbin to federate properly