This is a third-party script/app and is not created by the WaniKani team. By using this, you understand that it can stop working at any time or be discontinued indefinitely.
This is the initial release of the Tofugu Latest user script.
This script simply adds a section to your dashboard with links to the most recent articles on Tofugu.com:
The section is added before Recent Community Topics.
Articles that you’ve already visited in your current browser will be shown in a lighter font. The rightmost column shows how old the article is in days.
HUGE thanks to Viet and the Tofugu crew for helping me to resolve a cross-origin permissions issue.
I’ve only done modest testing with this script. Please let me know in this thread if you run into any issues or have any suggestions or concerns.
You’re welcome! It makes me happy, too. I’ve got a rather ridiculous backlog of stuff on Tofugu that I want to read, but at least I won’t miss new stuff now!
That’s pretty weird. I can’t think of any obvious way that could happen unless the script is run twice somehow.
I’ll try on Firefox, but could you try temporarily disabling all other scripts except this one? I’m wondering if there is some strange interaction with another script.
Darn. I cannot replicate this problem with firefox on my mac. I’ve loaded the Double Check script, but the bug still doesn’t manifest itself. Double Check only affects review pages, not the dashboard, so it’s unlikely to be the problem anyway.
Can you point me to the actual Stroke Order script you’re using? There are multiple different stroke order scripts and I want to ensure I’m replicating your environment as closely as I can (albeit macOS rather than Windows).
All I can imagine is that the Tofugu Latest script is being executed twice on your system for some reason.
Let’s at least verify that by logging a debug message:
Open the Tampermonkey dashboard by clicking on the icon in the upper right of your browser window.
Click the “enabled” button next to every script except Tofugu Latest to turn them off.
Click on the text “Tofugu Latest” which will open the script in an editor window.
Scroll down to the very bottom and find the line containing document.querySelector(".forum-topics-list").before(tlSection);
Add a line immediately after the querySelector() call but before the closing braces that reads console.log("Exiting Tofugu Latest");
Click File then Save in the editor window.
Now either open a new tab or refresh the tab in your browser for https://www.wanikani.com (ctrl-R or click the little reload icon
Right click anywhere on the screen and select inspect. This will open the developer tools at the bottom of your screen.
Click on the “Console” button in the developer tools.
You’ll likely see several warnings and errors for various things that Firefox doesn’t like that are unrelated to this issue (pure tampermonkey and Wanikani dashboard complaints). Turn those off for now by clicking on “Errors” and “Warn” on the second row of the developer tools.
You should be left with just one white line reading “Exiting Tofugu Latest”, but I’m pretty certain you’ll see two such lines.
If your setup is indeed running the script twice for some reason as I suspect, I’m unsure what might be causing it.
Let’s verify first by following the steps above, but if the script is getting executed twice, it may be necessary to disable any other firefox extensions and reinstall tampermonkey in its entirety.
Since this script is the only thing new in your environment, it’s seems the Tofugu Latest script itself is the most likely culprit, but I can’t think of anything in such a simple script that might cause this to occur.
No worries about the delay, but now I’m really mystified.
It appears the script is only being executed one time, but the Tofugu Latest section is being added to the DOM twice.
I added the same Stroke Order script, but when I try it in a fresh install of Firefox with just tampermonkey and those three scripts installed, I only see the section inserted once.
Ordinarily, I’d assume my script is at fault (both on general principles and because it was the last that changed in your environment ). Because I’m unable to reproduce it, though, and because nobody else has reported this problem, I think it must be something in your environment that is causing this.
I can’t even hazard a guess as to what it might be, though. Let me think for a bit.
Actually: could you click on Errors and Warnings in the inspector to display them again and send me the entire output? You’re getting many more errors and warnings than I am in a fresh Firefox install. I’m hoping there’s a hint in there.
You can drag the inspector window up to take up more real-estate.
You don’t have two installations in your script handler?
You don’t have two installations in two different script handlers?
You don’t accidentally have it installed directly in the browser (check extensions)
Try turning off any ad-blockers or other privacy-oriented extensions
Insert some console logging to figure out if some code is actually being run twice (presumably Rrwrex could provide this for you so you could just copy/paste the whole script)