Does a technical break mean a downtime for system maintenance? Will there be any fixes or enhancements?
Thanks for all your hard work, Ernest.
this post was submitted on 02 Oct 2023
8 points (100.0% liked)
/kbin meta
1 readers
4 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
Ernest has previously said that this will be an upgrade to address several issues, such as those related to federation, spam and lack of moderation tools.
Do we know if API implementation will be part of it yet?
API is part of the latest develop branch. And live at: https://kbin.melroy.org (Docs: https://kbin.melroy.org/api/docs).
https://codeberg.org/Kbin/kbin-core/activity/monthly#merged-pull-requests
API stuff is listed in the 'merged pull requests' section (quite a few times), so unless I'm mis-interpreting what that means, I think the API should be going live as long as this downtime is for the updating of the instance!
This will help a LOT with people seeing /kbin as an option ... the mobile webpage is pretty fantastic, but I'm really looking forward to switching to the Artemis App as my daily driver.
I don't recall Ernest explicitly saying so, but the API is live on the artemis.camp instance, so hopefully it's in a state where it can be implemented as part of the core kbin code base. Perhaps the kbin codeberg can shed further light on this question.
edit: see tjhart85's answer.
API is part of the kbin code base (on latest develop branch). For example https://kbin.melroy.org also have API enabled. But kbin.social is still not upgraded until this day.
I’m excited about the upcoming update that will roll out the API for kbin.social. Is there any updated information that can be shared about the timing of the roll-out?
So, I made a new thread asking about the status and ernest responded to it.
It seems there's been some unexpected irl issues that have prevented ernest from properly working on the update.
However, I'm almost ready to continue on this journey, so you can expect that in the near future, there will be a banner with information and the update date of the instance and release. After that, we will work on avoiding such longer development downtimes in case of my absence.
Any chance that the broken inbox bug is among the things getting fixed by the suite of changes?
Does it have an issue on codeberg?
If not, I recommend bringing it up there. If you only bring it up here, you rely on ernest or another contributor writing it down and remembering it, which probably isn't too reliable. Better to put it on the issue tracker.
Thanks for the heads up, good luck!
This post has no comments visible for me (though it should have 9 as of now). I do not see it in the kbinMeta at all. I also sometimes get 500 errors in kbinMeta, particularly when sorting by new. I only found this post by clicking on Ernest's name to see activity. Any ideas (though I'm not sure if I will see any responses, heh). Not seeing anything but 200s in the network tab of inspector.
You probably won't see this, but I've sent you a private message. Hopefully that one arrives.
I assume it's the blocking bug, which is getting fixed this update I think.