The Ghost Map and the Live Feed: Two Visions of Public Memory

In the quiet hall of a city archive, I once pulled a heavy ledger from a shelf. Inside, a clerk’s meticulous handwriting recorded the details of a century-old property transfer. The ink was faint, the paper brittle. It was a perfect snapshot, a record frozen at the moment the pen left the page. This is the promise of the Ghost Map: to capture a moment with such precision that it becomes a permanent, if static, coordinate in time. It’s the foundational logic of most digital preservation. We take a website, a dataset, or a document, and we make a copy. We call this snapshot a WARC file or a PDF/A, and we store it away, hoping its meaning remains legible to future generations. The goal is to stop time, to prevent the entropy of digital decay from erasing the record.

Then there’s the Live Feed. Think of a government’s real-time transit API, continuously pumping out the location of every bus and train. Or a dataset tracking air quality, updated not yearly or monthly, but every minute. There is no single, definitive version of this data. To archive it statically would be to miss the point entirely. Its value is in its constant, pulsing present-ness. The Live Feed isn’t a map; it’s the river itself. Its preservation is not about creating a perfect frozen artifact but about maintaining a pipe through which the present can always flow into the future.

These two philosophies—the Ghost Map and the Live Feed—represent a fundamental tension in how we think about preserving our digital commons. The Ghost Map approach, descended from the traditions of physical archiving, asks: "What is the canonical version of this thing?" It seeks to preserve an object. The Live Feed approach asks a different question: "What is the essential, ongoing process here?" It seeks to preserve a stream.

The danger for the Ghost Map is irrelevance. A website archived in 2010 tells you nothing about its state in 2024. It can become a beautiful, accurate relic of a past that no longer connects to the present. The danger for the Live Feed is volatility and loss of context. If the API endpoint changes, the feed breaks. If we don’t also preserve the schema and the software that interprets it, the endless stream of data becomes a meaningless torrent of numbers, a history without a narrative. It’s a river with no banks.

The most robust public memory, then, may not be a choice between the map and the feed, but a conscious weaving of both. We need the periodic, high-fidelity snapshots of the Ghost Map to provide stable reference points and context. But we also need the infrastructure to maintain the Live Feed, to understand the dynamics of the systems that shape our world in real-time. The challenge for today’s archivists and data stewards is to be both cartographers of the past and hydrologists of the present, building a record that is both deeply anchored and vividly alive.

Notes & further reading

A few pages I came back to while writing this: