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, 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.
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.
(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.
very cool, i did something similar but turning the doom frame running on a server into ascii (with colour) and then a small shim to give inputs via subdomains
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.
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, 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?
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.
Yup. A better title might be “Author discovers data can be stored in DNS TXT records which were created to store data.”
Also we could probably achieve this by using dnsfs and regular doom install
https://blog.benjojo.co.uk/post/dns-filesystem-true-cloud-st...
You make me wonder if it is possible. All you need to do is to programmatically change bits, and you have compute. Some cache monkeying or somethong.
Of course, I imagine it would be incredibly slow.
> All you need to do is to programmatically change bits, and you have compute.
all you need is to rapidly push off one foot and land on the other, and you have running.
This novel form of data storage reminds of me of this classic YouTube video, Harder Drive: https://www.youtube.com/watch?v=JcJSW7Rprio
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.
Waiting for Doom over https://github.com/yarrick/pingfs next
very cool, i did something similar but turning the doom frame running on a server into ascii (with colour) and then a small shim to give inputs via subdomains
https://www.youtube.com/watch?v=GoPWuJR6Npc
without the colour i did it in a worse way for bad apple
https://www.youtube.com/watch?v=AJ2Q12vYojY
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.
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.
You were right to assume that in this case. DNS is not running doom here, it's just storing it.
Which is more ambitious, targeting the MONIAC platform or ENIAC?
https://en.wikipedia.org/wiki/ENIAC
https://en.wikipedia.org/wiki/Phillips_Machine (MONIAC)
I'd say both are looking increasingly doable.
“Run” is doing a lot of heavy lifting at this point.
I remember the pregnancy test Doom. Wasn't it "running" on the display only?
Coming up: playing doom on Ping-as-Storage
Malware could still use DNS records for storage and access to bootstrapped payloads correct?
Yes, but it's not a problem, any more than downloading any arbitrary text is. You'd still have to have something execute the binary.
A database storing data? Now I’ve seen everything!
Finally, a DOOM download that bypasses captive portals
Super cool. Never thought of this. Would this be useful for seeding LLMs?
This is a data storage system, so I guess yes, data is useful to train LLMs?
Why does everything get turned into an LLM discussion?