davidbgk
/
larlet-fr-david-cache
Watch 1
Star 0
Fork 0
Code Releases 0 Activity
A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
42 Commits
1 Branch
Tree: 2e4d51a7b7
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '2e4d51a7b7'
${ noResults }
larlet-fr-david-cache/cache/64f6381f9270b8b6c8eb1208336.../index.md

index.md 3.0KB
Raw Blame History

title: Why? url: https://4042302.org/why/ hash_url: 64f6381f92

My first web site was hosted on Geocities.

Then Tripod.

Then it was a full Flash site that I coded from scratch.

Then it used b2.

Then it used Wordpress.

Now it’s my own hand-rolled static site generator in Node.js.

Soon, it’ll be my own Indienet site.

The Geocities site lives on only thanks to the Internet Achieve (thanks Brewster) as does the Tripod page. I’m glad they’re still there (so embarrassing, but we all had to start somewhere!) But the original URLs today are broken. I couldn’t do anything about that because, just like my Facebook or Twitter profile today, they were never mine. I was just renting them from those companies and, when they went away, they took that part of the Web with them. My own site (and my Mastodon), on the other hand, are mine and, among other things, I get to decide if they live or die.

Once I had my own domain, I was able to be more thoughtful.

I didn’t want to break the Web when I went from b2 to Wordpress. But that took some work. I had to write a b2 to Wordpress migration script.

Then, when I went from Wordpress to my own hand-rolled static site generator, I had to again write code to process my legacy content and make sure I maintained the URLs. That took some work also. It wasn’t trivial.

(And, when I changed my domain from aralbalkan.com to ar.al, I had to keep a web server running at aralbalkan.com to forward the HTTPS calls to the new domain.)

Soon, my personal site will change completely as it becomes a federated personal site. So it’s going to go from a static web site to a Node.js application. I don’t want to break the Web but I also don’t want to burden the new system I’m building with a means to handle legacy static content. And yet, this is also an important use case that I cannot ignore.

So what’s a developer to do?

Here’s the simplest solution I could come up with:

  1. Serve the current site from a subdomain (e.g., 2017.ar.al)

  2. Make my 404s into 302s that point to the previous version of the site.

  3. If I change the site again in the future, rinse and repeat.

I call the technique 404 to 302.