What this is, and why I started keeping it
A note on why doomscroll.txt exists, and what I'm actually trying to do here.
I didn't set out to build a media platform. I set out to answer a smaller, more embarrassing question: why does my phone feel like it's watching me think.
Not in the conspiracy sense. In the ordinary, everyday sense, where a model finishes my sentence before I've decided what I mean, where a feed learns my mood faster than my friends do, where I catch myself asking an AI what I think before I've actually thought it. That gap, between having a feeling and having a model already respond to it, is new. It didn't exist five years ago. Most days it's invisible. Some days it's the only thing I can see.
I started keeping notes on it the way you'd keep notes on a symptom. Not because I had a diagnosis, but because I wanted a record, something to check my own memory against later, when the strangeness of this period has worn off and everyone insists it always felt normal.
Why this isn't a newsletter about AI
There's no shortage of places to read about the technology itself: what model shipped, what benchmark it beat, what it means for the stock. That coverage is necessary and I read plenty of it. But it mostly stays at the level of the tool. It rarely stays with the person holding it.
I wanted something that sits closer to the ground. Not "AI is changing work" as an abstraction, but the specific, small, slightly humiliating ways it's changing how I write a text message, how I argue with someone I love, how I decide what's worth remembering versus what I can just ask for later. The stuff that doesn't fit in a headline because it's too personal to verify and too common to ignore.
That's the gap doomscroll.txt is trying to sit in. Essays for when something needs the full shape of an argument. Signals for the smaller, faster observations that don't need three thousand words, just a moment of "wait, is anyone else seeing this."
Why it looks like this
The name is on purpose. Doomscrolling is usually something that happens to you, an hour disappears, you surface with a headache and no memory of what you read. I wanted to take that same compulsive, restless, always-refreshing energy and point it at something with a spine. Still fast. Still dense. Still built for the part of your brain that wants to check one more thing before bed. But accountable to itself, the way a real record has to be.
That's also why signals sit right next to essays instead of in some separate "news" tab. The fragments and the arguments are describing the same thing from different distances. Sometimes a single headline tells you more about where we are than a thousand-word take does. Sometimes it takes the thousand words to explain why the headline mattered at all.
What I'm not promising
I'm not going to pretend I have this figured out. Some of what's on this site will age badly. Some of the signals will turn out to be noise. I'm writing this in real time, which means I'm wrong sometimes, and I'd rather be visibly wrong in public than quietly certain in private.
What I can promise is that I'm not writing from outside this. I'm not a company issuing guidance from a safe distance. I'm someone who also can't quite tell anymore whether a thought is fully mine before it's touched a model, who also feels the specific vertigo of watching a technology rewire attention, relationships, and memory faster than any of us can build language for it. This is me trying to build that language anyway, in public, a little at a time.
If that's useful to you, or even just recognizable, welcome. Come back when something changes. Something always does.