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.
Stay tuned
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…
@clb92 From next week, significant changes in terms of security will occur. I will keep that in mind.
Are there other maintainers charged with reviewing and merging code or just @ernest?
Next week, I also want to organize work on Codeberg.