I don't think you get my point. I'm not advocating to relicense kbin code or make it closed. Everyone will always be free to fork and make their own kbin-like client if they're unhappy with the original. I'm also not suggesting taking kbin off Fediverse.
Right now, I think only 1 person has complete power over the domain kbin.pub, and the git repository. So that is as centralized as it gets. Same thing with the kbin.social instance, but I'd like to keep administration of the kbin project sepatate from the kbin.social fediverse instance (both can live without the other). I'd like the current main kbin client project (the only?) to get proper administration and financing.