This is a heads up I’ll be putting WaniKani under maintenance mode on 2024-11-25T21:00:00Z→2024-11-25T23:00:00Z, up to two hours.
I am hoping the maintenance process will be done in about an hour, given the results from performing a few dry runs. I am giving myself a buffer just in case the maintenance does not go as planned. During this period the website and the public API will be inaccessible.
The WaniKani Community boards will still be up and running during the downtime period. If you wish to participate in the community boards (for example, access the private boards or post), please ensure you are logged into the boards prior to the start of the maintenance period. Else, the public parts of the board is still accessible for your reading. The boards can be accessed at https://community.wanikani.com.
I apologize for any inconvenience this may cause and thank you for your understanding.
Could you say a little about what you’re working on? Is it to add new features or get better performance or something else? I’m always eager to know what’s going on behind the scenes!
This downtime is necessary to upgrade our database software version.
There will be some under the hood changes to reviews but nothing that you would notice if you are using “vanilla” Wanikani.
For those more technically minded, I have updated the data structure of the items / subjects that power the lesson quiz and the reviews.
The update messed up something. Hitting enter after an answer doesn’t show if it is correct/incorrect, can’t view item info. Disabling all my installed scripts makes it work correctly. Nice
Appears to be the WaniKani Double-check script that is broken, makes reviews not work (maybe other stuff doesn’t work, idk)
Nonetheless, it does seem a lot of reviews-focused userscripts have broken since it happened. For me it’s the auto-commit, but several others are apparently also borked.
We cant unit test code that does not belong to us. Please reach out to the script author for your broken script as it is your shared responsibility if you use unsupported scripts.
You run a platform which is entirely dependent on 3rd party scripts. You need to start communicating prospective changes AHEAD of time, so that you give your integrator’s ample time to prepare for upcoming changes. Rather than breaking everything willy nilly and causing your community to rage.
It’s the absolute basics of running a product which integrates with 3rd party services. Have some class and professionalism.
It’s the least you can do considering you don’t bother adding any new features to the platform. Would it really be too difficult for you to release a change log with a 48 hour upgrade window rather than just break everything? Get some perspective!
I’ve been around since before any userscripts existed. So, I can and have done reviews without them. I am also a script author myself, so I really do understand where you’re coming from.
But I don’t think that this knowledge nor your frustration are helpful for this conversation.
