ernest

ernest, 6 months ago

1. kbin has a tag view - you can click on it, and it will display content from the fediverse, merged with Mastodon posts and other microblogs. The type of content found there depends on the instance and any relay connections. Personally, I've never been a fan of the chaos in large Mastodon instances.

https://kbin.social/tag/NewYork
https://kbin.social/tag/silenthill

2. It's something I'll be working on in the future. I'm focused on integrations with various platforms and convenient browsing of multimedia content coming from them. Currently, it's done provisionally and is not the final solution.

I won't comment on the rest because I've always hated the Twitter format. But I know that there are many people who find it appealing. Mastodon didn't suit me either, despite several attempts to use it.

ernest, 6 months ago

Yep, another way is to choose abandoned from the list of magazines, soon it will be more sensibly sorted ;)

https://kbin.social/magazines/abandoned

ernest, 6 months ago

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.

ernest, 6 months ago

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.

ernest, 6 months ago

I assure you that I didn't intentionally push incorrect code into the repository. These were my first lines of code in a really long time. I simply got involved in other things that I wanted to finish first, and I noticed the edge case in the meantime, but it wasn't a priority. I saw that you were syncing and I was hoping to benefit a bit from it once you fixed it. I didn't expect the review to happen so quickly. By the way, I was genuinely curious about how this project management method works because, you know, I've always avoided such an approach. Merloy, you know how much I owe you, and I appreciate what you've done for the project, as well as the other Mbin contributors. Our overall visions haven't always been the same, and I think it's great that kbin has been forked. You see for yourself how my work looks until the release - there are many things I'll be refining over time. That's why I've put a hold on all other PRs, and now I want to focus on this.

ernest, 6 months ago

Yep, in Polish we call it skrót myślowy.

ernest, 6 months ago

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.

ernest, 6 months ago

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.

ernest, 5 months ago

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!

ernest, 6 months ago

I've already discussed some of the reasons on Matrix, but today, I'll try to briefly explain what's going on here. Due to the increasing popularity of kbin, infrastructure changes, the cost of maintaining instances, and development-related priorities, I wasn't able to deliver the milestones on time, which are crucial for project funding (even though I'm really close to achieving that). I wasn't prepared for this and didn't anticipate such a delay in terms of the savings I allocated for all of this. The servers are still being maintained with the donations that came through buymycoffe, but there are additional costs like living expenses and other obligations. So, I had to take up temporary work to ensure the continued development of the project.

This year has also brought many other unexpected personal problems, as I mentioned earlier. Now, another one has been added to that list – I had to end my marriage and a fifteen-year-long relationship. While it's not a sudden decision, it's never easy, but it has turned out to be more challenging than I anticipated. Not just for me, and this time, I want to dedicate as much time as necessary to conclude the matter properly. I had to learn how to do many things from scratch, set up a new work environment, establish daily routines, and more.

So, why all these deadlines and promises?
It was probably the only way for me to accomplish at least the absolute minimum. There's a lot of my own code waiting for review on my local branches, but it's genuinely hard for me to push myself to it for now. The infrastructure also requires fine-tuning, and Piotr is helping me with that. And the days are passing by very quickly.

However, I'm almost ready to continue on this journey, so you can expect that in the near future, there will be a banner with information and the update date of the instance and release. After that, we will work on avoiding such longer development downtimes in case of my absence.

@a @RealM @Pamasich

ernest, 7 months ago

Hey, I will try to check it this evening.

ernest, 7 months ago

This week, I've been dealing with cleaning up instances from spam. Several hundred accounts were removed, along with several thousand posts - these were massive operations. It's possible that due to the volume of requests, other federated instances hit rate limits. I see that some of them are still in the queue with a "fail" status. I will gradually resend them after some time. Along with the update of kbin.social and the first release of kbin, new modeartion options will be available, including spam blocking (such as global blocking domains), a new reporting panel for moderators, and improved federation between instances. I will also address abandoned instances and ensure that each one has at least a few active moderators. I know how urgent this issue is, and it's my top priority. I just need a bit more time as Piotr and I are preparing for the update.

ernest, 7 months ago

Of course, I'm taking action, and on kbin.social, those posts have been removed, which you can verify. However, for some reason, it doesn't always federate with Lemmy. It used to work before, but practically after every Lemmy update, there's something to fix in the code, or it could be related to API limits because some requests receive a "fail" status in the queues. The same applies to spam from Lemmy instances - I had to manually clean up hundreds of posts from other instances because they didn't always send AP requests, which I verified in the logs.

Do you seriously believe that it's a matter of individual accounts, and banning a user solves the problem?

ernest, 7 months ago

By the end of September, kbin.social will receive an update that will address some of the issues. For now, I'm banning spam accounts, and registration is disabled. Additionally, external links are marked as "nofollow." I just want to emphasize that this is not solely a kbin issue - I had to manually remove spam posts from Lemmy instances as well because moderation didn't federate, which doesn't happen with, for example, Mastodon.

For now, the admin of your instance can choose to defederate or remove communities, as the admin of lemmy.world did. Once I've dealt with the update, I will reach out to other admins and discuss the possibility of restoring valuable posts.

ernest, 7 months ago

The problem is that at this scale and with this infrastructure, hotfixes are no longer as straightforward as they used to be - when I could solve these kinds of issues in a matter of hours.

ernest, 8 months ago

Hi there, I'm currently working on solving the problem. There will be significant changes this month. I know it's taking longer than I initially announced, but this will be a really solid release. The contributors have made an incredible work and I didn't want to miss anything.
https://kbin.social/m/kbinMeta/t/381108/Lots-of-new-spam#entry-comment-2209332

ernest, 8 months ago

The mechanism itself is already ready, but there are so many other changes that the next server update won't be that easy. Additionally, I had to solve several private issues that effectively distracted me from work, sorry for that. At the beginning of September, everything will start to stabilize, and that's also when all the changes will be on kbin.social.

ernest, 8 months ago

This month, the largest update is planned. It's taking a long time because part of the team is returning from vacation, hence the delays. I hope that the update will resolve some of the most pressing issues. I'm also trying to remove spam systematically, but currently, the code is my priority. After implementing the new version, I will seriously address the community.

If there's anything urgent, currently contacting through the form is the quickest option. Cheers!

ernest, 10 months ago

I have an eye on this issue. I can't reproduce it myself, but I will have a few additional devices for testing this week.

ernest, 10 months ago

Wow ;) I'm incredibly lucky to have come across people like you. The authors of those posts are actually right - managing /kbin is a significant challenge nowadays. It requires extensive knowledge and experience to keep it under control. But also I've never hidden that fact - the information about it is placed at the very top of the repository's readme ;) However, as I mentioned, a lot is changing very quickly https://kbin.social/m/RedditMigration/t/122333/Fediverse-won-t-replace-Reddit-as-long-as-Lemmy-is-the#entry-comment-478779. And we're all working hard on it, to improve and automate as many things as possible. Thanks to all of you, I believe I can face it head-on, and together we can create a better place. Better internet. Not just this instance, but cooperation between platforms is the key here.

