I have no idea how the detector processes API information. You’ll need to ask the author.
It’s be really interesting to know how many people make this mistake, and for how LONG
I’m at LEVEL 17, I leared it a year ago and STILL it’s a leech!
There is actually a pretty simple rule that I didn’t realize until several weeks ago myself: if the vocab has 業 in it, then it’s always industry. Otherwise it’s construction.
That would work, except I also confuse it with 作業, “work, operation, and manufacturing” (but not industry) in the sense of “manufacturing” being like “construction” and 工作 also meaning “handicraft”
So I have the same problem but in the exact opposite way you do?
Ah yes, I forgot about 作業. That one trips me up as well.
Thank you for this!!
Guh. Mine is infinitely loading. Does that mean I just have WAAAAY too many leeches and I’ve broken it, or is something else going on?
Seems like it only works with API 1, while API 2 makes it load into eternity.
@redglare you are my hero.
Now, it’s time to go cry over my leech list.
spent quite a bit of time squashing leeches…now before they get out of control again, I thought I’d use the script, but it doesn’t seem to be working…just me or did something break with an update???
Just tried this… it froze on a blank screen if I used the new v2 API key, but it still seems to work fine with the old v1 API key.
What does the score mean?
It is the largest amount of mistakes for a review item (either reading or meaning), divided by your current streak of getting it right to the power of 1.5.
If the score is 1 or higher, the item is a leech.
Will this be updated to accept the new API before the September 2020 deadline?
It unfortunately looks like the creator hasn’t been back for quite some time.
That’s actually a very nice improvement. Good job, and thank you for your work.
Thanks for your kind words. I am glad that you are happy with the script.
not working anymore?
I got here from another thread indicating how to deal with leeches