3 ms·

"Cool URIs Don't Change" was always such a pretentious page to begin with. No, just because I hosted something for awhile does not mean I am obligated to host

"Cool URIs Don't Change" was always such a pretentious page to begin with. 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.

emaro 3y ago
Of course not. But it's cool if you choose to do so.
- nickelpro 3y ago
  Nah, it craps all over site operators for their lack of "forethought". 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.
  - spoiler 3y ago
    Supporting redirects can be simple, depending on your SSG (and it's possible to make extensions to most of them, so this could be something that responds to a posts frontmatter). It could just generare an html file with this <meta http-equiv="refresh" …> sent in the head, and some html/css to make it pretty. It's not ideal, but I assume search engines support it (dunno if there's any additional SEO improvements).
  - account42 3y ago
    > the unending burden of maintaining redirects forever 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.
  - scottlamb 3y ago
    > Should have known the company was going to move to Markdown static site generation five years before Markdown was invented. 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.
project2501a 3y ago
Correct. But you can always be kind and use a 302 to redirect to the URI you are currently using... speaking of... wonder if there are any 302 redirect managing software...
- sph 3y ago
  If you do not mind the self-promotion, I am building a links checker service that also monitors all your website's links, so if you forget to set up a redirect after moving and renaming some pages, you get a notification. 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 https://bernard.app
Aachen 3y ago
The point is not "host this into eternity" but "so long as you host it, keep the URL pointing to this resource stable"
- nickelpro 3y ago
  Nope, unless you're bankrupt you're supposed to host forever: > 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.
Uehreka 3y ago
> 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. I mean sure but… be cooler if you did
deleted 3y ago
[deleted]

emaro 3y ago

Of course not. But it's cool if you choose to do so.

nickelpro 3y ago
Nah, it craps all over site operators for their lack of "forethought". 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.
- spoiler 3y ago
  Supporting redirects can be simple, depending on your SSG (and it's possible to make extensions to most of them, so this could be something that responds to a posts frontmatter). It could just generare an html file with this <meta http-equiv="refresh" …> sent in the head, and some html/css to make it pretty. It's not ideal, but I assume search engines support it (dunno if there's any additional SEO improvements).
- account42 3y ago
  > the unending burden of maintaining redirects forever 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.
- scottlamb 3y ago
  > Should have known the company was going to move to Markdown static site generation five years before Markdown was invented. 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.

project2501a 3y ago

Correct. But you can always be kind and use a 302 to redirect to the URI you are currently using... speaking of... wonder if there are any 302 redirect managing software...

sph 3y ago
If you do not mind the self-promotion, I am building a links checker service that also monitors all your website's links, so if you forget to set up a redirect after moving and renaming some pages, you get a notification. 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 https://bernard.app

Aachen 3y ago

The point is not "host this into eternity" but "so long as you host it, keep the URL pointing to this resource stable"

nickelpro 3y ago
Nope, unless you're bankrupt you're supposed to host forever: > 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.

Uehreka 3y ago

> 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. I mean sure but… be cooler if you did

deleted 3y ago

[deleted]