Working on /kbin https://fedidb.org/software/kbin
I'm currently working on solving this problem.
Quick April Update
Hello everyone, I hope your holiday period passed peacefully. The status page is ready, and I'll soon put it online. I've also made some improvements to the new project website, which will be replaced shortly. Today, by the end of the day, two moderators will also appear, more about which will be in a separate post. You can still submit your candidacies to [email protected] - you will receive a short instruction in response. Today, I'm returning to the code of kbin; I need to review and start organizing the repository. It will probably take me a few days to get everything up and running, but as I continue refactoring, I will gradually eliminate errors in the instance. There will probably also be a few smaller updates that I will post on this magazine's microblog.
Until next time.
/kbin next March update
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 [email protected], 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...
/kbin another quick update
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!
/kbin quick March update
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!
/kbin March update
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 ;-)
RE: Is Ernest still here?
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.
RTR#52 Busy month
This month, I managed to wrap up many overdue matters. It seems to me that I responded to the majority of lingering emails, and a few issues turned out to be so important that they took a few extra days. I also dealt with [a certain aspect related to the project, about which I'll be able to share more in a few weeks. Additionally, it was a time I dedicated to education and catching up on certain things. Today, I'm going for a minor procedure at the hospital, and I won't be available for the next 2-4 days. When I return, I'll push all the corrections and fixes I've been working on and present plans for the near future. In the meantime, I'm making sure that the instance operates smoothly.
RTR#51 End of a short break
Last week, I dealt with formalities related to the project and a few personal matters associated with the new year. Unfortunately, there was quite a lot to handle. Today is the last day I'm dealing with this, and I'm returning to the code for the regular devlogs. I'll also take care of current matters on the instance. On Tuesday and Wednesday, there may be short interruptions in the website's operation due to an update.
RTR#50 Plans for the upcoming week
Lately, I've been dealing with a slight fever associated with the beginning of the year. I'm trying to ensure that everything runs fairly smoothly. Today and tomorrow, I need to focus on planning finances for the upcoming year and handle formalities related to the project. In the following days, I'll implement changes to fix recently reported issues, improve support for older media, and make sure to return to the normal rhythm of the previously scheduled work.
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.
Issues with the functioning of kbin.social
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!
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.
Issues with the functioning of kbin.social
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.
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
RTR#49 On-site work
The instance may not be functioning properly for the next few hours. We are working to identify and eliminate the errors. Sorry for that.
related: https://kbin.social/m/kbinMeta/t/728913/Kbin-pages-returning-404-page-not-found
RTR#48 Happy holidays everyone
For the past few days, I've patched up a few minor errors that there was never time for. I also took a short break from coding, but I'm still working on planning the federation. I'm trying to spend a bit more time with my family and recharge for the upcoming week.
RTR#47 Silent tests are being conducted on the instance
Quiet tests of the latest changes and patching of outstanding errors are ongoing on the instance. The remaining changes will be implemented by the end of the week. I have also completed all outstanding formalities related to the project and everyday matters. Starting from next week, work will pick up pace. Until then, I would like to observe what is happening.
RTR#46 Some tests on kbin.social
The weekend tasks are taking longer for me, I found another bug that causes a 500 error, I'm still working on it.. This evening and tomorrow, I will be testing the changes on the kbin.social. If there are any issues, please mention me in the post or contact me directly through the contact form.
RTR#45 Fix some bugs, comment url
Today, a very quick update. I addressed the errors that occurred during voting and the link to the comment in the notification.
All changes from the weekend will be on the instance on Monday at noon.
Arghhh... Sorry, I replied with a longer message from my phone at that time - at least that's how it seemed to me. Now I've noticed that the response didn't send. In short, there must be an application account on the specific instance due to limits, but catch me on Matrix - we'll discuss it in detail.
Ah, there's one more thing I forgot. I would like adding a new post/thread to be done asynchronously to reduce client-side time, but this might extend to next week because even though I have the foundation prepared, I want to thoroughly test it.
RTR#44 Weekend plans
Today, I took care of several overdue formalities related to the project that were weighing on me. Besides the routine refactoring and work on the ActivityPub module, there are a few things I would like to do this weekend:
- Launch the API on the main instance (yeah... again ;))
- Add Aggregate view, collections, and additional filters to the API
- Ultimately fix the issue of errors during voting
- Correct the link to comments appearing in notifications
- Sort out the recent comments and feedback
Is there anything else that should be added to or replace items on this list? :)
//edit: Ah, there's one more thing I forgot. I would like adding a new post/thread to be done asynchronously to reduce client-side time, but this might extend to next week because even though I have the foundation prepared, I want to thoroughly test it.
I'd rather grab a nap there than him exploring new places ;)
This little guy. I won't take a current photo because even though it's quite snowy in Poland, he won't avoid any puddle or mud, so he temporarily changed color :p
https://pixelfed.social/p/ernest/586197388701623684
https://pixelfed.social/p/ernest/586196209516127144
RTR#43 Break time
I just got back from a over five-hour walk with my dog. I had promised him that for a long time, and both of us really needed it ;-) Now, a quick lunch, and I still have an evening workout ahead of me. Today, I decided to take a break from coding, although I probably won't resist doing something, and at night I'll probably tweak something on the project website or work on something that doesn't require too much thinking. Tomorrow morning, I have to finish a few formalities and get back to 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.
RTR#42 Working on federation and creating documentation
Another day has passed for me working on code refactoring and federation development. In the process, I'm also creating better documentation that can be utilized for other apps integrations. I also had a few formalities related to the project to take care of today, and there are more to address tomorrow.
Closer to the weekend, there might be something more concrete that will be visible on the instance.
There are some tools there that I use for the development of the AP module. Among them is Yunohost, which allows for quickly creating test instances of many federated applications with just a few mouse clicks. It's a good choice for someone looking to embark on a self-hosting adventure.
RTR#41 Working on federation and adapting the API
Today, a really quick update - I continue working on the federation and begin adapting the API to the new codebase, implementing the latest changes and features.
@Damaskox Could you send me the URL from the notification via private message, please?
@Damaskox Pagination? I plan to fix that in the coming days.
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 ;)
Sorry, due to recent work, I missed a few notifications. Moderation tools have been consistently expanded over the past month. I have one more specific thing on the to-do list, and I just need to create a team of global moderators. This is my goal for the coming month. Further work on the ActivityPub module will also primarily involve improving communication between instances related to moderation.
Sure thing, I've noted that some accounts are stuck in the queue for deletion. This typically applies to older accounts. I'm currently working on it, and everything should be functioning properly soon. Your request is in the queue. Sorry for that.