ernest
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.
Issues like the one that occurred are typically resolved within an hour, hence this post - mainly to quickly inform that work is underway on it. But you're right, I'll strive to improve communication in the future. Your examples gave me something to think about, thanks.
I don't quite understand what you mean. The problem is that in such a case, it's challenging to provide a specific estimate. That's why I occasionally provide updates in case the work is prolonged. It seems to me that this is how it works. Issues arose without any interference in the code or infrastructure. I addressed hardware problems, but it turned out that wasn't the only issue. Throughout this entire period, I've been attempting to ensure that the instance operates as smoothly as possible. It should be significantly better now, but I'm still actively working on it. Unfortunately, taking a holiday break here doesn't help either.
Yeah, It's true. Since Sunday, I've been noting errors that I'm still working on resolving. It doesn't make it easier that it's the post-holiday period, and due to travels and security measures, it's not the easiest task. I'm working to get everything back to normal as soon as possible.
https://kbin.social/m/kbinDevlog/t/729349/RTR-49-On-site-work
By default, it's 11MB if I remember correctly. However, during the recent issues with the instance, we could modify this value at the server level. Once Piotr is back, I'll verify and restore the default values.
Additionally, the suspension of other work was a conscious decision on my part. I believe that the code at this stage needs to be deeply refactored, and that's exactly what I am doing. Solid foundations are the only option for the project to survive and grow in the long term, and to be properly scalable. Adding more blocks to what I have always considered a prototype (which forks do) makes no sense to me.
Hey, I will get back to this thread and the comments at the beginning of next week. I am able to quickly address some of the issues you mentioned in your post. Changes will undoubtedly be implemented gradually, but for now, the redesign of the ActivityPub module takes higher priority. Once that is completed, the development of the frontend part of the platfrom will truly pick up pace.
My priority is definitely the development of kbin-core, especially now that work on the app has started. For now, I prefer to focus my attention on adapting the API to the latest features. It may turn out to be necessary sooner than expected ;)
I'm currently working on solving this problem.