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
logical change, haven’t noticed any issues or incompatibilities on my end. is there a place where one could keep up with development of mbin from within the mbin system? for example, i follow Ernest for his general updates and discussions about kbin and its direction, as i don’t otherwise ever look at github.
and does this mean that mbin forks here, forever? so if kbin receives large updates down the line mbin is now its own beast and will update and evolve independently?
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. :-)
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
@debounced I’m glad you made ehte change, and I noticed zero downside in my day to day use of the instance. Overall I’m excited to see new features roll out as the Mbin community builds steam.
@debounced I have started running into a problem where “boosting” a comment leads to an error 505. Anyone else seeing that?
i boosted you and downvoted myself, fix seems to work!
yep, this is a known bug caused by one of the recent updates. downvoting will also cause the same/related error, it’s under investigation by one of the devs.
deleted by creator
Now that Kbin has received some updates, I am wondering if we will continue to stay on Mbin or if we will migrate back to Kbin.
I guess I’m a little biased since I’m one of the Mbin maintainers, but we’ve had two significant releases with over 200 PRs that are not part of /kbin. We’re selectively picking /kbin enhancements/code changes that we want in Mbin (and rewriting the ones we don’t like or doing something completely different), but I think the damage is done and our vision for Mbin is not compatible with /kbin. I’m not going to go into all the drama behind the scenes, but I think it’s best if Mbin and /kbin go their separate ways.
