ernest @ ernest @kbin.social

Working on /kbin

---

Read more

Posts

122

Comments

345

Joined

2 yr. ago

Could you send me a message, as I'm quite behind, to be honest.

https://kbin.social/u/ernest/ernest

I'll try to work on it over the weekend.

I also prefer the comment box at the bottom ;)

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

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.

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.

I'm back in the game now. The issue with spam will be addressed next week.

https://kbin.social/m/kbinDevlog

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.

Zdecydowanie tak, zastanawiam się tylko czy nie zrobić domyślnego filtrowania języka na polski.

karab.in planuję ogarnąć w najbliższym czasie, w przyszłym tygodniu. Jest chyba jakiś problem z aktualizacji dockerowych zależności, których nie mogę szybko ogarnąć. Mam wszystkie backupy w razie gdyby stała się jakaś tragedia, ale w najbliższych dniach będę próbował z tym walczyć, być może nawet postawić go z najnowszym kodem co będzie dobrym testem przed kbin.social. Na pewno nie zamierzam rezygnować z tej instancji.

https://kbin.social/m/kbinDevlog

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@kbin.social @RealM @Pamasich

Are you sure you haven't changed the display mode? :)

Hey, I will try to check it this evening.

Honestly, I've been using an alternate account on Mastodon, and until recently, I wasn't aware that this was such a significant issue on other Lemmy instances until you started to clearly communicate it to me. I've temporarily taken a few additional steps to reduce the spam intensity. By the end of September, kbin.social will receive an update that should address the federation issues.

https://kbin.social/m/kbinMeta/t/465872/Spam-from-unmoderated-communities-magazines#entry-comment-2427760
https://kbin.social/m/lemmyworld@lemmy.world/t/466266/Removed-Kbin-social-communities#entry-comment-2428078

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.

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.

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?

I apologize for causing you trouble. I'm trying to resolve the situation as quickly as possible, but apart from the usual spammers, there have also been organized campaigns where, for an hour on Sunday mornings, our instance was flooded with spam from hundreds of accounts. This, of course, is causing federation issues. I've changed my priorities regarding the roadmap, and additional tools will be released soon. I will also ensure additional moderation. I will also get in touch with admins from other instances - my absence was due to personal issues I mentioned recently. Thanks for your understanding, and best regards.