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

  • debounced@kbin.runOPM
    3·
    1 year ago

    great questions! i think the good thing (or maybe bad, depends on who you ask i suppose…) is there isn’t one person or owner of mbin. as of today, there are 10 owners/members of the project with merge privileges on the repo; however, we each need to get approval from at least 1 other project owner to “merge it” into the “main” branch.

    github and the associated mbin matrix rooms are where most of the discussion about features and direction takes place among contributors, but i will try to make it a point to keep everyone here informed when a major change take place. right now we’re trying to catch-up on the backlog of pull requests and enhancements that have been stagnating for months over in the kbin repo. @melroy is also pretty good about keeping the masses up-to-date on recent events if you want to follow him as well.

    finally, one way to look at mbin is viewing it as a superset of kbin, that is, unless the kbin codebase changes dramatically or some other crazy thing happens like a change in license (which wouldn’t be a good thing for kbin), it should be relatively easy to port over upstream changes from kbin that we want to see in mbin. my sneaking suspicion is that mbin will quickly surpass kbin in every way since we don’t have a massive money pit like kbin.social holding us back, the focus is purely on the development of the code base and listening to community feedback/inputs. :-)