Why call it poetry? Because poetry thrives in ambiguity, compression, and loss. A poem often says more by what it omits than by what it includes. A corrupted file, a half-loaded webpage, a directory listing from an old backup—these are the haiku of information technology. They present fragments: ????.doc , Untitled 1 , (corrupt) . They force the user into an act of interpretation. What was this? A love letter? A spreadsheet? A half-finished novel? The metadata might tell you a date, a file size, a creator name, but the soul is gone. Filepo is the epitaph not just for the file, but for the intention behind it.
In a corporate context, Filepo is a liability. In a personal context, it is a kind of digital archaeology. But in an artistic or philosophical sense, it is a mirror. Our files are extensions of our memory. When they rot, we confront the fragility of our own recall. The .jpg that now only renders the top third of a photograph—what face is missing? The .mp3 that plays static instead of a song—what melody is lost? We become archivists of our own forgetting. filepo
In the age of the cloud, we like to imagine our data is immortal. We upload, sync, and back up with the quiet faith that somewhere, on a server blinking in a desert warehouse, our digital selves will outlast our bones. But there is a quieter, stranger truth: files decay. Not in the physical sense—no rust, no water damage—but in the ontological sense. They become unreadable, forgotten, orphaned by software updates, locked in obsolete formats, or simply lost in the infinite recursion of folders within folders. I call this condition Filepo —a portmanteau of file and epitaph —the slow, silent poetry of digital rot. Why call it poetry
