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

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](https://kbin.social/u/testing) Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;) [\#kbinMeta](https://kbin.social/tag/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](https://codeberg.org/Kbin/kbin-core) or on Github [https://github.com/ernestwisniewski/kbin](https://github.com/ernestwisniewski/kbin)

<details><summary>Knock knock. </summary>Who's there? Lettuce. Lettuce who? Lettuce in, it's cold out here! </details> [\#kbin](https://kbin.social/tag/kbin) [#kbinMeta](https://kbin.social/tag/kbinMeta)

Hi [@maegul](https://hachyderm.io/@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/active) [https://kbin.social/sub/microblog/active](https://kbin.social/sub/microblog/active) [https://kbin.social/sub/comments/active](https://kbin.social/sub/comments/active) [\#kbin](https://kbin.social/tag/kbin) [#fediverse](https://kbin.social/tag/fediverse) [#kbinMeta](https://kbin.social/tag/kbinMeta)

Fediverse ernest • 10 months ago • 100%

fediversereport.com

Framasoft starts talking about the upcoming features for PeerTube, as well as next year's plans. German newspaper Zeit interviews Eugen Rochko. Fediverse safety.

Fediverse ernest • 10 months ago • 100%

fediversereport.com

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.

The instance has been updated to the latest version of the code. For the next few hours, there might be issues with communication in the fediverse. We are working on it, and everything should return to normal shortly. I'll keep you updated. [https://kbin.social/m/kbinDevlog/t/613299/kbin-RTR-8-The-update-of-kbin-social-and-plans-for-the](https://kbin.social/m/kbinDevlog/t/613299/kbin-RTR-8-The-update-of-kbin-social-and-plans-for-the)

This update introduces the ability to request the takeover of abandoned magazines. The karab.in instance has been updated to the latest version of the code, which prepares for the kbin.social update after some tests. * list of abandoned magazines (owner hasn't logged in for a month) * the ability to submit a request for taking ownership of a warehouse @todo * section in the administrator panel where one can reject or confirm the takeover of a magazine @todo Time remaining for the kbin.social update: ? days. [/kbin Road to Release](https://kbin.social/m/kbinMeta/t/588413/kbin-Road-to-Release-devlog-series) [https://codeberg.org/Kbin/kbin-core/pulls/1216](https://codeberg.org/Kbin/kbin-core/pulls/1216)

Programming ernest • 11 months ago • 100%

github.com

Architecture is a structure, a way to distribute your application components in various groups. There is not a single way to organize your projects because it could depend on several aspects like project state, team size, time constraints, etc

From today, I'm starting a small series of daily devlogs where I'll be describing the changes being implemented before the official release of the first version of /kbin. As I mentioned earlier, I had some minor turbulence in my private life from which I'm slowly emerging. I have partially stabilized my life situation in various aspects. I hope this will help me smoothly return to old habits, maintain consistency, and keep you updated on what specifically is happening in the project. There's a lot of mess I need to sort out, starting from overdue tasks that failed in queues, improving the infrastructure, and ending with going through pending emails and private messages. The first report will be out either today or tomorrow evening, as I am just about to start working on it. [https://kbin.social/m/kbinDevlog](https://kbin.social/m/kbinDevlog)

Today, a technical server malfunction occurred. Unfortunately, it wasn't the planned update yet. The upcoming one will definitely be much shorter ;) For the next few hours, there may be some unusual errors. We're still working on it. I apologize for the inconvenience.

This week (at the latest at the beginning of next week), there will be a several-hour technical break. A banner with detailed information about this will appear 24 hours before the planned work. Have a great week, everyone!

Technology ernest • 12 months ago • 77%

www.youtube.com

Recently voted the most iconic monument in Britain, Big Ben has come to symbolize the sights and sounds of a nation but ever-needy machinery. Her attachment to Britain's parliament building means that making sure she remains reliable is Big Ben's greatest challenge this year. Following her 150th anniversary, the keepers of Big Ben must ensure the monument stays clean, timely and most importantly, does not stop at an inopportune moment. Political elections, and royal and state visits alike all pass below its famed clock faces. But as history continues to be made on its doorstep workers behind the scenes must do everything from keeping pigeons at bay with a Harris Hawk patrol to monitoring a rather worrying tilt.

/kbin is certainly not dying, as [@fr0g](https://kbin.social/u/fr0g) pointed out, work on new features and bug fixes is ongoing. However, it may give the impression that it is, and for that, I take full responsibility and owe you an explanation. Several factors have contributed to this situation. The first and most significant reason is my family issues, which I must prioritize. I'm doing my best to stabilize the situation as quickly as possible, but not everything is within my control. The second reason is unfortunate financial matters. When Kbin suddenly gained popularity, the project's maintenance costs far exceeded my initial estimates. While community support still allows for the cluster's maintenance, I also need to take care of my own livelihood and commitments. Another reason involves spam campaigns and other issues that I need to address behind the scenes. I don't want to go into specifics right now, but there will come a time when I can share more. My top priority is to resolve all these matters so that I can return to working on Kbin full-time. I spend every spare moment writing code and reviewing code? from other contributors. It's a lot of work that goes into development, and I try to verify every accepted pull request and make improvements when I can. It also takes up a lot of time, more than it may seem. I have also delegated some responsibilities and permissions to the Kbin core team ([https://codeberg.org/org/Kbin/teams](https://codeberg.org/org/Kbin/teams)), which has allowed the project to continue to grow, and I am immensely grateful for that. However, I still want to maintain overall control, although over time, we will work on better processes to make it less dependent on me. I paused updates on kbin.social some time ago until the release of the first version. Hence, the impression that nothing is happening. Kbin is, in fact, developing so rapidly that I wouldn't be able to respond to potential issues quickly enough, adding to the stress. I've given myself a deadline to resolve all my issues and release the first official version by the end of September. If I can't meet the deadline, I will step down from leading the project and transfer full rights over the repository and instance to the contributors. Of course, this includes the budget I mentioned earlier, earmarked for instance maintenance. I feel truly awful about this. I can't even keep up with threads on Matrix Spaces, notifications here, etc. Right now, the only way to contact me is through the contact form. However, I want to catch up on everything as soon as possible and stabilize the situation. It's crucial to me, but at the moment, I can't put it above family matters. I apologize for letting you down, and I appreciate your words of support. If it weren't for such an amazing community, I might have given up a long time ago.

Hi, in this and probably the next week, I will be working on these tasks: * [https://codeberg.org/Kbin/kbin-core/pulls/357](https://codeberg.org/Kbin/kbin-core/pulls/357) * [https://codeberg.org/Kbin/kbin-core/pulls/815](https://codeberg.org/Kbin/kbin-core/pulls/815) * [https://codeberg.org/Kbin/kbin-core/pulls/132](https://codeberg.org/Kbin/kbin-core/pulls/132) * [https://codeberg.org/Kbin/kbin-core/pulls/823](https://codeberg.org/Kbin/kbin-core/pulls/823) * [https://codeberg.org/Kbin/kbin-core/pulls/817](https://codeberg.org/Kbin/kbin-core/pulls/817) * [https://codeberg.org/Kbin/kbin-core/pulls/785](https://codeberg.org/Kbin/kbin-core/pulls/785) * [https://codeberg.org/Kbin/kbin-core/pulls/798](https://codeberg.org/Kbin/kbin-core/pulls/798) * Change magazine ownership (ongoing) * Delete / purge magazine * Delete user fix (ongoing) * Delete all user posts from magazine (ongoing) * Mod magazine panel view * Logout bug fix * Reports view improvements (ongoing) * Admin guide (create instance instructions) * Transfer test enviroments * First release * Answers to overdue questions, messages, mails... Today, I will be slightly less available as I am in the final stages of taking care of all the formalities, and I also had to handle a few personal matters. Starting tomorrow, I will be back at full capacity again. When this succeeds, in the next releases, I will focus more on frontend and accessibility. [\#kbinMeta](https://kbin.social/tag/kbinMeta)

I wrote the first line of code for /kbin on January 14, 2021. Around this time, I started working remotely and decided that the time I used to spend commuting to the office would be devoted to /kbin. Throughout this entire period, /kbin has been a hobby project that I developed in my free time. It was also when Lemmy started federating. The full history is available on [GitHub](https://github.com/ernestwisniewski). The Polish instance - or rather its prototype - was created on 2021-09-08. By the end of 2022, I decided to take this a bit more seriously. The work that had brought me much satisfaction began to tire me out - anyone who's experienced burnout likely knows what I'm talking about. I needed a breather and a sense of doing things my way. I had some savings put aside, so I could work on this full-time. The amount of code might not reflect this, but it's only a small part of the things that need attention in such a project ;) I don't know if it had any impact, but on January 4, 2023, I received information that the project had qualified for the [NGI0 Entrust program](https://nlnet.nl/project/Kbin/). I had applied for funding a few months earlier. Currently, I have outlined my milestones in the Roadmap. The plan was to gradually complete each stage (after finishing one of them, I can apply for a funds release). However, due to the situation and how /kbin has developed in recent weeks, I had to completely change my priorities. As a result, I have started each stage, but none is polished enough for me to honestly apply for a payout. I'll need to address this promptly. The fact that I could take certain steps amidst all this confusion is solely thanks to your support. The kindness I've encountered here will be remembered for a lifetime :) My buymeacoffee account currently has 818 supporters, who have donated $11,320. This is a lot of money, and for a while, I'll be able to sleep peacefully, not worrying about maintaining kbin.social. Nevertheless, this money is meant for project development. Every expense will be documented in monthly reports. If necessary, I can also provide insight into the invoices. Things have been so heated recently that I consider the spending over the past months to be a failure. Most of the costs need to go to S3+Cloudfront, where costs due to the traffic increased from $2-3 per month to $1,000. This is about half a year of basic servers in the current stack. But in hindsight - so much has happened that faster migration was impossible. However, this has certainly accelerated the process. None of this would have been possible without the contributors and project guardians, and without Piotr, with whom we spent many hours and sleepless nights trying to stabilize the situation and bring it to its current state. This time we're much better prepared for potential surprises. I hadn't set the terms of collaboration before and I admit, I had some concerns when we arranged a call to discuss this. However, it turned out that within the foundation, Piotr introduced a "Pay what you can" financing model, whether it's $1 or $100 a month. As I mentioned earlier, this is a huge relief for me and we started from scratch regarding security matters. Many of you asked me about the possibility of recurring support. I wasn't entirely convinced, especially since the current account balance should maintain the instance. However, I think it would be irresponsible of me not to consider it. /kbin has grown to a level where I can't foresee everything that will happen. It would be great if we could cover monthly costs with [Patreon](https://patreon.com/kbin_pub) / [Liberapay](https://liberapay.com/kbin). All funds from [Buy Me a Coffee](https://www.buymeacoffee.com/kbin) will be transferred to this pool, but from now on, I'll treat it as buying me a coffee... or a beer... literally ;) For me, this also means maintaining critical zones for the project. I see this as a long-distance run, so I've decided to allocate: $100 monthly - donation to [Piotr's foundation](https://ftdl.pl/donate/) "Fundacja Technologie dla Ludzi" - I really encourage you to support it, they're really doing a lot for the fediverse. $24 monthly - [donation to Codeberg](https://liberapay.com/codeberg) - a great ecosystem for free projects. We've been making quite a buzz there recently. I also want to support contributors and creators around /kbin as much as possible - but I'll do this privately, and for now, I can only afford symbolic amounts. ``` | | | | $ | | ------------------------------------------------- | ---------- | ------------ | ---- | | Hetzner Jun 2, 2023 | €131.63 | one-time | 145 | | Hetzner Jul 2, 2023 | €246.74 | one-time | 271 | | OVH 24 cze 2023 | 2246.66 zł | 6 months | 553 | | OVH 1 lip 2023 | 904.63 zł | monthly | 223 | | OVH domains | 116.43 zł | annually | 30 | | AWS (S3+Cloudfront) July 3, 2023 | $1079.21 | one-time | 1080 | | AWS current | $320.45 | one-time | 321 | | Mailgun 2023-07-02 | $49.76 | one-time | 50 | | Testing enviroments, demo instances, landing page | $130 | monthly | 130 | | FTDL | $100 | monthly | 100 | | Codeberg | 95.33 zł | monthly | 24 | | Yubico 2x YubiKey 5C NFC Jun 22, 2023 | €135.30 | one-time | 149 | | Accounting and legal advice | $100 | one-time (?) | 50 | | Taxes in Poland | ??? | | | ``` Thank you once again for that. I will respond to your questions, but it may be delayed as I have a few important tasks I want to focus on. Soon we will also write more about the cluster and the conclusions we have drawn from creating infrastructure with Piotr. Then it will be time for the first release of /kbin.