Making KevHQ Available Everywhere - Part 1.

Been playing with this silly little site again. I had an idea for a series of posts. Something like “Making KevHQ Available Everywhere” or “How to make a website indestructible”. Name TBD.

The idea is simple. Take this site that doesn’t need any of this and turn it into something that can survive cloud provider outages, DNS bans, government pressure and possibly the end of the internet. Why? Nerd points. The road map looks something like:

  1. Dual cloud setup Run the site across 2 CDNs so it could tolerate failure of one cloud provider in theory. If one provider goes down, traffic auto shifts to the other. This will also include moving my DNS provider and moving traffic from the apex domain to www

  2. Privacy friendly mirrors.
    Setup Tor (and maybe I2P?) so it is available to the privacy conscious crowd. This will also mean self hosting all assets my site uses. This is mostly done except for OpenStreetMap tiles used in winging it on wheels. This is important so that those calls don’t deanonymize folks’ traffic.

  3. IPFS (InterPlanetary File System)
    Publish to IPFS. This way the site survives

    • Both clouds being offline
    • My DNS provider kicking me off
    • Even the pesky speed of light delays when Elon sets up shop on Mars.

  4. DNS + Identity

    • DNS is still a single point of failure. So I’ll set up a second domain under a different top-level domain with another DNS provider and pre-wire it. If the primary is ever nuked, I can publish the backup domain immediately. Maybe publish my own /etc/hosts file entry and distribute over git to bypass ICANN altogether… I did say this was over the top.
    • Issuing redundant TLS certs from 2 CAs so if one gets angry with me, I still have the little green lock.

  5. Archival + immutable history.
    Periodically and proactively push to the Internet Archive

  6. P2P Protocols
    To survive ISP level nuking. Torrent seeds, Nostr, plus whatever else fits

  7. Indie/retro protocols
    The web != internet. So setup some of the Indie, retro and old school internet protocols like Gopher and Gemini because why not?

  8. Independent origins. Self host in home lab.
    The dual CDN idea would still have both CDNs serve from S3. The next step is to self host the source files on Cloudflare’s R2 plus my own home server as a backup/failover.

  9. Bonus: PWA
    Already done but worth mentioning. If you are on a Chromium-based browser, you should see a little “Install” button on the top right. This gives some level of “Offline Mode” provided you have visited this site before. In future expand the offline.html to explain other ways to reach the site (alt domain, onion, IPFS).

So that is the goal, to become hilariously hard to kill. Yes, all of this is pretty damn pointless and totally over the top but I’m going for max nerd points. Short of full nuclear war, you should be able to reach this silly little personal site.

The next post will be about the Dual CDN setup. Vamos.