ernest

joined 2 years ago
[–] ernest@kbin.social 17 points 11 months ago (1 children)

I'm currently working on solving this problem.

 

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 supkbin@gmail.com - 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.

 

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 ;-)

258
RE: Is Ernest still here? (media.kbin.social)
submitted 1 year ago* (last edited 1 year ago) by ernest@kbin.social to c/kbinMeta@kbin.social
 

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.

 

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.

 

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.

 

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.

[–] ernest@kbin.social 11 points 1 year ago* (last edited 1 year ago) (1 children)

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.

 

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!

[–] ernest@kbin.social 11 points 1 year ago (3 children)

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.

 

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.

[–] ernest@kbin.social 49 points 1 year ago (5 children)

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

 

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

[–] ernest@kbin.social 6 points 1 year ago

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.

[–] ernest@kbin.social 17 points 1 year ago

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.

[–] ernest@kbin.social 3 points 1 year ago (1 children)

I'd rather grab a nap there than him exploring new places ;)

[–] ernest@kbin.social 14 points 1 year ago (2 children)

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

[–] ernest@kbin.social 7 points 1 year ago (1 children)

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.

[–] ernest@kbin.social 7 points 1 year ago (1 children)

I feel that our visions for the project's development are too different for this to succeed. At this stage, it will definitely be better to work on our own things, /kbin is open source, so there is no issue with that. There are several reasons for this link, link

[–] ernest@kbin.social 44 points 1 year ago* (last edited 1 year ago)

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.

view more: next ›