/kbin is certainly not dying, as @fr0g pointed out, work on new features and bug fixes is ongoing. However, it may give the impression that it is, and for that, I take full responsibility and owe you an explanation.

Several factors have contributed to this situation. The first and most significant reason is my family issues, which I must prioritize. I’m doing my best to stabilize the situation as quickly as possible, but not everything is within my control. The second reason is unfortunate financial matters. When Kbin suddenly gained popularity, the project’s maintenance costs far exceeded my initial estimates. While community support still allows for the cluster’s maintenance, I also need to take care of my own livelihood and commitments. Another reason involves spam campaigns and other issues that I need to address behind the scenes. I don’t want to go into specifics right now, but there will come a time when I can share more. My top priority is to resolve all these matters so that I can return to working on Kbin full-time.

I spend every spare moment writing code and reviewing code? from other contributors. It’s a lot of work that goes into development, and I try to verify every accepted pull request and make improvements when I can. It also takes up a lot of time, more than it may seem. I have also delegated some responsibilities and permissions to the Kbin core team (https://codeberg.org/org/Kbin/teams), which has allowed the project to continue to grow, and I am immensely grateful for that. However, I still want to maintain overall control, although over time, we will work on better processes to make it less dependent on me.

I paused updates on kbin.social some time ago until the release of the first version. Hence, the impression that nothing is happening. Kbin is, in fact, developing so rapidly that I wouldn’t be able to respond to potential issues quickly enough, adding to the stress.

I’ve given myself a deadline to resolve all my issues and release the first official version by the end of September. If I can’t meet the deadline, I will step down from leading the project and transfer full rights over the repository and instance to the contributors. Of course, this includes the budget I mentioned earlier, earmarked for instance maintenance.

I feel truly awful about this. I can’t even keep up with threads on Matrix Spaces, notifications here, etc. Right now, the only way to contact me is through the contact form. However, I want to catch up on everything as soon as possible and stabilize the situation. It’s crucial to me, but at the moment, I can’t put it above family matters. I apologize for letting you down, and I appreciate your words of support. If it weren’t for such an amazing community, I might have given up a long time ago.

  • DarkGamer@kbin.social
    1·
    1 year ago

    Self care first, my friend. When you are okay then you can worry about others. All the weight doesn’t have to be on your shoulders.

    I appreciate what you’ve built so far and the rest can come as it does. It’s not worth running yourself ragged over. I hope things resolve well with your family issues, many thanks and no gripes here. Kbin remains awesome as-is and I’m sure it will only get even better eventually. Every improvement doesn’t have to be today.

  • TellumSiege@kbin.social
    1·
    1 year ago

    You’ve done an awesome job. And anyone complaining needs to remember that Kbin/ Fediverse is still in its infancy stages: It’s going to cry, teethe, piss and shit itself when you least expect it. But with the right care (and time), one day it’ll be a lot easier to manage.

  • Seraph@kbin.social
    1·
    1 year ago

    If I can’t meet the deadline, I will step down from leading the project and transfer full rights over the repository and instance to the contributors.

    I respect you entirely but this is a bit dramatic. Not all projects can be on time due to complications and no one is asking you to step down. Please just do what is necessary - you’re doing fantastic!

    Looking forward to the first version!

    • blightbow@kbin.social
      1·
      1 year ago

      Yeah, there is no need for “final solution” style accountability here. This was a project that a single developer was working on when the stars just happened to align and drive a lot of attention to it at once. A commercially oriented website in the same situation would struggle to deal with it and be forced to take out loans in order to expand staffing and infrastructure capacity.

      The phrasing of Ernest’s initial post suggests that there is at least one exploitable vulnerability that spammers are taking advantage of and can’t be openly discussed until the gates are closed. I understand the frustration and optics problem that comes with “easy and important fixes” sliding on the schedule (i.e. the topic of the other thread), but look at it this way:

      • Ernest is too slammed with work to be consciously creating more work for himself.
      • He needs the spam and bot problem to go away so ASAP so that it stops taking time away from him. This includes the missing moderation tools, spam/bot campaigns that are operating at a scale that those additional tools would have difficulty addressing regardless, and the issues he can’t talk about yet that were hinted at above.
      • If he is waiting to push out a fix to problems that would greatly reduce his workload, there are very good reasons for it.
      • If he is not able to push out fixes that reduce his workload, it stands to reason that fixes unrelated to them are also sliding.