/kbin contribution and information for instance owners
The search form has been fixed (if you were experiencing this issue). This time, the Docker recreate may take a bit longer. Moving forward, when making changes, I will create pull requests like everyone else and ask for your review. Sorry for the inconvenience. Soon, the first tagged release will also be available. It's time to start doing things the right way.
"#kbin:matrix.org" - It's the best place to get information or assistance regarding kbin instance administration. https://app.element.io
The kbin.social instance may experience intermittent interruptions or temporary slowdowns over the next few days. We want to test certain things that are only visible at a larger scale. This will benefit all other instances as all findings will be thoroughly described and shared.
Tomorrow, I will formally hand over the server's maintenance, so the upcoming days and weeks will focus on stabilization. Until now, the experience of kbin from an administrator's perspective could be quite frustrating.
I gotta say Ernest, your handling of this whole situation has been above and beyond. It feels strange because even within the open source world, this kind of feedback and transparency isn't common. I feel ver comfortable staying here for the foreseeable future. Thank you!
Hey @ernest, I bought you a couple of coffees from your About page link and I've invited others to do the same. But is that enough? How do you handle all this traffic? Is buymeacoffe.com your only revenue source for this project? Anyway, keep up the good work and thank you for your frequent updates and open dialogue.
Thanks for the update @ernest, I noticed that there's quite a few pull requests piling up on codeberg that requires your attention - will you be looking to merge these soon? Particularly the ones related to SQL injection seems like a high-priority: https://codeberg.org/Kbin/kbin-core/pulls
He will address the PRs, but to ensure no bad code is added, it should be reviewed + tested, especially for security related issues.
Hopefully the situation will get better very soon and ernest will have more time to review the PRs and issues and fixes will start flowing. But it's his first major open source project, which got a lot of new users, so I can't blame him for moving cautiously.
Not to spread fear or anything, but if anyone here reuses their password from elsewhere, you may want to change it everywhere. Maybe @ernest could look through logs to see if the SQL injection has actually been exploited? I assume passwords are hashed and salted, but still...
I suspect /m/FuckingFascists is probably going to get kbin defederated from everywhere, which is clearly their intent :(
eta: Ugh, there's a whole slew of magazines they're using under the pretense of being roleplay kink, horrible, and definitely going to end up causing friction IMO.