Over the next few weeks, we're facing another server change. I'm doing everything to optimize costs and prepare the instance for long-term operation. More details are available on the status page I'm currently working on.

This week, I also refreshed the project's code, and it seems like I'm slowly getting back on track regarding health matters.

Soon, there will be several moderators on the website - if you'd like to help with this, please write to supkbin@gmail.com, mentioning your nickname in the message. Moderators will be selected based on profile activity - there might be a few additional questions in the reply. However, remember that moderation is not always a pleasant task, so think it over. All moderation actions are transparent and subject to public evaluation.

Most importantly, I've sorted out my personal matters and, in a way, financially secured myself, so starting next month, I'll be able to fully dedicate myself to the project for a few months, focusing solely on it, which I haven't had the opportunity to do for a some time again. More information coming soon...

Good morning, last week we managed to address pressing issues related to infrastructure. Thank you once again for your assistance, Piotr. I will continue work in this area, but it will be less invasive and cumbersome. I have restored the test environments and am slowly getting back into coding.

Today, I will start by organizing abandoned magazines, mag mods requests, checking user account deletions, etc.

This week, additional global moderators will be added to the instance. Tomorrow, there will also be a post where you can submit your candidacy.

Additionally, this week, a Status page will be introduced - where you can check for any instance outages and their repair status.

Various communication issues still remain before I dive into the code. But overall, things are progressing more and more rapidly. I will also try to provide more frequent updates.

Have a great week, everyone!

I'm slowly catching up with backlog tasks and cleaning up instances, but there's still quite a bit to do. Day by day, I'm managing to work longer hours, but I still need some time to ramp up the intensity of work. Just wanted to let you know that there might be brief downtimes in instance operation over the weekend. I aim to resume communication on Monday and write some code.

Have a great weekend, everyone!

I'm feeling a bit better. Starting today, I'll be returning to work as much as possible. This week will likely be spent catching up on tasks, replying to emails, reading overdue comments, etc. I also need to work with Piotr on instance infrastructure. I'll be more actively handling spam as well, but it's clear that we need additional people for global instance moderation. I'll prioritize this. I'd like to delegate instance administration as much as possible and fully focus on code. In short, there's a lot of work ahead, but I aim to reach a point by the end of this month where I'm 100% focused on code development, and hopefully this time there won't be any unpleasant surprises. The past few months have been overwhelming with a series of unfortunate events ;-)

I check in here quite often, but for now, I'm just focusing on clearing spam and keeping the instance alive. In January, I was working on the AP module, and there has been significant progress in the work, which hasn't been publicly published yet. Unfortunately, at the beginning of the year, I developed a skin condition that worsened from week to week, reaching a point where I couldn't even leave the house. In February, I spent my time visiting doctors and undergoing treatment with medications, which often had very unpleasant side effects. Therefore, I decided to hold off on any major updates to avoid causing even more chaos. Today, I've undergone one procedure, and I have another one scheduled for Thursday, which I hope will be the last.

Just because it's not visible that something is happening doesn't mean I haven't been doing anything during this time. In fact, two really significant things have been successful, which I've been working on for a long time and which I intended to announce soon once I recover.

This weekend, I also plan to work on infrastructure with Piotr, and from next week onwards, I intend to resume committing, provided my health allows it. I understand if you're exploring alternatives, but I hope I've exhausted my bad luck limit for this year, and the remaining time will be marked by gradual, steady progress, especially since new opportunities have emerged, about which I will hopefully write soon.

The main issues with the improper functioning of the instance have been resolved, but it led to additional complications. Currently, using the instance should be quite comfortable, but I will continue to work intensively on a comprehensive solution for the next few days. Therefore, occasional interruptions or errors may still occur.

Thanks for your patience!

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.

@testing Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;)

#kbinMeta

Today, there may be transient issues with voting, counters, etc. I'm working to resolve the issue as quickly as possible. Also, there might be 2-3 brief interruptions in the website's operation. Thank you for your patience!

Today, I continue with code refactoring, getting closer to finishing the most tedious part. I've also improved tools to prevent spam on the instance, which will take effect in a few days, addressing the issue of overloading other instances that have been reported. After today's wave of spam, I've also started working on notification reports for magazines owners, which nicely aligns with the current code changes.

I've encountered an error a few times during upvoting, and it seems to occur when attempting to block users as well. I've made initial attempts to address the issue, but finding the bug might take some time. If the instance returns this error, please mention me in a post on kbinMeta along with the post URL and the time the error occurred. Together, we'll identify and eliminate this bug much faster :)

You can track changes in the official repository
https://codeberg.org/Kbin/kbin-core

or on Github
https://github.com/ernestwisniewski/kbin