Is KBIN dying? Srs Question: Is there any further development or support being done for Kbin.Social Keep getting the error page when trying to block users, create posts, view notifications. Been going on for weeks now. en (kbin.social)

ernest, hace 9 meses

@downpunxx 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.

Arotrios, hace 9 meses

You're doing awesome @ernest - I can't express how much your hard work has made a difference to the Fediverse. This is the only software that really bridges the Lemmy / Mastodon divide, and given how new it is and the fact that Kbin's uptime is better than lemmy.world - that's remarkably impressive. Take care of your family, and pace yourself - take a break if you need to, but don't feel like you need to quit because folks expect one man to do the unpaid work of multiple admin teams. Step back and delegate if you need to, but don't step down - you're an excellent leader and the current success of Kbin is proof of that.

@downpunxx Kbin is definitely not dead. These are just growing pains. I believe the bug you're encountering is related to domain blocking. Try unblocking any domains on your block list and you should see the commenting bug go away - this may fix the notification issue as well.