Dianc0536.jpg <Direct Link>
Elias checked the metadata. The "Date Taken" field was empty, but the "Modified" date was listed as . He froze. It was currently 2026.
Elias was a digital archivist, a man who spent his days cataloging the detritus of the early internet. His job was to sort through "dead" hard drives recovered from defunct government offices and estate sales. Most of it was mundane: tax spreadsheets from 1994, blurry vacation photos, and corrupted system files. Then he found the drive labeled Project Dianthus .
As the second hand ticked forward, a blinding flash erupted from the camera at the end of the hall. For a split second, Elias felt himself being pulled through a straw—his atoms stretching into lines of code, his memories flattening into pixels. dianc0536.jpg
Over the next few days, Elias became obsessed. He ran the image through enhancement software, trying to sharpen the figure at the end of the hall. With every pass, the software didn't just clear the blur; it seemed to add detail that wasn't there before. The figure was wearing a coat exactly like the one hanging in Elias’s hallway. The watch on the figure’s wrist had a cracked face—the same crack Elias had made on his own watch just that morning.
Back in the apartment, the computer screen finally turned off. On the hard drive, a new file appeared in the folder: . Elias checked the metadata
It was a high-resolution photo of an empty hallway, perfectly still, waiting for the next person to click. AI responses may include mistakes. Learn more
Elias realized then that "dianc" wasn't a random string of letters. It was a truncated code: Digital Interference and Neural Capture . And the number wasn't a sequence. It was a time. He looked at his cracked watch. It was 5:35 AM. It was currently 2026
When he first clicked it, his monitor flickered. The image that appeared was a low-resolution shot of a hallway. It looked like a hospital, but the lighting was a sickly, bruised purple. At the end of the hall stood a figure that was slightly out of focus, as if the camera had struggled to lock onto its dimensions.
That’s a brilliant tip and the example video.. Never considered doing this for some reason — makes so much sense though.
So often content is provided with pseudo HTML often created by MS Word.. nice to have a way to remove the same spammy tags it always generates.
Good tip on the multiple search and replace, but in a case like this, it’s kinda overkill… instead of replacing
<p>and</p>you could also just replace</?p>.You could even expand that to get all
ptags, even with attributes, using</?p[^>]*>.Simples :-)
Cool! Regex to the rescue.
My main use-case has about 15 find-replaces for all kinds of various stuff, so it might be a little outside the scope of a single regex.
Yeah, I could totally see a command like
remove cruftdoing a bunch of these little replaces. RegEx could absolutely do it, but it would get a bit unwieldy.</?(p|blockquote|span)[^>]*>What sublime theme are you using Chris? Its so clean and simple!
I’m curious about that too!
Looks like he’s using the same one I am: Material Theme
https://github.com/equinusocio/material-theme
Thanks Joe!
Question, in your code, I understand the need for ‘find’, ‘replace’ and ‘case’. What does greedy do? Is that a designation to do all?
What is the theme used in the first image (package install) and last image (run new command)?
There is a small error in your JSON code example.
A closing bracket at the end of the code is missing.
There is a cool plugin for Sublime Text https://github.com/titoBouzout/Tag that can strip tags or attributes from file. Saved me a lot of time on multiple occasions. Can’t recommend it enough. Especially if you don’t want to mess with regular expressions.