HN Debrief

I turned my RSS feeds into an e-ink newspaper to stop reading on my phone

  • Developer Tools
  • Hardware
  • Productivity
  • Open Source

The post is a personal build writeup about packaging RSS feeds into an e-ink newspaper so the author can read blogs and news on a dedicated device instead of a phone. The appeal is less about novelty than about changing behavior. E-ink strips away alerts, browser tabs, and infinite feeds, and makes lightweight reading feel closer to sitting with a paper than poking at an app.

If you want this for yourself, the hard part is not rendering text to an e-reader. It is building a low-friction pipeline for full-text extraction, syncing, and offline access, or deciding that stricter phone controls are a simpler fix.

Discussion mood

Positive about the goal and nostalgic about print, but practical to the point of skepticism about the execution. People like the idea of e-ink as a healthier reading surface, yet keep running into the same blockers: partial RSS feeds, clunky syncing, and e-reader software that is still far behind general-purpose tablets.

Key insights

  1. 01

    Calibre already solved the newspaper part

    Calibre’s long-standing news recipe system changes the story from a clever one-off hack into a rediscovery of existing tooling. That matters because the problem is mature enough that you should start from battle-tested feed ingestion and periodical generation, not from custom conversion scripts unless you need something very specific.

    Check Calibre before building your own pipeline. If its recipes and scheduling cover your needs, you can spend your effort on delivery and habit design instead of feed parsing.

      Attribution:
    • zie #1
  2. 02

    Full-text fetching is the real enabler

    Miniflux’s ability to pull article bodies for incomplete feeds is what makes an e-ink workflow viable at scale. Without that layer, every suspicious truncation pushes you back into a browser, which defeats the whole point of using a distraction-resistant reader in the first place.

    Audit your feeds before you commit to an e-ink setup. If many are partial, add a fetcher like Miniflux early or expect constant fallbacks to the web.

      Attribution:
    • MattTheRealOne #1
    • dewey #1
  3. 03

    The winning setups all remove manual sync

    The useful systems here are not just about putting articles on e-ink. They turn articles into a library object that the device already knows how to consume. EPUB into OPDS, Wallabag into KOReader, or a morning push into ReMarkable all work because they fit the e-reader’s native distribution model instead of fighting it with ad hoc transfers.

    Design around your device’s strongest ingestion path. If it already handles OPDS, EPUB libraries, or read-later sync well, build on that instead of forcing live RSS onto underpowered hardware.

      Attribution:
    • podgietaru #1
    • ratio53 #1
    • tmjwid #1
    • joshgachnang #1
    • mateioo7 #1
  4. 04

    Client-side capture beats feed parsing for paywalled pages

    Readeck’s client-side capture via browser extension gets around a common failure mode of RSS-based systems. Publishers often expose only excerpts or hide content behind scripts and login flows. Capturing from the browser after the page is rendered can preserve the full article where feed fetchers and server-side parsers fail.

    If your reading list includes paywalled or badly structured sites, add a capture tool alongside RSS. A pure feed-based system will leave holes in your archive and push you back to the phone.

      Attribution:
    • teroshan #1
  5. 05

    Print newspapers were a remarkable production machine

    The nostalgia around paper was not just aesthetic. A former newspaper editor described the daily choreography of editorial, design, production, ads, and printing, with older analog processes still mixed into 1990s digital workflows. That reframes the e-ink “newspaper” idea as an attempt to preserve the reader experience of print, not to recreate the industrial system that made it possible.

    If you are building digital products that borrow from print, separate the format from the operation. You can capture the ritual and pacing of a newspaper without inheriting its production complexity.

      Attribution:
    • ilamont #1
    • hydrogen7800 #1

Against the grain

  1. 01

    Device swaps do not fix compulsive phone habits

    For some people, an e-reader full of worthy material still loses to the phone sitting next to it. The more credible fix here was not another reading device. It was aggressive friction on the phone itself, like app blockers, grayscale mode, and making the e-reader carry lighter leisure content instead of only “serious” reading.

    If you have already failed with dedicated readers, work on the phone first. Remove fast paths to distraction before you invest more in alternate hardware.

      Attribution:
    • TFNA #1
    • mswphd #1
    • noman-land #1
    • al_borland #1
  2. 02

    Phone dependence can be infrastructure, not weak will

    In some countries, the smartphone is not just a bad habit delivery vehicle. It is the authentication token for payments, identity checks, and access to routine services throughout the day. That makes “just leave it at home” sound glib and misses a real systems constraint.

    When designing for digital wellbeing, treat the phone as civic infrastructure in some markets. Solutions that assume users can abandon it outright will not travel well.

      Attribution:
    • TFNA #1 #2
  3. 03

    Matte LCD may be good enough now

    TCL’s Nxtpaper was raised as a practical alternative to e-ink. The pitch is simple. Keep normal screen speed and color, then switch into a more paper-like mode when reading. That undercuts the assumption that dedicated e-ink hardware is the only path away from a harsh phone experience.

    Test newer low-glare display modes before buying into a specialized e-ink stack. A better screen on a mainstream device may remove enough friction to win on net.

      Attribution:
    • alsanan #1

In plain english

Calibre
A popular open source e-book management application for organizing, converting, and sending books to e-readers.
client-side capture
Saving a web page after it has been rendered in your browser, which can preserve content that server-side tools miss.
e-ink
A reflective display technology used in e-readers that looks paper-like and uses very little power when showing static content.
epub
A common ebook file format used by many readers and publishing tools.
Instapaper
A service for saving web articles to read later in a simplified format.
Kavita
A self-hosted digital library server for books, comics, and documents.
KOReader
An open source document and e-book reader used on e-readers and other devices as a replacement for stock reading software.
Miniflux
A minimalist RSS reader that can also try to fetch the full text of linked articles.
Nxtpaper
A TCL display technology designed to look more paper-like while keeping the speed and color of conventional screens.
Omnivore
A read-it-later and RSS application that some users self-host to manage saved articles and feeds.
OPDS
Open Publication Distribution System, a catalog format used to browse and download e-books from online libraries and servers.
Readeck
A self-hosted read-it-later tool that can capture web pages, including through a browser extension.
ReMarkable
A popular e-ink tablet focused on writing and document reading.
RSS
Really Simple Syndication, a standard web feed format that lets sites publish updates readers can subscribe to.
wallabag
An open source read-it-later service that saves web articles for later reading.

Reference links

Core tools and services

  • Calibre news recipes documentation
    Shown as an existing built-in way to turn feeds into e-reader-friendly news publications.
  • inkfeed.xyz
    A web-based RSS reader built for Kindle and other e-ink devices, repeatedly offered as an alternative approach.
  • reader.inkfeed.xyz
    Mentioned because a commenter reported feed loading errors in the live reader interface.
  • Jomo
    Suggested as a strict phone-blocking tool for reducing distraction without changing reading hardware.

Self-hosted reading stacks

  • Readeck
    Recommended as a self-hosted read-it-later tool that captures content client-side and works well with e-readers.
  • Readeck KOReader plugin
    Adds Readeck integration to KOReader for sending saved articles to an e-reader workflow.
  • Readeck Firefox extension
    Used for client-side capture of full pages, including sites where RSS or server-side parsing fails.
  • freeMarkable
    Shared as a way to extend the software capabilities of ReMarkable devices.

Device platforms and roadmaps

  • Crosspoint roadmap
    Cited to show that active connectivity features like RSS, news, and browsers are explicitly out of roadmap.

Related projects

  • tuhat.net
    A similar project for browsing and downloading posts or serialized collections as EPUB on an e-reader.