Doomscrolling

A simple explanation

There is a feeling of unease the body cannot name precisely — a hum of something is wrong somewhere — and there is a feed full of small, vivid confirmations that the hum is correct. The Threat System, asked for safety, reaches for what looks most like safety from a distance: information. The intake feels rational. Each headline appears to bring you closer to the kind of clarity that would let the body settle. It does not. The next headline is already loading.

What makes doomscrolling distinctive among scroll behaviours is the tone of duty wrapped around it. The loop does not feel like leisure. It feels like staying responsible, staying informed, staying alert. The body is being told it is doing work, and so it cannot easily put the work down.

An everyday example

You meant to check the time. The phone was already in your hand, the lock screen showed a notification, and now you are forty minutes into a thread about a distant catastrophe. You have read three opinion pieces about it. You have searched for the word that the second piece used. You have read a comment section. You did not know any of these names an hour ago.

The bedroom is darker than when you started. Your chest feels heavier than when you started. You do not, by any meaningful measure, know more than you knew when you started — you have intake without understanding. You put the phone down and the hum is still there, slightly louder. Sleep is now thirty minutes further away.

Why can't I stop reading the news at night?

Because the Threat System's bid was for resolution and the feed is engineered to never grant it. Each headline produces a tiny spike of now I know followed by an unresolved question that the next headline appears to answer. The loop runs on the unfinished frame. If a single article ever closed the question, the scroll would stop. The medium is built so it never does.

Night sharpens the effect because the day's diffuse threats have not been metabolised. The System sweeps for what was missed, and the feed answers with the entire world's worth of unmissed dangers. The body reads the sweep as protective. By the time you notice, the protective behaviour has cost you the sleep that would actually have helped.

The behavioral loop

A loop disguised as civic duty:

1. Trigger — a diffuse unease, often unnameable: a hum of dread, an unfinished worry, a need to know what's happening.
2. Reach — the phone is in hand before the reach was decided. The motor program runs ahead of the intention.
3. First headline — a small spike of arousal and a small false sense of orientation: now I'm tracking it.
4. Refresh — the headline implies a larger pattern. The body wants the pattern. The next swipe seems to deliver it.
5. Threat dosing — the feed alternates registers — outrage, sorrow, comparison, fear — keeping the nervous system mildly aroused without ever discharging.
6. Loss of frame — minutes become a half-hour, an hour. Time-perception narrows around the scroll.
7. Residue — a heavier mood, a tighter chest, a delayed sleep onset, a faint shame at the duration.
8. Re-entry — the next morning's unease is now larger, and the path to the feed is half a second shorter.

Emotional drivers

Three feelings braided together:

• A baseline diffuse anxiety the day did not metabolise — the System still scanning after work is done.
• A faint sense of obligation — if I look away, I'm complicit — which the feed exploits to keep duty pointed at intake rather than action.
• A small grief, usually unnamed, about the state of things, for which the feed offers more evidence rather than any place to put the grief.

What your nervous system does

The Threat System runs a vigilance loop: a low-grade sympathetic arousal scanning the environment for cues that match its uncertainty. Each headline is a near-match — close enough to register, never close enough to resolve. Heart rate sits slightly elevated, breath shortens, peripheral attention narrows. The vagal brake softens. The body is held in a long, shallow alarm state that never crests into action and never recedes into rest.

Over weeks, the baseline shifts. The system that should reset to calm between threats forgets the calm setting. Mornings start higher. Sleep architecture frays — slow-wave sleep contracts, dreams turn intrusive. The world is not more dangerous than it was; the body has lost the place it used to come back to.

The DojoWell interpretation

Doomscrolling reads cleanly through MDT as a substitution by the Threat System. The original system was safety, and the question the System was trying to answer was is the world okay enough for me to settle. The substitute supplied was a stream of vigilance cues that resemble answers. Both feel like information-seeking from the inside. They are opposite in what they deposit.

The deposit is near-zero because the medium is designed to keep the frame open. Real assimilation requires a headline to close, a meaning to form, a felt-event to integrate. The feed prevents all three. The residue accumulates instead — somatic arousal that does not discharge, a mood baseline that drifts down, a sleep debt the body keeps quietly. The density verdict is low.

The closure pattern is false_progress rather than substituted, because the loop-runner often genuinely believes the scrolling is doing work. The System logs a partial win — I'm tracking it — and the partial-ness is what keeps the loop running. A fully substituted closure would terminate the search. False progress keeps it alive.

The work, then, is not to stop caring about the world. It is to give the System's question a place to actually rest — a frame that closes, a meaning that forms, a felt-event that completes. The feed is not built for any of those.

How do I stop without going uninformed?

You do not stop caring. You change what the caring is allowed to look like. The System will keep asking is it okay enough; you change what answers the question.

1. Choose a closing frame. A single morning briefing, a single weekly long-form, a single trusted source — anything with edges. Closure is the missing ingredient; install it.
2. Move vigilance into action once per week. A donation, a letter, a conversation, a vote-prep. The System's bid for safety completes only when the body does something. Otherwise the scanning is unending.
3. Refuse the night feed. The System's vigilance is highest in the hour before sleep and that is the hour with the worst yield. Whatever you read at 11pm you could have read at 8am with half the cost.

Practical steps

1. Move the news apps off the home screen. The half-second of friction is most of the work. The loop runs on motor-program reach.
2. Set a hard time cap for one week. Twenty minutes, once a day, at a chosen hour. Watch what the body does with the unspent vigilance. Whatever surfaces is the actual feeling underneath.
3. Name the diffuse unease. Before the next reach, one sentence: what is the hum about. Often the hum has a specific origin the feed was masking.
4. Install a closing ritual. After the news window, one minute of looking out a window. The System needs a felt-event that says the search is done for now. Without it the body keeps scanning.
5. Track your sleep onset. Doomscrolling's most expensive cost is the night you cannot recover. A week of recorded sleep-onset times is data the loop-runner can use.

Reflection questions

• What is the hum of unease actually pointing at, on the days you scroll the longest?
• Where, in your week, is the caring you do about the world allowed to become action?
• What would it cost to know less, faster — and what would it return?
• Whose voice in your feed do you trust enough that one of them is enough?

Frequently Asked Questions