3 ms·

> From the year 2000, 42 ways to distribute arbitrary data over the internet, including DNS This is very cool, thanks for the link. Would be interested to hea

• 1vuio0pswjnm7 6y ago
  People have now wrapped DNS RR in TLS, then in HTTP and they are thinking about putting DNS RR into HTTP headers or into HTML tags. https://www.potaroo.net/ispcol/2020-06/row.html https://www.potaroo.net/ispcol/2020-06/row.html In the late 2000's I took the oppsoite approach, because back then, DNS, i.e., traditional 512K UDP packets, was much faster for data retrieval than TCP/SSL/HTTP. TLS has gotten quite fast but using UDP is still faster, that's why we see UDP-based "reliable transport" protocols like (lesser known) CurveCP and (better known) QUIC. I put the content into the DNS RR instead of putting the DNS RR, e.g., IP address, into the content. Retrieving content, e.g., a web page, has become a two-step process, thanks to DNS. It could be a one step process if we used IP addresses instead of names; I still do this where possible. However to use names, first we have to get the IP address (step 1), and only then can we retrieve the content (step 2). If we combine the IP address with the content then we can eliminate a step. Putting everything into DNS instead of into web pages gives more control to the user, IMO. Web browsers are controlled by companies that rely on the survival of the online ad industry. DNS software does not have this problem.
  • 1vuio0pswjnm7 6y ago
    s/512K/512/