Dope! Thanks for the clarification.
Is there a way to insert reviews for prior days? My heatmap doesnât have anything for yesterday despite me doing a few review sessions on the Flaming Durtles app.
Yes, you just need the correct timestamp (Unix epoch, first value). To convert a date to timestamp you can use Date.parse()
in the console. For example Date.parse("apr 25 2023")
Note, however, that the Heatmap will no longer pick up on any reviews done in Flaming Durtles
Is that just flaming durtles or other 3rd party apps as well?
I think itâs any other browser or device if I understand correctly. Itâs only stored in your local browserâs cache, so if you switch to a different browser or app, or even just clear your cache youâll lose all of it.
Thanks
bye bye review records
We no longer have access to any review data from the API, so there is no way for the Heatmap to track reviews done anywhere but on the device where it is installed
I have heatmap installed on multiple devices. Will it still track those on my account? Or just show the ones on that device?
I guess it doesnât matter much anymore, but I am curious about the answer.
Just the device where you did the reviews
Hello! I use flaming durtles on mobile and just did reviews on my laptop where I have the heatmap installed. It did NOT track my reviews. Is there a way to fix this? Is anyone else having this issue?
With the changes mentioned above and in multiple other threads, itâs currently not possible for scripts to get review data from the Wanikani servers. Kumirei did a great job at updating the heatmap super fast with a temporary workaround (make sure you have the script updated), but it canât sync across devices. Hopefully Wanikani will sort something out to get this back up and working again, but until then we just have to manage with what weâve got!
sigh; never really be frustrated with WK before. Feels like they keep changing things without thinking about what customers want. I mean- this will def reduce their hosting costs, and Iâm okay with that if itâs like, âthat or we go bankrupt an lose WK all togetherâ but itâs unclear why. Like for the reasons they stated, an API throttle is the way to goâŠ
rip to my study streak o7
I alternate offices on different work days so i do WK on like 4 different machines (including my phone). A strange edge case but itâs still a bummer that i will no longer be able to maintain a streak
Yes Iâm also having this issue it didnât track any of the reviews I did on my laptop at work and now it wonât even track reviews Iâm doing on my main laptop - no reviews are being tracked Iâm not sure what to do
Make sure the script is up to date for it to track locally
They hired at least 2 people if not more in the last year, so I hope that theyâre not going bankrupt.
This isnât a problem that can be solved by API throttling, or rate limiting. Itâs a fundamental problem with the database query itself. API rate limiting applies at the user level. If you have 100,000 users all hitting the home page, all using a userscript that makes a single, database intensive query, which do you throttle?
I totally love my heatmap, and hope that WK devs find a solution, but this is an overly simplistic take.
Yeah I read the post by dev. Sounds like they need a DBA and migration. But also to answer your question: the last ones. Use a LB with weighted max cons. Anything can tip over, infra should expect that.
thank you for your swift work, kumi i did ~150 reviews and then noticed my heatmap was still null and freaked out lol
i updated to the newest version and it seems to be working again, but itâs also counting lessons in the review count - not sure if thatâs a major issue or something thatâs already slated to be straightened out later
Ah! Good observation. Iâll get that fixed tomorrow