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):
https://codeberg.org/Kbin/kbin-core/src/branch/develop/src/Repository/Criteria.php
https://gitlab.com/postmill/Postmill/-/blob/1e98b99bc4a20b396f2fa4089bdb1a308b7e18fd/src/SubmissionFinder/Criteria.php
https://gitlab.com/postmill/Postmill/-/blob/a9704316c1c78f15ca12c2dc5ad477f4ac9f530e/src/Entity/Submission.php#L21-57
Since then, over 230 pull requests have been accepted. I had a branch where I was working on this, but a lot of code has changed in the meantime - among other things, ex the markdown implementation has been rewritten and, in fact, some of it is now outdated. Many files will still change and be rewritten before the release.
Before the first release, it will be done properly, and I will probably seek help and consultation from the right people https://codeberg.org/Kbin/kbin-core/pulls/937. Currently, in the project's readme, I've clearly indicated that kbin is inspired by Postmill. Unfortunately, recently I've been overwhelmed by some personal matters, which caused me to neglect certain things. Now I'm doing everything to bring kbin to the appropriate state.
Hey, this mechanism is already finished. The problem is that I planned the next update after the release of the first /kbin tagged version. There's still about a week left for that because there are really a lot of changes that I'm still testing. I'll try to speed up this process and quickly create some external procedure.
@Arotrios The magazines have been cleaned up and I've deleted the associated accounts. If this happens again, I'll apply a temporary fix. And if the campaigns cease, I'll work on a more comprehensive solution. Thanks for reaching out.
Currently, all I need is a bit more time ;) I'm gradually granting additional permissions and sharing responsibility with contributors. We still need to establish a some policy. If it speeds up work on /kbin, I'm okay with that. They are great and experienced developers. However, it's important to remember that they all do this in their free time.
Hey, that's the plan. After the first release, the status update will probably be every two weeks. Currently, I'm struggling with the preparation of the release, it's taking up a lot of my time because I have many changes to integrate. On top of that, I've been going through a tough period in my personal life, but I've overcome it and starting from Monday, I'll be giving it my 100%. Contributors continue to be active, and their assistance is invaluable to me. To make matters worse, I have to deal with waves of spam that have recently surfaced on kbin.social, which you've probably noticed. Stay tuned ;)
@20gramsWrench Almost, all I need is a shower and a gentle breeze outside ;)
@EnglishMobster This week, I will take a closer look at the topic, and additional options for the blocklist may be required. To be honest, I cannot guarantee that it will happen right away, but the improvements will definitely be gradually introduced. The priority, however, remains the stable functioning of the website and data security due to the significant changes prepared by contributors. I don't want to do anything faster than necessary, but I realize how important what you're writing about is.
Ok, so in the next few days, I'll be testing some things. It might be a bit worse for a while, but it will definitely speed up the problem-solving process. I'll be grateful for any feedback. I'm unable to reproduce it in local/testing environments, so it might be an issue with the cluster.
At the moment, I am the only admin on kbin.social - mainly because /kbin doesn't have a tested global administration by multiple admins/mods ;) It's something I'm currently working on. Sometimes, there are so many notifications and messages that responding would physically take up entire days. I can't reply to everything immediately, but I try to do it systematically. However, the best way to get in touch is through Matrix spaces. I feel that every problem will be properly addressed there, which is why I can allow myself to work calmly besides managing all of this ;) Another more reliable method is a contact form.
Hey, on Monday, the system for transferring magazines and submissions to moderators will be ready. I am currently working on it, which is why I need a moment of focus and isolation ;)
I'm still working on it because it doesn't happen to everyone, which is why it's not that simple. Before the release, the problem should already be resolved, so please have a little more patience :)
https://kbin.social/m/kbinMeta/p/1002621/Hi-in-this-and-probably-the-next-week-I-will
Currently, kbin has no delays in the queues. This may be due to not all streams being sent to us or an error in the federation. Over the next few weeks, this process will be improved.
The federation between the Mastodon instances I am using for testing is either immediate or takes a maximum of a few seconds. However, other instances may experience their own delays.
Hey, next week. There is still the matter of changing one js library, and we need to determine the minimum percentage of progress at which translations should be released.
Today, the clearing of some sessions was intentional. But I have heard about it before. Are you sure that you logged in with the "Remember me" option checked?
I didn't manage to do it in time, but it will be implemented soon.