SMF·MATTER
Can a prompt replace Matter?
Read it later & RSS — read-later, bookmarks and RSS
Exhibit tracking slip
Verdict
The reading part is a solved problem: fetch, run Readability, store, highlight. What makes Matter Matter is that your email newsletters arrive inside it, and that means running an inbound address, parsing HTML email that was never meant to be re-rendered, and stripping tracking pixels. That is doable, but it drags in a mail provider and a domain, and the mobile app and the read-aloud voice do not follow at any price.
Exhibit A — The prompt
Received on31.07.2026Build a self-hosted reading queue that accepts both saved web pages and forwarded email newsletters.
Two intake paths.
URL save: a bookmarklet and a paste box. Fetch the page with a descriptive user agent, honour robots.txt, run Mozilla Readability over it, and store title, author, published date, canonical URL, and the cleaned HTML. Never attempt to get past a paywall or a login; when extraction fails, save the link with a clear "could not extract" state rather than storing a cookie banner.
Newsletter ingest: the user points an address on a domain they control at the app, either through a mail provider's inbound webhook or an IMAP mailbox the app polls. For each message, take the HTML part, strip tracking pixels and one-pixel images, rewrite link-tracker redirects back to their destination where the target is visible in the URL, and run the same Readability pass. Keep the sender as the author and the subject as the title. Show the raw source on demand, because newsletter HTML breaks in creative ways and being able to look is worth more than a perfect parser.
Reading interface: one queue, filterable by unread / archived / source type, with a typography-first reader view. Select text to highlight; a highlight can carry a note. Highlights are the export unit — support Markdown export of all highlights for an article, and a full JSON backup of everything.
Store articles in PostgreSQL with full-text search over title, author and body.
Out of scope: native mobile apps, text-to-speech, cross-device reading position sync, and any recommendation or social layer. Say in the README that reading on a phone means opening the web app in a mobile browser, and that this is the real gap against the paid product.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the iOS and Android apps, which is where most reading actually happens
- B.2 text-to-speech read-aloud with decent voices
- B.3 reading position syncing between devices
- B.4 the recommendation feed built from what other readers highlight
Prior art
Exhibit C — Why people still pay: capture polish, sync, and content partnerships
Because reading happens on a phone, in a queue, on a train. A web app on a laptop is not a substitute for that, however good the parser is.
Questions
Can I get my Matter library out?
Matter exports highlights and a list of saved articles, so highlights and URLs transfer. The cleaned article text does not, so the importer re-fetches each URL, which means anything that has since gone offline or behind a paywall comes across as a bare link.
Do I need my own domain for the newsletter part?
Yes, or at least a mailbox you control. The prompt supports both an inbound webhook from a mail provider and plain IMAP polling of an existing address, so a spare mailbox on a domain you already own is enough. Without either, only the URL-save half works.
What does it cost to run?
A small VPS with PostgreSQL, roughly five to ten dollars a month, plus whatever the mail path costs. IMAP polling of an address you already have is free; a provider's inbound webhook is usually free at personal volumes.
What is the one thing that does not survive the rebuild?
Reading away from your desk. Matter's phone app, the offline cache and the read-aloud voice are the product for most subscribers, and none of it is reachable from a self-hosted web app without writing and shipping two native clients.
Related tools
Receipt