What makes you think the issue is fundamental?
1 Like
Correct. I know that at least @rfindley’s Double-Check, @Kumirei’s Reorder Omega, and my Item Info Injector library [1] use WaniKani.wanikani_compatibility_mode to determine whether to expect the old or the new version. Depending on how long it will take until you remove the last remnants of compatibility mode, would it be possible to always set WaniKani.wanikani_compatibility_mode to false? I think that would avoid many problems.
I don’t think that this will be a problem, because all scripts that I know of use something like
if (!WaniKani.wanikani_compatibility_mode)
and when wanikani_compatibility_mode is gone it still evaluates to false.
which I’m using to maintain Mnemonic Artwork, Advanced Context Sentence 2, Lesson User Synonyms 3, Item Filter, Old Mnemonics, Kanji Damage 2, Rendaku Information, Keisei, Niai, Pitch Info, and Homophone Explorer, and which is also used by the authors of Stroke Order, Anime Context Sentences, and Kanji Search Notes ↩︎
1 Like
For Omega I think I will just strip out compatibility support later today
2 Likes
I often have typos as I try to get reviews done quickly. Why can’t there be some sort of native way to correct errors?
Edit: Many scripts offer functions that could be seen as subjectively bad, but the inability to correct typos is so frustrating, and it feels like a huge amount of functionality has been lost.
1 Like
Historically, our concern has always been that people would abuse the ability to change answers beyond just typos… and there are plenty of confessions in the forums from people who have fallen into that trap (via scripts), negatively affecting their learning and in some cases resulting in a large backlog leeches.
But just so you know, we do still think a lot about this and other issues. A lot of decisions have deeper implications than the obvious ones, so we sometimes have to be thoughtful and thorough about making changes.
1 Like
Many thoughts, but I think Mistake Delay is ok for sure, at least to optionally Show Info.
Kana should be strict, yet Okurigana matcher can be optional, to prevent fat-fingered wrong.
I am in the camp that meanings in English don’t matter much, but it also depends on stages of learning. It can be hard to adapt to learner differences, from clumsy to outright misdoing; and one can be on both sides of the spectrum at the same time. The current implementation of string distance, and hidden warning lists and blocklists, are quite messy in my eyes.
So, I think it should be an option, although might not be the default one; just like native re-ordering, which gets implemented at last…
1 Like
Good Morning
I have removed Script Compatibility Mode completely from WaniKani this morning. Hopefully any scripts that have yet to be updated will now default to false if they had any reliance on the wanikani_compatibility_mode variable which is now no longer on the window.WaniKani object.
If you see any posts instructing you to turn off Script Compatibility Mode these can now be ignored as it is effectively turned off for everyone. I hope this helps.
3 Likes