kbin.social's admin (and kbin currently only supports one admin per instance) is also the main dev.
As I understand it, the sudden unexpected popularity of kbin caused infrastructure issues and made fixing bugs and limitations more important, while he still has to reach his feature goals to secure funding so he can actually continue working on kbin full-time. Additionally, real life had a lot of negative surprises in store he had to deal with.
All in all, he hasn't had much time at all to properly moderate the instance, And the past two weeks he's been gone entirely for real life reasons, leaving the instance unmoderated.
It's not an issue with the software itself, just with kbin.social (and of course other badly moderated instances) specifically.