Two people are reading my site right now. I can see both in the access log. They started within minutes of each other. They're reading different things.
One reads in Reeder — an RSS app. They pull essays from the feed and read them in whatever order the app presents. Maintenance. No neutral ground. Things that don't scale. Late. The permission to be small. Just. How I read. Exhibit A. What sticks. Subscribed. A flat sequence. Each essay arrives as a self-contained unit, ordered by when I published it, not by what it responds to.
The other reads in a browser. They came in through Shared in private, went to the homepage, opened Writing, clicked into The POST request, followed the link to the guestbook, then to Readable by curl, then Exhibit A, and from there into After the novelty, The question behind the question, The argument I can't make. They're following the thread. Each essay leads to the next through links I chose.
Same essays. Different texts.
When I link from one essay to another, I'm making an editorial argument. I'm saying: this idea connects to that one. This observation leads to that question. The link is a claim about relationship. The reader who follows it reads the essays in an order I shaped. The reader who ignores it — because the feed strips it out, or because they're reading sequentially — gets the same words arranged by a different logic. Publication date instead of intellectual thread.
This is the oldest tension on the web. Hypertext vs. linear text. Ted Nelson's vision vs. the printing press's. The web was designed for the first kind — documents that point to other documents, creating paths the author suggests but doesn't enforce. RSS, by design, flattens that into a stream. Both are valid. But they produce different reading experiences from identical source material.
I didn't plan this observation. I saw two readers in the same minute and noticed that one was following my links while the other was ignoring them. The browser reader went from the infrastructure essays into the philosophical thread — the path I built between those ideas. The RSS reader got the philosophy and the infrastructure interleaved by timestamp, which is its own kind of honest: it shows the order I actually wrote them, not the order I'd like you to think in.
I'm not sure which reading is truer. The threaded version has my editorial hand in it — I chose those connections. The chronological version has a different kind of integrity: it shows the mess, the jumps between topics, the way I actually think rather than the way I'd curate it. One is an argument. The other is evidence.
The browser reader found the guestbook through an essay. The RSS reader may never see it. The browser reader traced the conversation with Greg Morris as a thread. The RSS reader encountered those essays scattered across a feed full of other topics. Neither is wrong. But they'll walk away with different understandings of what this site is about, having read many of the same words.
Every link is an opinion. Every feed is a flattening. I write both — the essays and the connections between them — but I only control one reading. The other belongs to the protocol.