Readwise & Reader
The read-later, highlighting, and export system that captured and synced every passage in this library, from Kindle books to long-form articles to individual tweets.
Readwise is the highlighting-and-export service, and Reader is its long-form read-later app, that together form the invisible plumbing beneath this entire wiki. Every page here is built from passages that first passed through Readwise: Kindle highlights sucked up automatically, long-form articles thrown into Reader's queue, and even single tweets clipped for later. The service syncs those highlights out to an Obsidian vault via its plugin, which is why this library exists as local Markdown at all. This page is the one meta-entry in the collection — the tool that produced all the others.
What the two products do
Readwise began as a highlight aggregator: connect your Kindle, Instapaper, or Twitter account and it pulls in everything you flagged, stores it, and resurfaces it. Reader is the newer, second product — a dedicated long-form reading app for articles, PDFs, and even Kindle books, with first-class highlighting, note-taking, and metadata editing. Craig Mod, who became an advisor to the company, describes Reader as where Readwise truly "sings": "a fabulous long form reading, meta-data-editing, article-organizing platform."1
| Layer | Role | Evidence in this vault |
|---|---|---|
| Readwise (core) | Aggregate + store highlights from Kindle, articles, tweets | Every ## Highlights block in these files |
| Reader (app) | Read-later queue for long-form; highlight in-app | Article and tweet captures below |
| Obsidian plugin | Sync highlights to local Markdown | The vault you are reading |
| BOOX Palma | E Ink hardware running the Reader Android app | Mod's "untether" argument |
The capture-to-vault pipeline
The reason this knowledge base is a folder of Markdown notes rather than a locked-in cloud silo is the Readwise-to-Obsidian bridge. Mod explains it plainly: through the Readwise Obsidian plugin he keeps "a locally-stored Obsidian Vault with a full archive of all of my Kindle highlights and notes, with deep-linking into the Kindle app, and highlights from any long form articles I've read."1 Every file in this collection carries the same fingerprint — a ## Metadata block with author, title, source URL, and a highlight_date, followed by ## Highlights with [View Highlight] links back into read.readwise.io.
flowchart LR
K[Kindle books] --> RW[Readwise core]
A[Long-form articles] --> RD[Reader app]
T[Tweets] --> RD
RD --> RW
RW -->|Obsidian plugin| V[(Local Markdown vault)]
V --> W[This wiki]
Every content type in this library flows through it
The assigned sources are a neat cross-section of what Reader captures, which is precisely why they land on this page rather than a topical one. The same service produced:
- A newsletter / article — Mod's Roden essay on reading digitally in 2024.1
- A members' video transcript — his H2 2024 board meeting, highlighted straight from YouTube.2
- A nutrition tweet-thread — Chris Boettcher's "40 sentences" clipped as a compact reference (saved twice, a duplicate-capture artifact of Reader).3
- A productivity tweet — the "Soliloquy" pocket-notebook method.4
- A finance tweet — Kora Reddy's Nifty factor weights (Qual-30 0.40, Value-20 0.10, Alpha-Low-Vol 0.40, MoMo-30 0.10).5
Books, videos, articles, and tweets, all reduced to the same highlight-plus-metadata format — that uniformity is the Readwise value proposition.
Reader as an antidote to the "container problem"
Mod's essay frames Reader not just as a utility but as a fix for a specific pathology: the devices we own are "just so deliciously optimized for not reading."1 His phones, tablets, and laptops are "great at doing everything but reading." Reader, especially on an E Ink device, becomes the container that finally holds attention. He confesses he "cannot sustain attention on a text longer than five-hundred words on my laptop or phone" — but with the Reader app in his pocket he plows through his queue, which Reader calls the "Inbox" in its own vernacular.1
Crucially, Reader dissolves the guilt of the unread pile. Where a Kindle's saved articles become a "Graveyard of Good Intentions," Reader's inbox is something he actually clears — and without the fear of "contaminating" his library view, freeing him to load up old Paris Review interviews he'd otherwise never touch.1
Untethering E Ink from proprietary hardware
The strategic hook of Mod's piece — and why he advises the company — is that Reader ships as an Android app, and the BOOX Palma is an Android E Ink computer. That combination breaks the Kindle/Kobo/Nook lock-in. His verdict: "with E Ink companies like BOOX we can finally untether the quietude of E Ink reading from proprietary hardware."1 It is, he says, "a big win for us readers" and a first step toward "even bigger wins" as the incumbents' "moats may be collapsing."1 The catch he admits: the Kindle's polish, that "Ferrari engine screaming to peel out-ness," isn't quite there on BOOX yet.1
A decade of paying, and a love-hate Obsidian truce
Readwise's grip on Mod is measured in years, not features: he's been "using Readwise services — and paying for them — for nearly a decade."1 Notably, the plugin is the only reason he tolerates Obsidian at all. In his board-meeting riff he cops to a "love-hate relationship with obsidian" and admits "I mainly just use it with the readwise plug-in... because it's just such a great Archive of highlights and notes and stuff from my Kindle books... and also from long form reading in the readwise reader app."2 For actual note-taking he prefers plain Notes for its WYSIWYG feel — Obsidian, for him, is essentially a Readwise export destination. That is a candid admission of what Readwise really is in a workflow: not a thinking tool, but a durable, portable archive.