ernest

This update introduces the ability to request the takeover of abandoned magazines. The karab.in instance has been updated to the latest version of the code, which prepares for the kbin.social update after some tests.

• list of abandoned magazines (owner hasn't logged in for a month)
• the ability to submit a request for taking ownership of a warehouse @todo
• section in the administrator panel where one can reject or confirm the takeover of a magazine @todo

Time remaining for the kbin.social update: ? days.

/kbin Road to Release

https://codeberg.org/Kbin/kbin-core/pulls/1216

Architecture is a structure, a way to distribute your application components in various groups. There is not a single way to organize your projects because it could depend on several aspects like project state, team size, time constraints, etc

From today, I'm starting a small series of daily devlogs where I'll be describing the changes being implemented before the official release of the first version of /kbin. As I mentioned earlier, I had some minor turbulence in my private life from which I'm slowly emerging. I have partially stabilized my life situation in various aspects. I hope this will help me smoothly return to old habits, maintain consistency, and keep you updated on what specifically is happening in the project.

There's a lot of mess I need to sort out, starting from overdue tasks that failed in queues, improving the infrastructure, and ending with going through pending emails and private messages. The first report will be out either today or tomorrow evening, as I am just about to start working on it.

https://kbin.social/m/kbinDevlog

Today, a technical server malfunction occurred. Unfortunately, it wasn't the planned update yet. The upcoming one will definitely be much shorter ;)

For the next few hours, there may be some unusual errors. We're still working on it. I apologize for the inconvenience.

This week (at the latest at the beginning of next week), there will be a several-hour technical break. A banner with detailed information about this will appear 24 hours before the planned work.

Have a great week, everyone!

/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.

We’ll eventually understand how these sounds are created and how they get to your ears, but we have to start by talking about the medium that is most commonly associated with sound – air.

Annual ear infection: completed.