If it were little enough data, you wouldn’t even need to spread it across all items. Just pick ONE item (the same one every time) and stuff it all in there. At least a handful of global-like variables. I wonder if you can add user notes on hidden/discontinued items that are still in the DB?
Finally, a use case for 里心
Waiting for tofugu-scott to jump in with “please do not do this” 
One item is certainly not enough for all reviews. My latest heatmap export is almost a megabyte in size, which basically covers levels 30 to 51 at a reasonably fast pace. You could come up with a more compact format (some type of base64 encoded zipfile) but it wouldn’t reliably fit in one item.
No, yeah for that you’d need each item to carry its own weight, but for a simple streak tracker, one might be enough.
New update seems to have broken Heatmap
It still works just fine for me, strange!
It doesn’t work for me either, although none of the userscripts I have installed work anymore since the update.
Have you tried using the settings? It’s broken in there.
For me, the heatmap simply does not show up. I’m using Chrome.
Firefox here, and the heatmap also does not show up for me at all. I tried out every position, and it turns out that ONLY the “below SRS” position shows Heatmap. None of the others work at all (mine was set to ‘below panels’), which is an interesting behavior to have happen.
Good catch, Mine was set to top so that is why its still working for some users
I believe this is all that’s needed to fix the positioning, Kumi:
let position = [
['.dashboard__content', 'beforebegin'],
['.dashboard__srs-progress', 'beforebegin'],
['.srs-progress', 'afterend'],
['.dashboard__item-lists', 'afterend'],
['.dashboard__content', 'afterend'],
][settings.general.position]
Some of the names had me guessing where it was meant to go however, since I never used those options.
Edit: oh and I noticed the settings icon doesn’t get cursor: pointer; because it’s in a <button> instead of an <a>. So might want to add that.
I think the update for Firefox might have been slightly delayed somehow? Most scripts I use are now broken in one way or another, but just after the announcement, everything still worked like normal!
I have merged fixes from @LupoMikti. The Heatmap should be working again, I think
I edited the heatmap’s review forecast colour step numbers a bit, clicked apply and then save, and now it’s failing to load with these errors. Any ideas?
Hmm, this isn’t part of what I changed so maybe it’s a new bug or been there for a while with no one noticing. I’ll take a look at it and see if I can reproduce it.
I’m already looking at it
Ah, okay then!
Should be fixed in 3.1.10. You will need to set your intervals again, sadly.
