Your data lives in a Pod you own -- Blogmarks

What is Solid?

Solid is a W3C specification created by Tim Berners-Lee. At its core is a single idea: give every person a Pod — a typed, permission-controlled web-addressable filesystem. Every resource in a Pod has a URL. The owner decides which applications and agents can read or write. Access is controlled at the protocol level, not by platform policy.

A Solid Pod is Enquire reconstructed for the modern web. Where Tim Berners-Lee's 1980 notebook was local and private, a Pod is distributed and selective — yours to share precisely, yours to revoke, yours to migrate between providers without data loss. Applications are decoupled from storage. You can switch clients without switching data.

The Pod does not know or care which application is reading it, as long as that application holds the right access token. This is the architectural inversion that surveillance capitalism made impossible: the data is yours by default, and you grant applications temporary access, not permanent custody.

Isometric diagram of a Solid Pod showing WebDAV interface, typed resources, ACL permission layer, and multiple client apps

Why it matters

Every major bookmark manager — Pocket, Notion, Raindrop, Instapaper — stores your reading history on its servers, in its format, under its terms. They are better landlords than ad-tech companies, but they are still landlords. You cannot walk away with your data without their cooperation. You cannot grant a new tool access to your own reading history without going through their API.

Solid inverts that model. Your Pod is the source of truth. Blogmarks is a client that reads and writes with your permission — not a server that holds your data hostage. If you stop using Blogmarks tomorrow, your knowledge stays in your Pod, readable by any Solid-compatible client you choose next.

Shoshana Zuboff named the dominant model surveillance capitalism: the unilateral extraction of human experience as raw material for prediction products. Solid is the architectural correction. Not a better privacy policy — a different property regime enforced at the byte level.

How Blogmarks uses this

Blogmarks uses a Solid Pod as the single source of truth for all user data. Raw assets (the original bytes you saved) and their extracted knowledge live in your Pod — not on Blogmarks servers.

Every bookmarked asset is stored as three files: the raw bytes, the extracted Markdown, and an RDF metadata document in Turtle format. The metadata document uses the Blogmarks vocabulary defined against the W3C Solid specification.

This is not a feature. It is a structural guarantee. Blogmarks cannot monetize your reading history because it never possesses it.

Your data lives in a Pod you own

What is Solid?

Why it matters

How Blogmarks uses this

Further reading