Hi there, in the upcoming kbin releases, I will be describing the changes along with author tags, but for now, you can check out what’s happening here: https://codeberg.org/Kbin/kbin-core/activity, as well as my personal feed: https://ernest.dev
Today, two test instances will be created where we will be looking for bugs for some time, and then the changes will be rolled out to kbin.social and hopefully other instances as well :)
I want to accept as many pull requests as possible, currently, there are still 50 open ones. I’m also following your posts and adding new things to the to-do list.
Have a nice day!
Will the test instances be publicly available?
That would be greatly appreciated by us over at /m/kbinStyles so that it’s possible to see that everything still works before the new version goes live.
Obviously not exactly high priority, but I thought it was worth asking anyway.
Sure thing, I will manually approve accounts from time to time. These scripts are mind blowing ;)
https://lab2.kbin.pub/
https://lab3.kbin.pub/
Was lab1 destroyed by a zombie outbreak?
@ernest heads up, looks like lab3 is down atm
Yep, I need a few hours to finish it. The sun would shine too brightly on my monitor right now ;)
Some of the userscripts could, longer-term, be converted into server-side Web UI features; I think that that’d make them available to a wider audience, since they become available to all browsers without user effort then. However, for any that don’t, I also imagine that it’d also be possible to set up some sort of automated regression testing using Selenium or something like that that warns if it looks like they aren’t working in a new version. That’d take load off human userscript maintainers if the userscripts are going to be around for the long haul, and it’d give a heads-up earlier, potentially as soon as the breaking commit goes into git.