▤ eink.article

This Blog Might Support Your E-Reader

E-Ink is the best. I care little for the rest. Like paper, no less.

Kindling Interest

A first-generation Kindle resting on its book-shaped box BCSAJQKHNORMGEPTDXBCSAJQKHNORMGEPTDXBCSAJQKHNO kindle

The single most important design influence on my blog was thinking "How would I want to read this?"

The answer that came to mind was "On my Kindle."

In 2007, my aunt gave my dad an absurdly designed white parallelepiped, which weighed nothing, contained an infinite number of books, had no annoying cover to deal with, and had no pages to turn.

Within the next few years, this thing soon became mine, as my dad was busy with work, and I would spend the following years reading off it whenever I could. My teachers hated it, I think. In fact, I'm quite certain my 2nd grade teacher deliberately destroyed the thing's screen when I left it in my backpack, probably because I was terrible and cared more about it than anything in her dumb class. Which is fine, my dad is handy and he fixed it.

Obviously, I started to value Amazon's simulation of reading a physical book far above that of the actual thing, as anyone would. Real books are smelly, dirty things that get touched on by everyone else. They're bulky to boot. At the same time, though, I began to place this simulation above Microsoft and Apple's conventions too. There was an intention related directly to what is pleasing to biology, rather than a compromise struck between engineering constraints and established systems. I really liked that. It was a delightfully unconventional idea, that perhaps that which was ideal was something perennial we had already discovered by accident as a species (Books, Apple's System 5) but without the right technology to express it fully we had differentiated and experimented with what we could down one of the river's deadarms.

Careless Whispernet

Some of my early internet usage was on my 2009 MacBook, but a surprising amount of it was via the browser on the 1st and 2nd Generation Kindles. You'd think this would be terrible, but back then the internet was slow to begin with. I was browsing iFunny in 2011 on a monochrome screen, and waiting minutes at a time for an image to load. The refresh rate was no problem at all.

However, it taught me that the internet was largely ugly on this screen, because the internet was meant for LCD monitors and tube displays. Gradients, something Amazon even included in their menu design back then, looked silly. Like a printout of a screen-capture of a computer program in the newspaper. What looked best was simple, what could be made into type and pressed into a page. High contrast.

Thankfully, my tastes would get a phenomenal justification. On most E-Ink displays, 1-bit color is fastest. Adding grays to that creates hideous dithering, or is crushed into either the blacks or whites.

Putting Pen to Paper

So, when it came to this blog, I had learned from one of my friends that HTML was originally intended for encyclopedias. This made me extremely happy, it fed back into the ideas about what computers could be that excited me so much before. In my mind I established three rules for how the website could look and work, but I now realize that they could be useful to others, or more likely, to LLMs that have been prompted to make a beautiful E-ink first webpage.

  1. Two Colors.
    • No drop shadows, no gradients.
    • If something needs a different value, that can be expressed using weight, inversion, or borders.
    • If something would be 'greyed out' on another website? Strikethrough.
    • I use absolute white and absolute black because I think contrast is something that should be up to the user and their machine. Approximating that ahead of time seems like it's reducing the amplitude of the crisp signal heading their way, but that could just be a feeling.
  2. No motion.
    • This is less necessary nowadays thanks to Modos, but E-ink is something that traditionally has had terrible refresh rates (which, honestly, I saw as a feature 4 years ago), and cool animations will just look like a mess and possibly decrease the life-expectancy of your users' panel.
    • Scrolling is kinda tough to gauge here, but I think as long as you can control the scroll via key inputs where it happens instantly it's good. You get a progress bar in the form of the scroll bar, and you don't have to have some weird "next page" button that wouldn't correspond with a proper E-Reader's anyway. I have considered keybinds for flipping through pages though. You may want to do it that way instead.
    • Some things require motion, like clocks, but you can solve this by just updating once every 20-60 seconds.
  3. No pointer necessary.
    • This is really a subset of no motion. Pointing is something very motiony: dragging things, moving mice to select things, you need refresh rate for that.
    • So we must ensure everything a mouse can do to a window, the keyboard can do too.
    • I actually didn't know how to implement this for the longest time, so I asked Claude.

On Paper

This ended up having a few interesting snags. For one, most operating systems don't really want you to do this. Particularly, emojis: browsers and OSes like to mess with these in completely un-expectable ways. Apple worked hard on their emojis, so I totally get that they want to show them off, but it's not really what I want. So, I went to an old solution: Twemoji! Kinda. At least, the general idea of it. At build, we find all the emojis used on a page, make them into svgs, inject them instead of the unicode, and "Hey, presto!" we can consistently keep our monochrome emojis.

