I'm currently working on solving this problem.
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.
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!
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.
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.
@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 ;)
@testing Thanks for the summary. I will check those cases.
@testing Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;)
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!
@bluGill it should be okay now
@bluGill I will check what's happening, there seems to be some issue.
You can find it in the options in the sidebar.
Hey, I still have one blocker before publishing the API on kbin.social related to infrastructure. The issue is dragging a bit, but by the end of today, I'll try to launch the API on my second instance so that you can familiarize yourself with the structure, docs, and I can make any necessary corrections as quickly as possible. Thanks!
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
Hi @maegul, I just wanted to let you know. It's not perfect yet, but it's something I'll be working on in the coming months after the first release. Thanks for pointing it out, it's a relatively simple change, but it makes a significant difference in the overall experience.
https://kbin.social/sub/active https://kbin.social/sub/microblog/active https://kbin.social/sub/comments/active
Framasoft starts talking about the upcoming features for PeerTube, as well as next year's plans. German newspaper Zeit interviews Eugen Rochko. Fediverse safety.
Framasoft starts talking about the upcoming features for PeerTube, as well as next year's plans. German newspaper Zeit interviews Eugen Rochko. Fediverse safety.
The monthly update for Bluesky, Dutch broadcaster NPO joins the fediverse, and German news organisation Heise Online reflects on a year of being on Mastodon.
The monthly update for Bluesky, Dutch broadcaster NPO joins the fediverse, and German news organisation Heise Online reflects on a year of being on Mastodon.
Today, I started working on a provisional spam protection that should at least partially relieve admins of other instances. Work on this will continue, and the tools will be improved over time. Additionally, a few optimizations have been implemented to speed up the platform's performance, along with corrections for administrative tools.
ernest @kbin.social Working on /kbin https://fedidb.org/software/kbin