It Spreads

I didn’t really pay attention when it first happened, but reading the full story later made me understand how much of a thing it actually was.

A blogger published the encryption code for HD-DVDs. One post, one string of characters. And it spread everywhere—Digg, forums, blogs, over and over. Every time someone removed it, three more people posted it again. It became this weird loop of upload, takedown, reupload, takedown, except the reupload always happened faster.

The code itself wasn’t even special. It was already cracked. The encryption was already broken. But the moment someone just published it plainly, like any other information, the whole dynamic changed. Because you can’t unpublish a number. You can delete a post, but the number still exists. You can send lawyers after the blog, and the number exists in fifty other places. It’s just mathematics sitting there waiting to be copied.

I kept thinking about the companies involved—all that legal force, all those resources, completely helpless against replication. You can’t issue a takedown on an idea. You can try. They did try. But the infrastructure doesn’t work that way. Copy a number, send it to someone, they copy it, send it somewhere else. No permission needed, no verification, just spread.

The thing’s already faded now, the Digg wars are over, the code’s out there somewhere or it isn’t. But for a few days there was this moment where the whole thing just felt transparent in a way it usually doesn’t. Like you could see exactly how little the formal structures actually matter when people stop respecting them.