I almost feel like it's October last year, when I pled for improvement on all fronts regarding the Kbin development strategy. Now it seems development has ceased once again and there hasn't been chat on the matrix channels for over a week. Update: that's two weeks now (including his blog) and over a month of no visible Development.
Update: According to https://fedidb.org/software/kbin there are a grand total of 29 active kbin servers. Of 61,489 users on all instances, 59,962 of these are on kbin.social. To those users I would like to say that should kbin.social fail, there will always be Mbin servers to fall back to.
What is going on?
We can only speculate, based on what has happened in the past. Several mind bending theories can come to mind.
Perhaps Ernest (and whatever team still exists) is continuing development in the background, not publicly sharing his work on codeberg. He may have had enough of all the criticism and wants to do it his way without interference. This may sound a bit far fetched, but he's admitted in the past that he prefers concentrating on coding over communicating with his community.
Other theories could involve something bad involving Ernest personally, let us hope that is not the case. Ernest is a great person, nobody would wish anything bad upon him.
But in reality, speculation doesn't change anything, we can only deal with the situation at hand.
I believe waiting for a new release comes with too many risks in the current setting. Nobody can monitor the code during progress or do any testing for themselves while development is ongoing (assuming it is). If anything, what's coming next? Your guess is as good as mine.
A new version may well break compatibility between Kbin and Mbin. Mbin is trying to stay compatible with Kbin for as long as reasonably possible. However, staying compatible with something that is out of sight and out of one's control is challenging, if not impossible. A break in compatibility would mean there will be no easy way to migrate to Mbin after an upgrade for Kbin users who have patiently waited for one, should they want to.
I would not want the future of my instance to be dependent of such a level of uncertainty, now or in the future.
These types of threads always come across as whiny and overblown to me. Kbin works just fine the majority of the time, and it's still my preferred method for accessing microblogging/thread data.
The fediverse is a massive project, if you don't like what one part is doing go elsewhere, you can access most content in a variety of ways and it's good to have alternatives.
I'm far more appreciative of what kbin brings to the table than what all these naysaying posts and circle-jerks bring up everytime there is a lull.
Is there criticism of kbin, sure? But how is this constructive rather than whiny doom bait.
Edit: OPs whole post history is kbin whining. Whew.
yeah I chose kbin because out of the options I found at the time I liked it best. Im not going to make a new account somewhere unless either kbin just gets bad for some reason (and im not someone who jumps ship due to a day or two it would have to be extensive) or some other thing would have to have some sort of amazing features that made it worthwhile and given I like simplicity overall I doubt that will happen.
If your instance admin would choose to switch to Mbin, you'd hardly notice and you'd definitely not have to make a new user account
I mean if kbin switched to mbin then yes I would be using mbin. I was talking more reasons I might make a new account because the old one was not cutting it.
the concern is one day you go to login, and it aint there. at all.
yeah. I would likely make an account in that situation unless it was temporary.