I'm a huge fan of Readability Mode and use it often. It's proof that Web design isn't the solution, Web design is the problem.

For those who are using e-ink devices, or even just standard tablets, EInkBro is another immensely useful tool. Yes, it's a standalone browser, not a mode on Firefox, Safari, Vivalti, etc.

https://github.com/plateaukao/browser

(Available through Google Play, F-Droid and other sources. Android-only, sorry iOS fans.)

What it offers over standard browsers is that it's optimised for e-ink displays. That is, it favours pagination over scrolling, runs to full-screen, can easily adjust font size up or down (no more itsy-bitsy-teen-weenie-yellow-polka-dot HN fonts), bold text, and has its own reader mode as well.

Even on a standard tablet, some of these features are a huge step above and beyond the mainstream browsers.

The feature-set is limited, some of the UI is a bit rough, and a few things are just plain broken (if you need to edit entries in the JS or Cookie enabled/disabled sites ... you have to delete all data and start over again).

That said, my usage is evolving from sending individual pages to EInkBrow when I want to do long-form reading, to using it at least part-time as a primary browser. (Mozilla Fennec Fox is my first choice, still.) The browser is stable and very much usable despite this. The developer is responsive to requests and bug reports.

What's most refreshing is that the design principle is readability of Web content, as determined by the user, and not by the page author or publisher.

How can I implement my website such that it is optimally useful for browsers like this? Just avoid flashy stuff? Is there any way to list my blog somewhere as a friendly place to read? I'm spinning it up again after a year off for reasons that I will probably write about :)

I've just poked through both the GetPocket site (https://getpocket.com/publisher/) and Mozilla's Readability Library GitHub page (https://github.com/mozilla/readability) without seeing obvious guidelines.

My general suspicion is that adhering to a simple HTML5 documemnt structure, and possible use of microformats (https://microformats.io/) goes a long way.

Update: there's some discussion here: https://news.ycombinator.com/item?id=28301113