@alex I just realized I had never seen https://emacswiki.org down until now, a testament to the robustness of your setup and the size of the hit you (and everybody else like @corbet) are taking now.
Question: long-term, is there a "CDN" solution to this? Decentralized, like all content are #MagnetURI - the Bittorrent seeder rations bandwidth by design, and genuine clients of a popular website end up getting it via peers.
@alex @corbet actually, the way to sneak in #BiTorrent / #IPFS into the #WebBrowser would have to be via ... file:// URI's! Accessing file:///disk/magnet/hash_of_webpage would load the webpage and recursively any such links inside ... because file:///disk would be an Android DocumentsProvider for #MagnetURI (exists?) or a Linux BTfs mount (exists). Give https visitors a link to the file:// magnet URI.
@alex @corbet now they put PKI and #DNS into the #Bittorrent DHT.
A useful way to point to a website seems to be DID-DHT, based on https://pkarr.org
As I understand, you put your public key on the DHT and use it to sign a DNS record and put it on the Bittorrent DHT. I imagine anybody with your public key will be able to get your authentic DNS record via Bittorrent. You just keep updating the DNS record with the current location of the website.
But that location could be a magnet: URN!
Public Key Addressable Resource Records (sovereign TLDs) - pubky/pkarr
GitHub