It’s been two weeks since I started writing the devlog and the return to coding. I’m okay with the results. I’ve managed to establish the routines that were much needed. Finally, I could start organizing the code, which will undoubtedly yield results in the future. Sometimes, you need to take a step back to gain the right pace and avoid hitting a wall. Tomorrow morning, there might be a technical break, along with Piotr, we’ll attempt to update kbin.social - there’s a significant change in the database, and temporarily, we’ll need to halt other services. Subsequent updates will be carried out promptly, so if you encounter any new issues with the site, please mention me.
Szymon has been working on adding support for Nodeinfo 2.1
https://codeberg.org/Kbin/kbin-core/commit/ff3fe24467ce372eec1e9113b1a4e08348cb69db
@shazbot introduced KES 3.0.0, showcasing new features and stability improvements
https://kbin.social/m/enhancement/t/630864/KES-3-0-0-New-features-and-stability-improvements
You can track changes in the official repository
https://codeberg.org/Kbin/kbin-core
or on Github
https://github.com/ernestwisniewski/kbin
Instance updated. It seems like we’ve got it.
For those (like me) who are wondering… Nodeinfo is a standard seeking to improve interoperability between fediverse platforms.
Sounds like you’re laying a solid foundation – glad to hear it. Looking forward to the update. Cheers, and thanks for your hard work.
Subsequent updates will be carried out promptly, so if you encounter any new issues with the site, please mention me.
I wonder if it might be an idea to post a prominent message or banner or similar when you’re updating the site, especially for updates that may take longer than a few minutes and/or have the potential to cause longer site outages should something go wrong. That way people would know that any issues they may encounter are due to a planned outage rather than something going on.
I also wonder if it might be an idea to have a means of communicating with users that is not the kbin.social account, but rather something like a Mastodon account. That way if there’s a serious problem with kbin.social people can get updates from this alternative Fediverse identity.
So, the banner is something I’ve been thinking about for a while, but there was never enough time. Now, with more frequent updates, I’ll take care of it because it may be necessary. As for the second account, I was thinking more along the lines of a status page, something like https://status.codeberg.org/ because for some, that’s the only account on the fediverse.
