Feeling thwarted by the 404, I suddenly remembered there are plenty of curated feeds over in Collections for us to browse. Have updated one of mine to reflect newer communities.
Currently, on the main instance, people have created 40191 accounts (+214 marked as deleted). I don't know how many are active because I don't monitor it, but once again, I greet all of you here :) In recent days, the traffic on the website has been overwhelming. It's definitely too much for the basic docker-compose setup,...
A certain stage of development has ended - a prototype was created that allowed me to verify whether such a form makes sense in the #fediverse. Until now, it was a project that I developed in my free time. Now, thanks to the great people from Nlnet, I will be able to devote much more time to it. This time, we have already...
I just saw an email from Buy Me a Coffee. Not just one. I went in, and I'm truly shocked. Thank you all for the support; I would like to thank each and every one of you individually someday. Honestly, I don't know what to say. The account balance is $350, which will definitely allow me to develop kbin faster or at least not...
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...
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...
Hi there, in the upcoming kbin releases, I will be describing the changes along with author tags, but for now, you can check out what's happening here: https://codeberg.org/Kbin/kbin-core/activity, as well as my personal feed: https://ernest.dev...
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...
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...
@Ernest has pushed an update which allows users to request ownership/moderation of abandoned magazines. Ghost/abandoned magazines were fairly prevalent after the initial wave of hype due to users either squatting magazine names or becoming inactive for other reasons. Now is your chance to get involved, if you were waiting to do...
It wasn't entirely intentional, it was actually my mistake. But I held off on pushing the hotfix for a while. It was a development branch, so these kinds of bugs were permissible - in this case, it just changed the order of related posts, nothing serious. It was quite easy to spot and fix. Slow and cautious acceptance of pull requests, something I spent a lot of time on, was the main accusation from the creators of forks. Hastily accepting them was a problem for me. I personally considered a consensus similar to that, but now I see it doesn't make sense. Someone needs to take responsibility. Personally, I believe that forks are the best thing that could have happened to the project.
Yeah, that's true. Real-life stuff was kinda more important for me at the moment than managing the project.
For me, it's straightforward: I pushed some dev code that wasn't even a complete feature, and it got approved in your pull request. That's why I was advocating for everyone to only merged their own PRs in the /kbin repository – so that each person could take responsibility for their own work. I won't go on about this any further.
Yes, I say this fully aware - there are many things that I have failed at. Much of what I said, I failed to achieve. However, I never wanted to keep people on a leash; I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.
Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn't visible from the outside. However, in that mental state, the last thing I wanted to do was resolve conflicts among adults, and it all started to boil down to that. As @BaldProphet mentioned - "microcosm of the open-source community."
Moreover, there were too many different visions of the project, ignoring requests, etc. That's precisely why I decided to temporarily halt development, to secure the future of kbin. It was my decision, and as I mentioned, forking turned out to be the best thing that could happen. As you can see, the differences are not that significant, but it will be easier for all of us - especially since we can always draw inspiration from each other, and I don't think anyone has a problem with that.
However, I still maintain contact with many people, and sometimes they mention to me the attitude of certain individuals on mbin's Matrix - it is at least puzzling. In any case, I want to stay away from that and focus on my work with contributors who understand and prefer my approach.
You see, I don't know how I would act now in hindsight. You have to take into consideration that, at the peak, hundreds of people willing to help appeared out of nowhere, people I didn't know at all. By nature, I am rather distrustful and approach new relationships cautiously - I really need a lot of time to get to know another person well. It's true that after some time, a certain structure began to take shape, but not everything is always as it seems at first glance - especially when so many strong personalities converge in one place. Perhaps it was a mistake that instead of addressing many things publicly, I tried to solve them in private conversations.
And you're right, anyone who knows me a bit knows that I have trouble asking for help. Sometimes, I take too much on myself, which is not good in the long run. I'm working on it. But this time was something more. I promised to take care of things, and under normal circumstances, it would probably be easy for me because I have some experience in resolving such situations. But these were not normal circumstances. I realized this too late. I was just overwhelmed by real life. So many problems collapsed on me that I could never have anticipated. These were the worst months of my entire life. I don't want to write too much about it or make excuses, but at some point, even getting out of bed or eating something became difficult. When I tried to get back to the project, the thought of the backlog and how many people I let down made me feel sick. That's why I'm really glad to be where I am now. I can only apologize to you and try to fix some mistakes. I need to do it at my own pace. I want to clean up the mess, find my rhythm, and then engage in broader communication with people. I'm still recovering on my own.
What I did was indeed a bit malicious, but I believe it was the only way to achieve the intended effect. The fact that I really like you all should not mean that I will be uncritical of your work. I don't want you to fully trust everything that comes from me - only in this way can we fully utilize the potential we have in developing the fediverse. Frontend errors are just a trivial matter; they can be quickly found and fixed. However, the situation is completely different when it comes to backend mechanics. Seemingly minor errors when I was developing karab.in made me undo them for weeks. With larger instances, there may not be a second chance. This is not a centralized system, you have to consider others above all. That's why I am so sensitive to it and have so many doubts about making changes.
It's not that I want to make things difficult for you. I really care about mbin developing in the right direction. I am curious about what the future will bring. I would like kbin to remain rather ascetic, subtle, and something that you need to learn and understand a bit, rather than having everything handed to you on a platter. Mbin can be a different face, with more features, bolder, and I know that you have many great ideas for it. A simple example is the labels for marking mods/admins/ops that you are currently working on - kbin has it marked in a subtle way with a faint left border outline - you can do it differently, and that's great. As someone very wise once said, "If it's not diverse, it's not the fediverse."
@melroy I am sure that this is just the beginning of our shared adventure. I hope you won't hold a grudge against me for long ;) Guys, I deeply regret that we met at this stage of my life, but as I say, all I can do is try to fix my mistakes. Thanks for everything!
Oh c'mon, don't be mad. It's just a wrong sorting of posts, it's in an edge case, and seriously it wasn't intentional. I just wanted to check how such management looks in practice, how many merge accepts are needed, etc. I didn't mean to do anything wrong that could cause harm. I even push the same code to my instance to facilitate your tests ;)
But you're right - that's just my nature. I approach PR with very limited trust, whether they're mine or from others.
What mechanism governs federation with non group based instances? I set up some magazines for Running and Cycling on kbin.social, and I've noticed that there is quite a lot of activity of those hashtags from general mastodon instances....
That's right. The entire traffic on the website generates around ~2400 people whom I follow along with their reactions and followed communities. Kbin allows to track both (+ specific domains). I'm not a big fan of relays; I prefer when an instance grows naturally and is built by people. Relays will probably be implemented into /kbin someday, but first, better moderation tools are needed.
and I've noticed that there is quite a lot of activity of those hashtags from general mastodon instances.
Yes, that's a feature of /kbin - based on the magazine's name, posts are assigned to the microblog (soon there will be an option to disable this feature ;)). You can also add additional related tags in the magazine panel that you would like to gather.
Today, a technical server malfunction occurred. Unfortunately, it wasn't the planned update yet. The upcoming one will definitely be much shorter ;)...
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....
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.
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...
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....
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....
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...
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...
If you're encountering the Subscribed 404 error, this is a good time to revisit Collections
Feeling thwarted by the 404, I suddenly remembered there are plenty of curated feeds over in Collections for us to browse. Have updated one of mine to reflect newer communities.
/kbin server update - or how the server didn't blow up
Currently, on the main instance, people have created 40191 accounts (+214 marked as deleted). I don't know how many are active because I don't monitor it, but once again, I greet all of you here :) In recent days, the traffic on the website has been overwhelming. It's definitely too much for the basic docker-compose setup,...
Kbin Roadmap 2023
A certain stage of development has ended - a prototype was created that allowed me to verify whether such a form makes sense in the #fediverse. Until now, it was a project that I developed in my free time. Now, thanks to the great people from Nlnet, I will be able to devote much more time to it. This time, we have already...
It’s been a wild week for the open social web (dev.to)
Thank you so much for your support! 😍
I just saw an email from Buy Me a Coffee. Not just one. I went in, and I'm truly shocked. Thank you all for the support; I would like to thank each and every one of you individually someday. Honestly, I don't know what to say. The account balance is $350, which will definitely allow me to develop kbin faster or at least not...
/kbin project management costs, financing, future plans
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...
[UPDATE] 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...
/kbin - preview of upcoming changes
Hi there, in the upcoming kbin releases, I will be describing the changes along with author tags, but for now, you can check out what's happening here: https://codeberg.org/Kbin/kbin-core/activity, as well as my personal feed: https://ernest.dev...
/kbin Road to Release devlog series
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...
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...
To those genuinely interested in moderating
@Ernest has pushed an update which allows users to request ownership/moderation of abandoned magazines. Ghost/abandoned magazines were fairly prevalent after the initial wave of hype due to users either squatting magazine names or becoming inactive for other reasons. Now is your chance to get involved, if you were waiting to do...
Mbin: A kbin fork that promises to never review PRs before merging them
Somebody who was previously active on the kbin codeberg repo has left that to make a fork of kbin called mbin....
Federation Question
What mechanism governs federation with non group based instances? I set up some magazines for Running and Cycling on kbin.social, and I've noticed that there is quite a lot of activity of those hashtags from general mastodon instances....
We're back
Today, a technical server malfunction occurred. Unfortunately, it wasn't the planned update yet. The upcoming one will definitely be much shorter ;)...
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....
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.
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...
/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....
/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....
/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...
/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...