NordicRest said...I tested the script a few hours ago on Chromium (i use Ubuntu) and everything went smoothly (even with horribly slow internet). So i can't test it on Chrome.Mempo said...I have 8/1 Mbps. Not amazing, not horrible. Computer is mid-range parts from 2013, so not super slow. Script does not work, even with the API key being entered manually. I think the problem's with Tampermonkey/the script.NordicRest said... Using Tampermonkey on Chrome, it's not working. It gives me the popup that takes me to the settings page, then it doesn't do anything once it gets there. If I cancel it, it makes another popup every time I move to a page on WK saying "User not found". I think I made it work by just manually setting apiKey in the script itself, but that seems inelegant.Do you have slow internet? Technically nothing could go wrong, but while testing, sometimes i would hiccup because the script didn't load properly.
EDIT: now i think about it, it's quite possible Tampermonkey and Greasemonkey scripts are not totally interchangeable. I'll test it on Chrome today.
Since i can't recreate the problem, it's going to be hard to debug. Technically, the only problem it could be is that Tampermonkey isn't handling the Greasemonkey-specific functions very well. They emulate their functionality, but it's not 100% the same. I will soon replace these functions to enable better cross-browser compatibility.
The only thing i can recommend now is try to install it from scratch. And if you can, look at the dev console(right click anywhere>inspect element>navigate to console tab) to see if there is any output. The very first line of the script prints "started Wanikani Procrastination Annihilation BETA", so if that isn't showing up, the script has an error/got corrupted.
