this post was submitted on 15 Jun 2023
43 points (100.0% liked)
/kbin meta
4 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Are there other maintainers charged with reviewing and merging code or just @ernest?
Next week, I also want to organize work on Codeberg.
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.