7 ms·

A while back I showed how you could drop data into a server log file, and jokingly called it CurlyTP. I have thought many times about embedding a website direct

A while back I showed how you could drop data into a server log file, and jokingly called it CurlyTP. I have thought many times about embedding a website directly into DNS. https://miscdotgeek.com/curlytp-every-web-server-is-a-dead-drop/ https://miscdotgeek.com/curlytp-every-web-server-is-a-dead-d... Anybody up for the challenge? With some scripting you could do a dig on a TXT record, parse it, and display it right in a web page.

3xblah 7y ago
For some reasons I always had the idea of using HTTP headers and server logs to pass data. It can, e.g., be an alternative way of passing request/query input to a server, instead of using URLs or HTML forms. The server can read filtered input from a log file stored on RAM disk. I did the TXT record as HTML idea many years ago by modifying djb's dnstxt to output valid HTTP header. The idea was to use tinydns and dnscache as a "back-end" database to store millions of tiny "webpages". A true Rube Golberg machine.