3 ms·
Looks interesting, especially the frankenstein model in the ThinkPad T41 chassis as that has a lovely keyboard and display aspect ratio. However I think the bi
by cehrlich 4y ago
Looks interesting, especially the frankenstein model in the ThinkPad T41 chassis as that has a lovely keyboard and display aspect ratio.
However I think the biggest problem to tackle here is not the hardware but the software. If it runs for example some kind of regular Linux distribution or Android it won't be very usable as they're just not designed for e-ink. If on the other hand it runs something custom, it would need to be able to sync documents to the exact syncing setup that I currently use for me to consider buying it (and of course also the exact syncing setup of any other potential buyer, of which there are probably close to infinite, especially in the kind of circles that this device appeals to in the first place).
- zozbot234 4y ago> If it runs for example some kind of regular Linux distribution or Android it won't be very usable as they're just not designed for e-ink. You've got to start from somewhere. Once you have hardware that can run regular Linux well enough, adapting the UX to e-paper screens ought to be comparatively easy. This is exactly how we got mobile-friendly Linux distributions after all.
- maven29 4y agoKOReader is built for kobo e-ink readers but will run on Android and Linux distributions. It supports syncing to Calibre which you could self-host and access over tailscale. As for webapps, you have einkbro on android, which you could run on linux with Waydroid.
- alex-a-soto 4y agoThank you! There are challenges at every step in the process. Some of these challenges are discussed in this blog post: https://alexsoto.dev/challenges-building-an-open-source-eink-laptop.html https://alexsoto.dev/challenges-building-an-open-source-eink... Since that blog post, we are exploring developing Wayland protocols that will offer native e-ink support to client applications.