DNS-data-hiding
Storing a large amount of data (e.g., a picture or documente or video) by breaking it into
small packets (4 to 1000 bytes) and "storing" it in DNS servers around the world by sending
out DNS address updates. Eventual recipient recovers the data by making requests of
sequential DNS addresses. E.g., pick an unused C class subnet, and store 4 bytes per
possible IP address within it. Do a dnslookup for packet000001.stored_by_dns.com to get the first
4 bytes (the ostensible "IP address"), then one for packet000002.stored_by_dns.com to get the
next 4 bytes, etc. Not a solution for long-term hiding of data, but should work for a short term.
(An obvious predecessor to this is the idea of storing data in a newsgroup, by posting encoded data
with a unique tag; predecessor to that is the idea of emailing files to oneself, relying on an external
server to store them until "read".) Both are probably inspired by the concept of beaming data
via a laser to a reflector on the moon, and re-beaming it upon receiving it back at the earth ...
which in turn is probably inspired by mercury delay line memory units from about 1945.