When I tried (and returned) one of their monitors, it was absolutely horrific with ghosting. This was perhaps 5 years ago.

There was no manual, and it had a closed source application to time or force refresh. Of course, being closed source it wouldn't work on a Pi (arm64), nor did I feel comfortable about unknown code, or it working in a few years on a newer version of Linux.

It was all exceptionally poorly done. Amazon says it was a Dasung E-Ink Paperlike 3 HD Front-Light and Touch 13.3" Monitor.

If the app had been OSS, or it had an open API via the cable, I could have scripted an auto-refresh upon scrolling in vi or some such. Or just hacked into something seeing change scope under X. Point is, I could have made it work for me.

The default modes were terrible.

I hope things are better, but no way will I install some weird closed source client.

I have a fairly new tablet, and it handles refresh incredibly well, but I'm sure that's with strong integration into the display stack. Which is fine, of course, but that doesn't help me with coding.

EDIT: one of the things which makes some of these e-ink tablets incredible for refresh, is partial, very well done sectional refresh. So if a small part of the screen changes, BAM!, it's refreshed instantly for ghosting.

Again, I suspect this is tied into the display stack. The monitors I've seen don't seem anywhere as good. I'd love to to be wrong on newer models.