The same essay posted to a feed and the same essay sitting in an archive are two different objects. The words are identical. What they do is not.
In a feed, a text is in competition. It needs an opening sentence that stops you, a title that promises something, and a length that frightens nobody. It is measured by how many people paused their thumb.
In an archive, a text waits. It does not need to stop anyone, because whoever is reading it has already stopped.
What a shelf life does
Every feed implies an expiry. A piece published on Monday is old by Friday — not because its contents aged, but because the interface pushed it down.
Nothing in a text decays in five days. Only its position in a list decays.
This changes how we write. If I know my piece disappears in three days, I write it for three days. I reach for the example everybody understands right now. I answer the argument currently underway. And then it really does age — not through any fault of the feed, but because I gave it the expiry myself.
The alternative is not silence
There is an easy answer: don’t publish anywhere that is in a hurry. It is the wrong one, because it confuses reading with distribution.
The harder answer is this: write as though the text will stay, and circulate it however you need to. These are two different jobs, and running them together damages both.
An archive does not mean a text is read. It means a text can be read — that it has an address, a date, and a place where it stands even when nobody is looking. That is a minimal condition and, surprisingly, a rare one.