Platforms change but cool URIs don't
lethain.com
lethain.com
Podcasts are starting to get centralised, like how Spotify bought out Anchor.
The alternative of hosting ones own podcast doesn't seem easy, nor seems cheap. I explored that idea for a big with my own podcast, The Language of My Soul, but it ain't worth it.
The site with links to my site now consists of a placeholder page with a link to the Internet Archive. As much as I like stable URLs, I think that I would like to encourage people to just keep as much online as possible, and if you keep your content online, that’s commendable. It’s worthy of praise just staying online.
URIs used to be like phone numbers, in that they were designed for humans — today, they're designed for SEO. But today, nobody memorizes phone numbers — people depend on their phone's Contacts app. Similarly, nobody remembers URIs beyond the domain name — they depend on bookmarks, browser history auto-complete, app-specific search functionality, and search engines.
Podcast feed URIs change all the time (old feed URIs redirect to new) and zero people know or care. I believe the same is generally true for web pages.
Playing devil's advocate to myself, AFAIK no browser automatically updates bookmarks even in the face of permanent redirects. They should, right?
Accumulating links to and from your content over the course of many years isn't just valuable because of SEO, it's valuable because you're helping to build a legacy of interlinked content. And that's a cool thing to contribute to!
This seems to support my point so I must be misunderstanding it. If a link continues to work because of a redirect, who cares if the URI changes?
Sure, for a permanent architecture where we are putting information on the web to slowly accumulate human knowledge, it is a great idea. It dissolves like wedding cake decorations in a church fire under the power of Marketing.
It would not make sense if a bookmark could randomly change.
Ah, my preference is the opposite — if I have to constantly babysit bookmarks for 301 redirects, that's technically correct but fails the "job to be done" of it.
Set up custom redirectors not dependent on the platform using the Web server