Unfortunately, there are delays occurring again - I've decided that smooth website operation will be the priority this time. There are approximately 450k tasks waiting in the queue, and everything will be handled, but it will take some time. Today, we're also conducting final tests of the new infrastructure. It's taking a while because we're documenting templates that can later be used by others to create their own instances. I hope these are the last issues we have to endure ;)

Thanks for everything.

ernest, 10 months ago

It's possible that this is a consequence of the latest Lemmy update, in which a lot has changed. I have noted that kbin has some issues with request signature in communication with certain instances. I will try to check it tomorrow first thing in the morning.

ernest, 10 months ago

I just need a little more time. There will likely be a technical break announced tomorrow or the day after tomorrow. Along with the migration to new servers, we will be introducing new moderation tools that I am currently working on and testing (I had it planned for a bit later in my roadmap). Then, I will address your reports and handle them very seriously. I try my best to delete sensitive content, but with the current workload and ongoing relocation, it takes a lot of time. I am being extra cautious now. The regulations are quite general, and I would like to refine them together with you and do everything properly. For now, please make use of the option to block the magazine/author.

ernest, 10 months ago

All the things you mentioned are in the roadmap. However, we can either do it quickly and potentially encounter issues in a few weeks or months, or take a bit more time for a more thorough approach. I've decided to move away from playful prototyping. From now on, every change will be tested before it's approved for kbin.social - it's no longer just my code (https://lab2.kbin.pub/). I'd like to close this thread for you... but can we just agree not to respond in it anymore? ;p

ernest, 10 months ago

In such important tasks, I would like to engage in community-driven development. When I start planning these tasks, I will come to you with my whiteboard and sketch out the individual stages. Together, we will look for the advantages and disadvantages of such a solution, the weak and strong points. This is to jointly make a decision on whether the change makes sense on kbin.social but also in the perspective of the entire federation. It can be a great fun ;)

ernest, 10 months ago

I'll try to take care of it today and potentially clean up the activity. For now, I've limited the traffic from that instance. I'm currently working on additional tools for moderators.

ernest, 10 months ago

I will definitely check it out! Thanks

ernest, 10 months ago

It seems to me that she did it very gently ;)

ernest, 10 months ago

mobile / desktop?

ernest, 10 months ago

It should be fixed. If you could note it down and let me know, please :)

ernest, 10 months ago

Try @curiosityLynx@kglitch.social
I will add the issue, thanks.