Thanks for putting in something awesome, @ernest! Not sure if you want feedback, but functionality is as full as I know it to be. Maybe better. It is really fast right now! Hope you are on the mend.
Great to hear kbin is back on track, and assumably so are you @ernest. With so many improvements having been made, however, I can't help but wonder if and how these changes are being made public?
The issues that started occurring on Sunday turned out to be more serious than anticipated, extending beyond the application code. We are still working on resolving them to ensure the proper functioning of the website, but we need some more time. Apologies for any inconvenience.
Good luck trying to convince this man. I'm sad to say that what I predicted, now two months ago, is happening. My advice; don't rely on kbin.social, find another instance (I recommend Mbin) or make one of your own.
In hindsight maybe we should have responded by saying we merged your mistake intentionally to see how you'd respond.
i am not being serious of course, as that's not our community's nature. Even though it's allowed to gather proof, we (I am quite sure I can speak on behalf of the community here) would never intentionally introduce bad code into software which is being actively used.
Ernest, you have seen me before, pleading for you to change your ways, on all fronts. This, sadly, degrades the faith I have in your project being suitable for being used in production, from a pragmatic point of view. Kbin may be reliable, but you are not.
You are right. But was the whole debacle that lead to this fork being made worth it? Wouldn't it have been much better if Ernest had just sorted out all himself and we'd all be working on the same project together now instead of introducing mistakes into forks too see what happens? What a complete waste of time, especially under the current circumstances.
As a person who hangs around in repos but isn't a developer that sounds totally insane.
Why do you hang around there then? So you can write articles like this in an attempt to stir the shit? What is there to gain from that, for the fediverse?
I'd also like to know how you hang out there then, as I can't seem to find a person called Density hanging around? I might not be looking in the right place, of course
Ernest has said many things in the past and many times has not lived up to his promises. So I doubt this words now. Also he's already contradicted himself on this matter.
Real-life stuff was kinda more important for me at the moment than managing the project.
As it should be, always, for everybody, you won't ever hear me judge you on that, so please don't try to make me look bad by implicitly suggesting I am.
What you failed to do however is delegate, even temporarily, your responsibilities to people you trust. Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill. It seems keeping them on a leash was kinda more important to you than securing the future of kbin.
I won't go on about this any further.
I hope I'll never have to mention this again, so you'll never have to. Which would imply that you'll have come to terms and lived up to your promises, both recent ones and from the past.
Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn't visible from the outside
I am sorry but I'm having a hard time believing you when you say that you were seriously trying to delegate, as not a single soul ever said anything which would remotely confirm this. I believe you had conversations, but they ultimately didn't result in anything in this context.
However, in that mental state, the last thing I wanted to do was resolve conflicts among adults
I am not sure how to interpret this as there were no conflicts that I'm aware of that needed resolving during your absence, everybody was just waiting
I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.
There's nothing wrong with being like that, there are other people willing to do things like resolving issues. Like me. I realize I appeared out of nowhere. As a new instance owner it took a while for me to notice, but when the situation became clear to me I was ready to jump in and help, just like all the other people who had offered their help (before me).
You've basically just admitted that you were either incapable of or unwilling to engage in structural problem solving and management of the kbin project. That's fine, but you should have reached out and informed the community as soon as you became aware of this.
forking turned out to be the best thing that could happen
Yes, forking can have positive side effects and perhaps having two versions in development synchronously can merit more than one. This however was not the proper way to achieve this and using it as an excuse to justify your behavior and inaction is unjust.
However, it is not too late. You can still do the right thing by starting delegation now, by clearly assigning multiple people to all essential tasks, and giving multiple people complete control of kbin.social, so that, should a similar situation occur in the future, you and the community will confidently know that the project will not grind to a halt again.
Then seek a constructive dialog with the mbin community and we can make the project, in it's current for, work. Together.
If you feel uncomfortable with or are have trouble doing any of this, as you've clearly indicated you'd rather spend your time on coding, you are always welcome to ask me for advice.
/kbin is feeling great right now (kbin.social)
Thanks for putting in something awesome, @ernest! Not sure if you want feedback, but functionality is as full as I know it to be. Maybe better. It is really fast right now! Hope you are on the mend.
Issues with the functioning of kbin.social (kbin.social)
The issues that started occurring on Sunday turned out to be more serious than anticipated, extending beyond the application code. We are still working on resolving them to ensure the proper functioning of the website, but we need some more time. Apologies for any inconvenience.
Mbin: A kbin fork that promises to never review PRs before merging them (kbin.social)
Somebody who was previously active on the kbin codeberg repo has left that to make a fork of kbin called mbin....