Lately, I've implemented some restrictions that should eliminate or significantly reduce the issue of outgoing spam from kbin.social. I apologize for any inconvenience and really appreciate your patience. I'm confident that both the Lemmy and kbin tools will be adjusted over time, and until then, we all need to take a deep breath and overlook certain things. Good luck with that.
You need to inform your instance that such a community exists. Usually, it's enough to type the URL https://kbin.social/m/OriginalDocuments into the search bar while logged in on Reddthat.
In the latest thing with Reddit's /kbin, it was still in the early prototype phase (and remains so to this day). Prior to this, practically only I and a few friends were using it. It wasn't ready to handle the sudden creation of dozens of instances or accommodate thousands of users. Additionally, real-world issues emerged that demanded my immediate attention. I made the decision to take a step back instead of getting caught up in a race, opting to build solid foundations, which is exactly what I'm doing now. In my opinion, this will be better for the project and potential contributors, ensuring that their work will be utilized to the best possible extent.
Actually a lot is changing in /kbin, and this recent period has brought the most changes in months. Slowly we are coming back to life, and this time I will be better prepared.
Hi @maegul, actually you can track people you follow in the /sub feed at https://kbin.social/sub/microblog. It might seem a bit chaotic, with what looks like random posts, but in reality, each of them has a response from someone you follow (or an boost post/comment). But you're right, it's not perfect yet, and the presentation will be improved in the coming weeks/months to highlight specific comments from people you follow on front. I'll probably write about it in my devlog soon ;)
Not really. The official repository (with issue management) is located on Codeberg. GitHub serves as a mirror in case of any issues with the primary service.
This feature stopped working for some reason during the development of these software. In the coming weeks, I'll be working intensively to improve communication in the fediverse, including moderation.
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.
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.
At the end of the day, I wanted to thank you for that reminder. Sometimes I really need it. For now, these two PRs will have to suffice. I'm sure I modeled them after Postmill. I can promise I'll get back to this and do it right.
It took me from 4 to 6 minutes, I can't determine exactly. I think this is about more than just copying and committing a file - one needs to label specific files or sections of the code. I'm not sure how exactly this should look, so I'm waiting for a consultation.
Most of the indicated code is no longer part of kbin (unlike Pixelfed's code, to be fair). You can see the similarities in the links provided above. However, I need to thoroughly analyze everything once again to make sure nothing slipped past me and there isn't more of it. There might be a tool that could facilitate this. In any case, it's not my intention to hide the original source, even if major changes have been made. I'd gladly leave information about what the code was based on. I have no problem with that, the only enemy is time.
I think several factors contributed to this. First, I prepared the licensing tag, but when the time came to merge the branch - that code simply no longer existed. As you can see, the remaining files are what I call inspiration - it's not copied code but more of an overall concept, quite common in these types of applications (however, I'm not saying that there shouldn't be a tag). Another factor is that sometimes you have to choose what to focus on first - eliminate and remove thousands of spambots, fix activitypub communication after updates from other software so as not to crash your server and others, secure the instance from sensitive content, deal with all the formalities related to the legal situation, working on moteration tools, handle pull requests from people who dedicate their private time to it and many more. Additional, I still need to make sure I can pay my own bills, and there's personal life.
And yes, two months is a long time, but for me, it was just a flash this time. A swift reality check occurred because the first release was supposed to come out over a month ago. I'm doing this the best I can, and without the help of contributors, none of this would have been possible. Due to the situation, I have to prioritize certain tasks. This is still marked as high priority, but it's waiting its turn. Nevertheless, I have the opportunity, I decided to seek external help to do it the right way before releasing the first version. I realized that it only seems like a simple task on the surface. I want close the matter once and for all. All of this also pertains to the licensing tags of Pixelfed, btw.
As I said, the markdown implementation that received the main thing has been rewritten by contributors. I need to consult on how it should look in such a case. Now the indicated similarities are between these files (these files will also be changed soon, before release):
Lately, I've implemented some restrictions that should eliminate or significantly reduce the issue of outgoing spam from kbin.social. I apologize for any inconvenience and really appreciate your patience. I'm confident that both the Lemmy and kbin tools will be adjusted over time, and until then, we all need to take a deep breath and overlook certain things. Good luck with that.