Fair enough. I did notice it when the big update was carried out. I think if a someone else involved with Kumi’s repo sees my comment there will be enough there to find out what can be optimised at review entry time to mitigate the lag if they choose to. Thanks again!
Ehe, well recently the only people involved have been myself and @Inserio, kind of sad to say but even with scripts here all having open source licenses there is very little contribution to them from outside the primary maintainers (and a lot of them don’t even link repos).
I’ll keep looking into it. I’m not sure what about the updates would cause this kind of problem to crop up rather than it having been present all the time though.
Understood, I’ve found the Github repo if I get a chance myself this week I’ll see if I can put in a PR that optimises things a bit.
2 Likes
For anyone else who sees this before a fix is introduced you can prevent the slowdown issues for now by either skipping the homepage and going straight to the reviews page or opening the reviews page from the home page in a new tab (not just clicking through to it in the same window.)
cc: @raesh
1 Like
wow! that easy, huh? 
thanks a bunch man, you found out by chance or what?
By chance/spent a couple of hours digging through the code and working out what had changed about the new site that could be causing an issue with the extension that wasn’t happening previously - what’s the difference?
The devs know the cause now though so we might see a fix soon if we’re lucky anyway.
couple hours, thats impressive. i dont know a thing about coding, so i`m really glad you did what you did. kudos!
I’m thinking about to change my browser (currently using Opera GX and want to go back to firefox).
Is there a way for technical dummies like me to transport my heatmap-data to another browser, so it can continue counting instead of starting by zero again? 
The current process is described here:
It’s not as technical as you think as it’s mostly just copy pasting things (or typing them out as written).
I’m still working on making an actual interface for doing this so you don’t have to use the console at all. No ETA on that.
2 Likes
Thank you for linking the process!
I managed to transfer my heatmap successfully. 
(And to hide my stupidity I edited this post, lol.)
Hello! I just installed Heatmap on my computer at one location the other day and it works great…but I’m trying to install it on a different machine now and it says it’s installing but it never comes up on my dashboard. Everything is the same browser-wise both are Firefox. I think one computer has a newer OS than the other–would that make a difference?
The Heatmap only shows up once you have reviews in the cache. Since you have it on two machines, it would not show up on the 2nd until you do reviews on the 2nd. You might want to read through this thread for a bit to get a better idea, but basically the script is currently unable to sync reviews across different devices, i.e. reviews you do on one device will not show up on the others. This is because the API endpoint needed to do so was disabled over a year ago.
I recently switched browsers (Chrome to Firefox) because Chrome was bugging out (giving me “out of memory” errors and disabled extensions that they said would soon be out of date, among these was Tampermonkey with all my scripts). I followed the steps to transfer my review data onto Firefox and it showed up alright. Today when I did some reviews, however, it didn’t register anything. Any way I could fix this?
Edit: it’s working now (I didn’t adjust anything, idk how it works now)
1 Like