Hi everyone,
As some of you may be aware, kbin’s development effort has stalled significantly in the past month or so. I’ve made the decision (for now) to move kbin.run’s codebase to a fork of kbin called mbin. I’ve already completed the migration and users should experience no adverse side effects other than some default visualization changes that can be reverted in the settings menu on the right hand side of the page (click on the gear icon).
I am closely monitoring the situation with kbin, but the enhanced security of mbin alone (a version bump in the dependencies) was enough to convince me to make this change in order to maintain the security of my system. NO domain changes will take place and functionality is 100% compatible with kbin in its current state.
Constructive feedback is always welcome, thank you for the continued support and utilization of kbin.run.
Have a great weekend,
-debounced
Yes, I created the Mbin fork. Expect this fork living forever, Kbin development WoW caused to stalled development. Mbin is community-focused. Despite I was the creator of the fork, various contributors do have owner rights on GitHub. It’s build on trust and there will be no single maintainer. Development has been accelerated since. Due to Ernest inactivity and unresponsiveness in the past couple of months (year?), I didn’t saw any other way then creating a fork.
Thank you for the info, I can definitely understand why you needed to fork at this point. I respect Ernest a lot, but he’s one man with other responsibilities and things going on in his life.
See my follow up post here: https://kbin.melroy.org/m/updates/t/55330/Mbin-is-born-Fork-of-kbin