Submitted 1 year ago by Blaze@discuss.tchncs.de to fediverse@lemmy.world
https://github.com/MbinOrg/mbin
cross-posted from: discuss.tchncs.de/post/4735963
Learned about this fork from a post about a potential shutdown of Fedia.io, a Kbin instance.
As you can see in the comments, kbin.run already moved to Mbin.
Interesting to see if that can help with the development of new features compared to kbin being managed mostly by the main developer.
Is it me or the description leaves something to be desired? What is it that sets it mbin apart from kbin, wasn’t kbin developed by “the community” in the first place?
The general issue of Kbin is that most of the development has to be approved by the main contributor of the project.
This fork is meant to be easier to contribute to. Let’s see how it evolves.
It makes sense to approve things and keep navigating in one direction. What was the original problem?
It’s a good move I feel. The original velocity on kbin has been lost over the past few months as the main owner struggles to get his own personal stuff organized. I’m pretty happy with this fork, the idea being that everyone will be about to contribute and perhaps these changes will eventually be brought back into kbin if they’re open to it.
originalucifer@moist.catsweat.com 1 year ago
what are the feature/performance differences that would necessitate me upgrading today?
Blaze@discuss.tchncs.de 1 year ago
You can have a look at the post linked in the OP. The Fedia admin had issues running Kbin, which mbin seems to have addressed