for dashboard software like this are there any reliable techniques to prevent burn-in? I'd like to set up a large screen with a dashboard but I don't want to wreck the screen
Generally this is solved by displaying more than one image and rotating between images on a time interval.
> It's designed for both screens that update 60 seconds per frame, and for screens that update 60 frames per second.
Or that's what at least I infer from that, because I don't know of 60 fps eInk displays :).
It should be really easy to build a FrameOS app that does this. Add one node at the start of the render loop to increase the image accordingly, and one at the end to crop it back down. I was planning to use a similar technique to display smooth scrolling animations/slideshows, but it can definitely be used to prevent burnin.