This was really a great idea! The fact that the kanji are out of context is a bit annoying, but I still love it!
Also, I have three small improvements for you to implement if you think they deserve it:
- If the user hasn’t set its public key, clicking the crabigator should open the options window. This will help users that don’t read the instructions and just start mashing the button (like I did xD) to understand why the extension isn’t working.
- Add the option of only showing kanji if it’s not yet at level Guru/Master/Enlightened/Burned. I haven’t had a problem with not having this option yet, but if/when I get to level 20 or more, I’m guessing I’ll have too many kanji in my page, most of them out of context, for me to understand anything in the page at all! I think this is useful for kanji you’re starting to learn (Apprentice/Guru), but if it replaces everything the kanji you already know perfectly will just be in the way. As an example, I looked at Moguri’s stats, and this would mean the difference between him having about 650 kanji being replaced, or more than 2800 (and even if he wanted them all, he could always disable the option or not even enable it)!
- If wanikanify is active, i.e. if I already clicked the crabigator it to activate it, or it’s automatic, clicking the crabigator should disable wanikanify for that page. In other words, if clicking the crabigator wanikanifies a page, clicking it again should de-wanikanify it. This would make it more useful for me at work where I want it to be activated by default but be able to disable it fast if I need to show a page to someone…
Again, congratulations and thanks for the extension!
P.S: The extension is not open source, is it? As a fellow programmer, maybe I could provide you with patches instead of just suggestions! xD