[oarsinsync]

It sounds like there’s a lot more edge case complexity to this than the GP originally thought.

Like most DIY tinkerer solutions, unfortunately, which is why people like paying money for productised solutions - the time it takes to debug and troubleshoot home made solutions is often prohibitive for a lot of people who aren’t techheads.

[inanutshellus]

This is both fair and obvious... but at the same time, the nits folk are bringing up are not fleshed out.

  "I had to reboot my raspberry pi" 

and

  "whoops rando eInk display doesn't do javascript" 

are both super weird and frankly unfair to consider as criticisms of the original solution.

... In short - if our parish priest above sees the original post, I'd suggest he give it a go. It's an hour to set up and won't cost him or his parish anything (aside from buying the eink display ofc).

If it turns out that the DIY solution is insufficient, or his parish is wealthy enough to spend money on a thing like this, great, then upgrade to that.

[Nition]

Kobo readers are fairly non-rando, they're the second most popular eInk readers after the Kindle I think. I agree that lack of Javascript support is not a blocking issue on the use case though (although it does make it a little more annoying).

[inanutshellus]

Luckily the original solution doesn't involve javascript...