There’s an old problem with permalinks: they have a tendency to end up not being permanent. You keep a record of articles (bookmarks/favourites) that you know you’ll want to refer back to later. When it comes time to actually use them, the links are broken for whatever reason and you’re left staring at a 404 screen. Not fun.
It’s happened to me once too many times, so I’m going to try to solve the problem for at least my site. My thinking is that servers are outwith the control of most people, even the owner of the site living on the server, thus making it the weakest link in the distribution chain. So, how do we remove reliance on servers to recall information?
The best answer is immediate addressing in the form of Data: URL’s. For those who’ve never seen a data:url, it’s a way to store information (images, text, or pretty much anything else) as a link; that is, the link is the data, not just a pointer to it. It’s a great concept being used in various ways (not least as a way of beating DVD encryption).
When permalinks meet data:urls, we have a way of storing entries as links. That is, we have bookmarks that will never break.
Of course, this is not without it’s problems:
If you want to play with data: urls yourself, there are some good resources. Ian Hickson’s data: URI kitchen is the best place to generate them for experimentation. Or, if you’re feeling really fruity, there is Simon Willison’s self-contained data: URI kitchen; a reinvention of Ian’s kitchen as a data: uri (confusing yes, useless no).
Thanks to Ian Hickson for providing the numbers on URL lengths, and to Simon Willison for reworking the original kitchen and inadvertantly giving me a kick to get this done.
Posted: August 14th, 2003
#Permalink: Permalinks And Data, By Gary Fleming