That part is clear to me so far; although I would rather lean towards rewriting the image URLs to be fully qualified so one can actually see the images (if they are not too large, that is). I havenāt yet looked into it, will experiment over the weekend, I guess.
I was more wondering about how to publish the new version on Greasyfork under the same script name? (If thatās possible at all)
Because I assume that the script ābelongs to youā on Greasyfork so that not any arbitrary person can replace it?
You can create a new script with the same name, because every script gets a different prefix number, which is the ā35970ā in polvās link above. People will have to manually install from your versionās url the first time, but after that it should update automatically from the new url (if the user has updates enabled, of course).
As a first step, I have released version 0.6 of the WaniKani External Definition script today. As the original post for the script is meanwhile closed, I will create a new one.
Iāve been getting this fairly constantly. So itās caused by add-onās making too many requests?
I have a few add-ons that arenāt essential Iāll try turning those off.
I have not encountered this from any other script other than the old External Definition script, but yes, thatās usually the root cause.
You may want to look at the browser console to get an idea of what might trigger these requests.