this post was submitted on 28 Jun 2023
5 points (100.0% liked)
/kbin meta
4 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.