40 comments

[ 3.4 ms ] story [ 45.7 ms ] thread
Gotta admit that it didn't occur to me that "can it run DOOM?" would stretch all the way to DNS.

At this point I am wondering if people will somehow port DOOM over to the MONIAC.

To clarify, a good title would be "Loading Doom entirely from DNS records"

Neither one plays Doom over DNS nor is the first paragraph in the README correct, because DNS is only abused for storage, not for computing/processing/executing instructions:

> At some point, a reasonable person asked "DNS resolves names to IP addresses, what else can it do?" The answer, apparently, is run DOOM.

Well, there are DNS tunneling projects, so I would suspect you could displace the network support in DOOM with a DNS based protocol.
Super cool. Never thought of this. Would this be useful for seeding LLMs?
(comment deleted)
I never stop being impressed by these "<something-crazy> running Doom" posts. AFAIC, whenever we get to Mars, we won't truly have arrived until someone is playing Doom on Mars, and without wasting valuable resources by doing so. Running Doom, the canonical measurement of truly mastering a thing's capabilities.
(comment deleted)
Finally, a DOOM download that bypasses captive portals
A database storing data? Now I’ve seen everything!
Malware could still use DNS records for storage and access to bootstrapped payloads correct?
Respect. But also ... WHY????

Now let's do

(1) A DNS file drop: Split small files into TXT records and rebuild them client-side. Useless for big files, perfect for config blobs, tiny payloads, and cursed demos. Also someone can write an S3-compatible client.

(2) Redis DNS:

- GET foo.cache.example.com -> TXT record returns value chunks

- TTL is the eviction policy

- Cache invalidation becomes even more of a hate crime.

I once had this silly idea to create distributed storage of arbitrary data by exploiting a range of completely unrelated sites. Say, when you want to upload your file to the System, it may store one encrypted chunk as an image on a free image hosting site, another chunk as an encoded blog post on a random forum about farming (or in the user profile?), another chunk as a youtube video, etc. Imagine having something like hundreds or thousands of such "backends". Every chunk would be stored in 3 places for high durability of course. Free storage, hidden in plain sight :) Although, I didn't think through how to store the index reliably, and, because a moderator on a random farmers' site may delete our record(s), there needs to be a system which continously validates the integrity and reuploads the chunks.

Maybe such a silly project already exists?

I read this title, did a double-take, then had to go look at the git hub because it still didn't click for me. Because this sounds absolutely amazing, and absurd, and weird, all at the same time. Like..... Wow? Talk about turning protocols into pretzels...
Tangent, harder drives by suckerpinch
blech...too much windows. bring me the Linux version and i might care ;)
thank you for doing god’s work my friend.
thanks for doing god’s work my friend.
> Cloudflare will serve them globally, for free, cached at the edge, to anyone who asks. They are not a file storage system. They were not designed to be a file storage system. Nobody at the IETF was thinking about them being used as a file storage system when they wrote RFC 1035. And yet here we are.

Yeah these types of hacker stories kind of bug me. They are sort of in the same vein as "you can eat for free by going to McDonald's and eating a pint of ketchup without ordering anything" or "How I drank and showered for a year using public water fountains" . Or put another way "just because you can doesn't mean you should". Trustless societies kind of suck and forcing society to lower trust by abusing trust kind of makes things incrementally suckier ("trust" here being "it's on the honor system to not abuse DNS to serve static content").

You're taking this too seriously.

It's useful (and interesting) to think about ways that the implementation of functional specifications can be 'hacked' to do something different.

Also; acknowledging and understanding the potential for such aberrations, means we can look out for abuse in the future.

What is the serialization format? Base64?
Another fake Doom run, like the predictor one. This doesn't actually run Doom. Sorry. Meanwhile, other esoteric platforms actually runthe software.

There's the Infocom ZMachine with Zork I-III, Tristam Island, Calypso (Z machine v3 games) and many more which can be run starting from a PostScript file to a pen, a simple FPGA machine, an Amiga, the original Game Boy and who knows what.

If you can port a libre interpreter, you can run it. Old PDA's, Smartphones, JS browsers, Windows 95 machines with Winfrotz, DOS, Raspberry Pies with GNU/Linux, Riscos... There are emulators even written in Perl, Python, Lua, tons of them. It's text based output and the Z machine format it's documented.

I think some Activision games had the the Zork game embedded on their engine as an Easter Egg. As it's an 'easy' task for any programmer embedding it under a fake ingame computer woudn't have been a daunting task.

Maybe I can adapt the PostScript one to Eforth under the Subleq VM, PS' syntax maps slightly ok to EForth...

With Asterisks and some old modules you can even play it over a VOIP client and listen to the output with Flite/Festival/Espeak-nG or any compatible TTS software, such as PicoTTS. The voice input it's done with CMU Sphinx.

Something Doom can't do at all.