At some point I hosted my blog in DNS; it was a bunch of chunks in TXT records which the frontend would reassemble. It had really strange side effects, e.g. editing a post could shuffle the chunks but then they'd end up being cached separately and some people would see weird artefacts in the text.
The various "VPN/IP over DNS" solutions miss a typical, more performance variant: VPN over UDP/53. Because DNS is frequently not filtered in badly locked down hotspots.
A shameless plug for my own project where the DNS infrastructure plays a key role. The idea is to make a chain of TXT records where anyone with a domain name can join the chain my adding a TXT record pointing to the parent domain. https://recordrelay.net
Makes it even more important to put on a more unique design. Not fancy, just not the most default design any coding AI would create. I am sure many people instantly click away when they see that as well.
I've been trying to find a list I had previously of sites hosting webpages at top-level domains. I think there was a webpage you could access at http://ai./ for a long time.
20 comments
[ 2.6 ms ] story [ 16.8 ms ] threadI don't know why I did that, but it was fun!
https://ianix.com/pub/dnssec-outages.html
(I know pgl has been collecting DNS weirdnesses for years - that bit definitely hasn't been AI-generated.)