No, just because I hosted something for awhile does not mean I am obligated to host that resource in the exact same way for eternity. There is no contract, implicit, social, or otherwise that I will continue to provide that free thing for you in a way that is convenient to you personally in perpetuity.
Oh, you didn't perfectly lay out your URIs in the initial design? Too bad, you're saddled with the unending burden of maintaining redirects forever or you're not "cool". Should have known the company was going to move to Markdown static site generation five years before Markdown was invented.
Miss me with that shit. Link rot is the burden of the link author, not the target.
<meta http-equiv="refresh" …>
Right because keeping a list of source->destination and configuring your current server based on that is such a burden...
> Miss me with that shit. Link rot is the burden of the link author, not the target.
The link author isn't the one making the changes, the target is. The link author might not even be alive anymore. Expecting others to untangle your mess is ... not cool.
Okay, but you did know, right? Maybe not that the new thing would be called Markdown or exactly when but that there would be a new thing. The W3C sure knew and told you. That's why they wrote e.g. this paragraph:
> Software mechanisms. Look for "cgi", "exec" and other give-away "look what software we are using" bits in URIs. Anyone want to commit to using perl cgi scripts all their lives? Nope? Cut out the .pl. Read the server manual on how to do it.
> Pretty much the only good reason for a document to disappear from the Web is that the company which owned the domain name went out of business or can no longer afford to keep the server running.
speaking of... wonder if there are any 302 redirect managing software...
Mind you, this feature is still under development, but this is the ultimate goal of my app.
It is currently in free beta if you are interested in giving it a go: https://bernard.app
I mean sure but… be cooler if you did