RedSquadCampFollowerwhat happened to kbin?
ChozoErnest, the lead dev for Kbin, has had a lot of big events happen in his life recently, so he has a tendency to just kinda disappear for weeks/months at a time while the project gets put on hold. He'll usually come back, announce new plans for development, maybe push out a few updates, and then inevitably go radio silent again.
I believe he's got a few people assisting him now, but development has definitely slowed to the point of becoming concerning. I think it might be time for the Mbin team to start getting a little more free with the fork.
originaluciferI think it might be time for the Mbin team to start getting a little more free with the fork.
eh? what do you mean?
I believe that currently, Mbin isn't making any drastic changes, and relying mostly on Kbin's existing code as its base. As far as I'm aware, the Mbin team are mostly just doing maintenance-level development; fixing things as they break and making optimizations, but not so much in the way of developing new features. Mbin is currently just basically a copy of Kbin, without much distinguishing the two.
Since Kbin doesn't seem to be moving much at all, I think it might be a good idea for Mbin to start flexing their own muscles a bit, and making it into its own separate project. Otherwise, having a copy of a stale project just leaves you with two stale projects.
BentiGorlichMbin isn't making any drastic changes
UI wise, that one is definitely true
and relying mostly on Kbin's existing code as its base
This one most certainly not. We actually stopped porting kbin code a few months into the project, because it just was too much work and it was obvious that Ernest didn't want us to. So everything which changed on mbin in the about 8-10 months since, was purely our own work. Of course the basis will always be kbin, but the form will most likely change
We've been keeping the UI mostly as is, because we all like it, however on the backend site of it a lot has changed. The biggest problems kbin had were compatibility wise (federation) and scaling wise. These were the points where we made huge changes. The federation compatibility has improved a lot (yes there is still a lot to do) and scaling/performance has also improved a ton.
The biggest UI changes we made are:
- new filter designs that work for threads as well as microblogs
- a subscription panel
- a usable instance wide modlog
- a cake day display
- and more stuff that I am forgetting at the moment (it's been a while since I looked at kbin and I am mostly a backend dev)
The backend changes we improved are (imo) more impactful:
- (next release) direct messages are federating
- (next release) pins federate
- deleting users federate
- magazine descriptions are federating correctly
- mods federate
- reports federate
- incoming likes are working
- the "hot" sort actually makes sense with lemmy content because it also looks at upvotes and not just at boosts
- completely redone the hashtag system so it scales at all
- completely redone the background worker system so it scales better (partly next release)
And these are only the changes I could think of in 5 minutes. We likely changed a lot more things, which I just forgot.