In 2012, a writer named Jack Cheng published a short essay called "Slow Web." It was not a manifesto. It was an observation: that the web had optimised itself for speed in ways that were actively hostile to the human experience of using it. That the real-time, always-on, perpetually updating nature of the modern internet was not a feature but a pathology. And that a different kind of web — slower, more deliberate, more human — was both possible and desirable.
The essay circulated quietly among designers, developers, and writers who recognised something in it they had been unable to name. A decade later, the conditions Cheng described have become so extreme that the observation reads less like insight and more like understatement.
The Slow Web is not a technology. It is not a platform or a protocol. It is a philosophy of use — a set of principles for engaging with the internet in ways that serve human depth rather than platform metrics.
The Slow Web is not about using the internet less. It is about using it differently — deliberately, at a human pace, in service of what you actually came for.
Where it came from — the Slow movement
The Slow Web draws its name and intellectual lineage from the Slow Food movement, founded by Carlo Petrini in 1989 as a response to the opening of a McDonald's near the Spanish Steps in Rome. Slow Food was not opposed to food. It was opposed to a particular relationship with food — one that optimised for speed, uniformity, and throughput at the expense of quality, culture, and pleasure.
The same structure applies to every "Slow" movement that followed: Slow Travel, Slow Fashion, Slow Journalism, Slow Science. Each identifies a domain that has been colonised by an industrial logic of speed, and proposes a return to human-scale engagement with it. Not rejection of the domain — rejection of the speed imperative.
The Slow Web makes the same move for the internet. It is not anti-technology. It is anti-extraction. The web optimised for engagement is not optimised for humans. The Slow Web proposes a web that is.
Jack Cheng's original distinction
Cheng's 2012 essay distinguished between "timely" and "timeless" on the web. Timely content — news, social media, notifications — creates a sense of urgency that demands immediate consumption. Timeless content — essays, books, long-form journalism — rewards deliberate engagement and retains its value over time. The Fast Web, Cheng argued, had overwhelmed the timeless with the timely. The Slow Web is an attempt to restore the balance.
Fast web versus Slow web
The principles of Slow Web practice
The Slow Web is less a set of rules than a reorientation of values. But several consistent principles emerge from the various writers and practitioners who have articulated it.
Timely information has an expiry
Most news that felt urgent this morning will be irrelevant by evening. Most breaking stories that demanded immediate attention will be forgotten within a week. The Slow Web practitioner reads news on a delay — newsletters, weekly summaries, deliberate sessions — rather than in real time.
Natural stopping points are features
Infinite scroll is designed to eliminate the moment when you would naturally stop. The Slow Web values tools and practices that have clear endpoints — the end of an article, the bottom of an email, the last item in a curated list. The pause is where reflection happens.
Subscription over algorithmic discovery
The algorithm surfaces what will hold your attention longest. Subscription surfaces what you chose when you were calm. RSS feeds, email newsletters, and curated links give control of the reading experience back to the reader. You decided what enters your attention before the content itself could manipulate that decision.
Depth over breadth
Reading one long essay carefully produces more genuine understanding than skimming twenty headlines. The Slow Web chooses depth: finishing what you start, rereading what merits it, thinking about what you read before moving to the next thing. This is not inefficiency — it is the only kind of reading that changes you.
Asynchronous over real-time
The expectation of immediate response — to messages, comments, emails — is a social contract that the Fast Web created and enforces through anxiety. The Slow Web practitioner responds when they are ready, not when the notification demands it. Delay is not rudeness. It is autonomy.
Intentional sessions over ambient use
The phone that is always available is never fully present for anything. The Slow Web practitioner uses the internet in deliberate sessions with defined purposes, rather than as an ambient background to every other activity. You go online to do something specific. You leave when it is done.
The Slow Web manifesto
// Principles of Slow Web practice
Slow Web tools — what the practice requires
The Slow Web is not practised in the abstract. It requires specific tools — or the deliberate absence of specific tools — that support its principles rather than undermine them.
- RSS readers — Feedly, NetNewsWire — let you subscribe to sources on your own terms, reading when you choose rather than when the algorithm decides to surface content.
- Email newsletters — particularly weekly or monthly digests — compress the timely into the deliberate. You read it on schedule, not in real time.
- Read-later services — Instapaper, Pocket — create a buffer between discovery and consumption. You save now, read when you have genuine attention.
- Time-locked vaults — for the reactions, responses, and thoughts that feel urgent but rarely are. Write it. Seal it. Read it when the urgency has passed.
- No notifications — the single most structural Slow Web practice. Not reduced notifications. None, for everything except direct person-to-person communication.
The Slow Web is not a nostalgia for the past. It is a design specification for a future internet that serves human beings rather than extracting from them.
CHRONOS as a Slow Web tool
CHRONOS was designed as a Slow Web tool from its first principles. It has no feed, no timeline, no notification system, no algorithm. There is no content to scroll. There is no engagement loop. You open it when you choose, write when you need to, seal what you write, and close it.
The time-lock is the most explicitly Slow Web feature: it enforces the delay that the Slow Web values. The reaction you write in real time cannot be retrieved until the moment you assigned. The urgency dissolves. The considered version of you decides what happens next.
AES-256-GCM encryption ensures that what you write in CHRONOS belongs to no one but you — no data, no profiling, no algorithmic processing of your thoughts. Offline-first architecture means it works without a connection. The entire system is designed to be used and then left alone.
This is what a Slow Web tool looks like: it does one thing, it does it well, it has a natural stopping point, and it has no interest in keeping you engaged beyond the moment of genuine use.
CHRONOS
One tool. One purpose.
A natural stopping point.
Write it. Seal it. Close the tab. That is the entire relationship CHRONOS wants with you.
Open CHRONOS