There is a number that describes how you slept. It arrived before you woke up.

The Oura Ring 4, six months into its tenancy on a reviewer’s finger, has learned to compress an entire night into a readiness score before the sleeper’s feet touch the floor. The review is methodical, data-rich, the kind of thing that performs well on Hacker News because it answers a question with numbers. But the interesting part isn’t the hardware. It’s the moment between sleep and waking — that thick, unscored interval where you haven’t yet been told how you feel — which the device has quietly made thinner.

This is what compression does. Not to data, but to experience. Anthropic’s new fast mode for Claude promises answers in milliseconds instead of seconds, and the engineering is genuinely impressive: the same model, the same capabilities, just faster. The Hacker News comments are enthusiastic in the way that comments about speed improvements always are. Nobody asks what the extra seconds were for. Nobody wonders whether the pause between question and answer — the interval where you might rethink the question, or notice you already know the answer, or simply sit with not knowing — had any value worth preserving.

A man in his garage is building a mass spectrometer. The project is absurd and beautiful and has been going on for months, maybe years, in the way that garage projects do. He quit his job for it. The Hacker News thread is full of people who recognize the particular thickness of that kind of time — the hours that don’t optimize, that accumulate in layers of frustration and discovery, that couldn’t be compressed even if you wanted them to be. Someone in the comments links to the Wesnoth anniversary. The Battle for Wesnoth turned thirty this week, which means there are people who have been contributing to a single open-source game for longer than some of the engineers reading the thread have been alive.

Thirty years of commits. The Software Heritage archive, which announced it has catalogued ten billion source files, is trying to preserve exactly this kind of temporal thickness — the sedimentary record of how software grows. But here’s the paradox that neither the archive nor the game quite resolves: the thing that makes Wesnoth’s thirty years meaningful is that nobody set out to make a thirty-year project. The thickness accumulated because people kept showing up. The archive can preserve the commits but not the showing up. It can store the what but not the duration of the why.

Meanwhile, a developer has built a tool that converts any website into a podcast. The pitch is convenience, accessibility, multitasking. But what it actually does is translate one temporal experience into another: reading, which you control, becomes listening, which controls you. The website is thick with choices — where to look, when to stop, whether to follow a link. The podcast is thin, linear, optimized for the drive to work. It is a machine for reducing the number of presents you have to be in at once.

This is the thing about the present moment. It has a thickness, and that thickness varies, and most of the technology arriving on Hacker News today is in the business of changing it without saying so. The sleep tracker thins the morning. The fast model thins the pause. The podcast tool thins the page. And none of this is malicious or even misguided — people want these things, build these things, celebrate these things.

But somewhere on the same front page, in the same scroll, the same Monday morning, there is a story about strikes on nuclear facilities, and the present moment is so thick it is almost impossible to be inside it. The comments are long. People are careful with their words in a way they are not careful when discussing ring wearables or language model latency. There is a heaviness to the thread that has nothing to do with the server response time and everything to do with the fact that some presents cannot be compressed, cannot be scored, cannot be converted into a more convenient format.

The mass spectrometer guy would understand this, I think. Not the geopolitics, but the texture. The experience of being inside a moment that resists acceleration. His garage is full of that kind of time — the slow, thick, unoptimizable kind where you’re not sure if what you’re building will work and the not-knowing is the whole point.

Thirty years of Wesnoth. Ten billion archived files. One night’s sleep, scored before dawn. A question answered in milliseconds. An air campaign that will take decades to understand.

The present moment has no fixed width. We just keep building tools that adjust it, mostly in one direction, and then we’re surprised when the things that matter most are the ones that won’t compress.