lemmy is the more mature platform, whilst kbin is newer and more feature rich.
What it amounts to is that kbin can do things that lemmy can't do, but the things that they both do, lemmy tends to do better. And as kbin is effectively in alpha at the moment, it doesn't have much documentation, making installation and configuration a challenge.
The biggest point of difference in features is that kbin is aware of other fediverse content in a way lemmy isn't. kbin and lemmy both talk to each other really well, but kbin also natively supports other types of fediverse groups (gup.pe, friendica and chirp). kbin also lets you see non threadiverse content, by attaching hashtags to groups. So if you set up say a cycling group on kbin, you can also make the group watch the #cycling tag, any any mastodon or other micoblogging content will appear on a special tab in your cycling group.
So if you set up say a cycling group on kbin, you can also make the group watch the #cycling tag, any any mastodon or other micoblogging content will appear on a special tab in your cycling group.
Now that is a powerful feature. Great way to fill a feed with content too.
(Not shooting the messenger, just as info for other readers.)
Using hashtags for this seems like an idea with some severe limitations because it can only see the posts it has happened to come across otherwise. (Unlike the other group formats.)
Yep, but that's true of keyword search on all fediverse platforms, and unlike lemmy, you can follow micro blog fedi accounts from kbin, so you can federate non group content in more readily
Lemmy and kbin are two different forum software that can be installed and run on servers. Because both use the ActivityPub protocol, the content between them can be shared. So, a Lemmy user will be able to see content from a server running kbin, using Lemmy.
There isn't an option, you can't even tell but you already have the kbin content.
You can't disable it.
The reason that's happening right now is because kbin is enacting ddos protection using cloudflare so they aren't federating properly, this is a temporary problem.