Last Screens · No. 017
The last thread
The thread doesn't know that they died. It still says active 3 days ago, still leaves the cursor blinking for a reply that won't come, still prints Delivered under the message no one will read. This entry is about the three things software can do with someone who is gone — pretend, freeze, or finally tell the truth and let you keep writing anyway.
did you get in alright? there’s soup in the freezer if you forgot to eat again
drive safe tomorrow. text me when you’re home.
home. knackered. talk properly tomorrow? x
I keep almost texting you. so I am.
no reply will come. that’s allowed.
What it breaks. The whole grammar of digital presence — active now, the typing dots, the read receipt, Delivered — rests on the one assumption nobody designed an exit for: that the person on the other end is alive. When they aren’t, that grammar doesn’t stop gracefully; it keeps running, and the dead stay quietly “online” by neglect. The interface becomes a small machine for not-knowing.
Why it might work. Grief has rituals everywhere except the place we now do most of our talking, and the platforms’ two answers — leave the account haunted, or wall it behind a frozen banner — are both things that happened to the bereaved, never chosen by them. An interface that tells the truth gently and keeps the thread open as a place to write to rather than with could do what a letter does: give the words somewhere to go.
Where it fails. A thread that invites you to keep writing can hold a person in the doorway of their grief instead of through it — comfort and avoidance wear the same face, and no interface can tell which one it’s handing you tonight. And “memorialization” is already shipped as a retention feature, so the tender version is one product review away from becoming engagement dressed as mourning.
When someone is gone, should the software pretend, freeze them behind glass, or tell the truth and leave the thread open?