While I have been trying it a few months ago, UI as of now is mostly OK…
SVG are broken, but are alright on hover.
Also, I get rate-limited when using it.
Yeah I don’t think there’s a lot that can be done about the rate limit. It’s not an issue of not working, it’s that there isn’t a way to bulk resurrect/retire with the API. From looking at the code it seems like it tries to make the requests in batches of at most 5 but they’ll still be done one at a time. See comment from rfindley below:
Separate issue I noticed while looking at it, it does not fetch kana vocabulary. Probably no one’s noticed because they’ll rarely feel the need to reset those.
I’m almost positive that it does not do anything related to the rate limit. I checked the code for any type of waiting, but there’s nothing there.
That being said, I modified the script to read the rate limit. Wildly, the rate limit information doesn’t get published until you’re already rate limited (e.g. it tells you how many requests you have left before you’re rate limited, which will always be 0).
I implemented a log in the console to tell you that you’ve been rate limited and how long you need to wait for it to continue. There’s probably a better way to do it but that’s what we have for now.
I would love for these changes to be pulled into this script if you’re at all inclined @rfindley
Edit: I’m currently working on changing the state of a lot of items myself. Unfortunately you’re limited to 120 requests per minute, which means say 5k items will take 40m at best (and actually longer because it seems there are other requests that will be happening concurrently, taking up your limit)
Edit 2: I previously made a mistaken statement about when the rate limit was added.