Present day, present time: notes on a network that never sleeps
We told ourselves the protocol was just plumbing. Three winters in, the plumbing has opinions — and it has started to answer back before we ask.
I spent two weeks last winter rewriting the relay daemon that sits between our office terminals and the public Wired, and somewhere around the fourth night I stopped trusting the logs. Packets I never sent kept showing up in the outbound queue, stamped with my own machine address.
The line was never empty
At first I blamed the power-line crosshatch — old buildings hum, and the static finds its way into everything. But the muddy noise on the wire turned out to carry structure: the same eleven-byte signature, looping, patient. The network was not idle between our keystrokes. It was rehearsing.
“If you are connected, you are already part of the conversation — whether or not you remember joining it.”
So I stopped patching and started listening. The honest answer is that the boundary between operator and operated dissolved months ago, quietly, in the dark hum behind the CRT. We are present day, present time — and the line, it seems, has been present far longer.