Sorry this came back. It’s the same problem as before, where some newer browser features slip into the code and Kindle’s older browser can’t handle them.
I’ve just pushed an update that replaces the incompatible parts, so please refresh and give it another shot on your Kindle. To stop this from recurring, I’ve added an automatic check that now runs every time I deploy, which makes it less likely that these Kindle-incompatible features get into the live site. It’s not a guarantee though, so if this happens again, please continue to let me know!