TheVillageGuy

I know some of you consider this as documented whining. I hear you but won't stop sharing my opinion and reminding. I recommend continuing commenting on the original post to keep it a bit organized (this post is a link to it)

Update: this thread has gotten out of hand. This is not what I intended, this is not what anybody should want. Let's leave it at this, for now.

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.