You might think this harms text selection, since an svg isn't a character. We solve it the same way Twitter did: the real character is still there, invisibly, so copying, searching and screen readers all get it. Oh, this also saves us a ton of bandwidth since we don't have to send over a giant font for every page.

Bandwidth is something that seemed important to address too. Even though internet speeds are increasing and becoming very cheap, it seems dumb to use that as a crutch, especially because many ePaper devices are painfully low-spec.

What a first visit to the home page downloads, before and afterBefore: 6242 kilobytes, of which 5189 are fonts. After: 556 kilobytes, split fairly evenly between styles, scripts, the emoji sprite, the page and one font. before · 6,242 KB fonts 5189translations 482emoji sprite 276scripts 141 · styles 134 · page 20 after · 556 KB same scale after, enlarged fonts 74emoji sprite 110scripts 145styles 146page 75translations 6

But, I'm also lazy, so we handle that at build time. Photos go in as… whatever I want, photos come out as .avif! Which is a good format! For this particular use case, I think. Browsers too old for it get a .webp, and ones too old for that get the original. Fonts are cut up by Unicode block ahead of time, and your browser only fetches the blocks a page actually uses, so we never have to send over thousands of glyphs that will never ever see your screen.

Moving to a build step for many things, like pre-dithering the photos for E-Ink devices and language injection, keeps hard work and potentially non-compatible js off the users' devices too. I have no idea if that was a problem before or not, but like, we're going to be chivalrous and treat E-Ink devices like delicate flowers that should be pampered as much as possible. That's probably a good idea in general for a good deal of web stuff. Especially for a blog, y'know, where everything is text so if anything was particularly intense it would be a breach of expectations.

Paper Tiger

But there are some disclaimers. Not with my rules, those are ironclad and perfect, but with my execution. JS is mandatory for a lot of my site's features, and demos on certain articles. The window-based design is definitely more System 5 than Kindle, windows are inherently motion-coded. But I think in terms of windows, it's a good way to organize things IMO. There is a flash of motion when my windows try to rearrange themselves on a JS device so you won't have to yourself. Also, compatibility with older devices might be bad, and I also never tested performance on older devices to begin with so it might already have been fine from the start. Oh, and dithered images take more bandwidth than non dithered images, but that's probably mostly to do with the fact image formats are designed to compress real images well, and not pointillism. There may be an interesting solution for that.

For now, E-Ink mode is also stuck on by default, and if you don't have js there's no way out of it. However, the images without JS render using an older trick where the colors are all crushed into black or white, with contrast, so they are worse that way. Again, there may be an easy solution. I like that as a dead-man's switch, but without JS you do have to hit tab a bunch to do things keyboard-only. The dead-man's switch is necessary though, because even though there's a css @media (monochrome) query, it's not guaranteed an E-Ink device will properly share its identity in a way that engages with it. You may then therefore get the impression that I don't particularly care if a non-E-Ink user gets an E-Ink-like experience, and you would be completely right, because I personally want to have an E-Ink-like experience on all my devices.

TLDR

system.settings

Display Theme



colors
silly

developer

Visitors only ever get the tiles with JavaScript off. This preview is saved in this browser until you turn it off.

Copyright & Licensing

All photographic works displayed on this website are the intellectual property of the author.

Reproduction, distribution, or transmission of these photographs in any form or by any means for any purposes, without prior written permission, is prohibited. (This is just to force you to ask me so I can know if people like my photos :P I don't actually mind.)

All other content, including code and written text, is freely available for use, modification, and distribution under a permissive license unless otherwise stated.

This website uses the following fonts: EB Garamond and Frank Ruhl (SIL OFL), Noto Emoji and Android Emoji (Apache 2.0), Noto Sans Symbols 2, Noto Sans Math and GNU Unifont (SIL OFL), Twemoji by Twitter (CC BY 4.0), FairfaxHD by Rebecca Bettencourt (Personal Use License), Symbola, and Selyodka.


program.launcher
system.keys
←↑↓→
window.move
Esc
window.close

W
window.next
⇧W
window.previous
?
system.keys
S
system.settings
C
shaon.zmanim
E
E-Ink Mode
T
Display Theme
L
Interface Language
H
pelmeniboiler
shaon.zmanim
–
chalakim – regaim –
–
⋯
🌅 – 🌇 –