I propose we design a markup language so this can be parsed. How about DTML? And maybe some styling rules as well, we can call it DSS. And we can't forget a basic scripting language called DJS.
I'll start working on the parser, we can call it a drowser.
I think plain text is OK. There is also Markdown, MediaWiki format, etc, although a simple readable format is best, so that includes plain text (and possibly Markdown too).
And even if another format is made, we should avoid the mistakes of HTML, such as scripting and styling and some other stuff.
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.
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".
dns.wpodns.adtac.in. 3600 IN TXT "The Domain Name System (DNS) is a hierarchical and decentralized naming system for computers, services, or other resources..."
But! That solution made http requests (obviously), however you can in theory replace its queries with the thing in the current post and have true DNS-over-Wikipedia via the DNS protocol.
I wouldn't say it's the opposite. It sounds the opposite from the title, but this actually returns Wikipedia content. The other one fetches a link to a site.
"A globally-distributed, eventually-consistent, 100% available key-value store ;)" (I haven't actually tried running this code personally): https://github.com/craftyphotons/ten34
Unrelated comment: I like this sort of web design. Might just be nostalgia. It reminds me of web design circa 2001 or so. You can see many similar examples on OSWD, e.g.:
Large single record seems to work fine testing from BIND via Windows nslookup as long as you obey the 255 character per line rule i.e. split strings "like" "this" at least every 255 characters.
That’s really cool ! A security teacher told me a long time ago about these possibilities and I love the concept, I love Wikipedia and I love plain text, so thanks a lot for this !
Those countries would just block adtac.in recursively when they noticed.
And if you decide to work around that by setting up more domains to do this, then you could just as well use those domains to front regular proxy servers.
I propose we design a markup language so this can be parsed. How about DTML? And maybe some styling rules as well, we can call it DSS. And we can't forget a basic scripting language called DJS.
I'll start working on the parser, we can call it a drowser.