A hex dump where one line still spells something

On the back of a near-black tee, rows of hexadecimal run corner to corner, pale green like a screen's own afterglow. Most of it is noise — byte pairs that don't resolve into anything readable. One horizontal run near the middle sits at full strength while everything around it stays faded, and reading that run as characters instead of numbers gives you two words: COME HOME.

Nothing here was deleted. It just stopped being read.

What is a wall of hexadecimal actually showing?

Raw memory, read back exactly as it's stored, before anything decides what it means.

A file system doesn't store words — it stores bytes, and hexadecimal is just those bytes written in a base a person can scan without translating each one to binary by hand, the same practical logic as a diagram drawn to show what's actually wired together rather than what's supposed to be. Most of a memory dump reads as noise because most of what's in memory at any moment isn't meaningful on its own — fragments of old processes, padding, values left over from something that finished hours ago. The hex doesn't lie about that.

Why does deleted memory ever surface again at all?

Because deleting something and erasing it are two different operations, and most systems only do the first one by default.

Telling a system to delete a file usually just removes the pointer that says where it is — the address, not the content. The bytes stay exactly where they were until something else needs that space and writes over it, which can take a long time or might never happen at all. Recovery isn't magic; it's reading the space the pointer used to point to before anything overwrote it. A legible fragment surfacing out of a hex dump is what that process looks like from outside, not a special case.

What makes the surfacing fragment work rather than feel sentimental?

Leaving it flat, the way the hero does, rather than framing it, colouring it differently for emotional effect, or building a whole design around explaining what it means.

COME HOME gets brighter than its surroundings because it's still addressed, not because the design wants to underline it. Everything else on the print stays exactly as unreadable as memory actually is, which is what lets the two legible words carry weight without a caption — the same restraint that keeps a corrupted-image print from over-explaining its own break rather than captioning the glitch. A version that framed the fragment or wrote a sentence explaining who sent it would be doing the reader's work for them.

Does referencing a recovered message like this involve anyone's real data?

No, and it shouldn't — inventing the fragment is the whole point.

A print built around an actual leaked breach, a specific named victim, or a real recovered message would be telling someone else's story without their permission, which is a different kind of decision than this one. The format — rows of hex, one line resolving into text — is generic technical convention with no owner. What would need sourcing is a real incident. An invented fragment needs nobody's permission, including the person it's addressed to.

Does the same idea work with a different fragment surfacing?

Yes — the mechanism doesn't care what the words are, only that they're short enough to read at a glance and specific enough to mean something.

A name. A date. A single coordinate. What changes the read entirely is length — three or four words is a fragment; a full sentence surfacing out of noise stops looking like residue and starts looking like a message somebody composed on purpose, which undoes the accident the whole design depends on. Even a transcript from a device built purely to translate speech sometimes keeps a fragment the software wasn't asked to render — the same gap between processed and human, in a different format.

Isn't a wall of mostly unreadable characters a strange thing to print?

No — the design isn't meant to be read in full, it's meant to be scanned.

Nobody scanning a hex dump parses every byte pair — the eye travels across a dense, even field and stops on the one place the pattern breaks. That's how a memory dump actually gets read by someone looking for something in it: not line by line, but scanning for the anomaly. The print asks the same thing of a viewer that the job asks of the person doing it at three in the morning.

Does it print well?

Yes, provided the density stays even and the bright run stays the only bright thing on the shirt.

Pale green on near-black is close to how a CRT actually renders, and keeping every other character the same faded tone is what makes the one legible run pop without extra effort. Fixed-width type is non-negotiable here — hexadecimal in a proportional font stops reading as data. One ink for the bulk of the dump and a second, brighter version of the same green for the surfaced line is enough; a third colour would turn a memory dump back into a poster.

How do I get one made?

Describe the fragment at JustOG — what surfaces, how much fades around it, and where on the garment it sits. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped.

Designs other people have published are in the shop.

Two words at full strength, and several thousand byte pairs the system never got around to erasing.