/kbin meta

16 readers

2 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

261

/kbin contribution and information for instance owners (kbin.social)

submitted 1 year ago by ernest@kbin.social to c/kbinMeta@kbin.social

51 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] in2erval@kbin.social 14 points 1 year ago (1 children)

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

[–] GauthierPLM@kbin.social 10 points 1 year ago (2 children)

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.

[–] knoland@kbin.social 2 points 1 year ago (1 children)

Are there other maintainers charged with reviewing and merging code or just @ernest?

[–] ernest@kbin.social 3 points 1 year ago

Next week, I also want to organize work on Codeberg.

[–] clb92@kbin.social 2 points 1 year ago (1 children)

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...

[–] ernest@kbin.social 2 points 1 year ago

@clb92 From next week, significant changes in terms of security will occur. I will keep that in mind.