Conversation

This is one of the MAJOR failings of the web, that urls are not persistent, and most web admins do not bother to setup redirects to the new location when things change.
Quote Tweet
Google for all it's CI/CD work can't even have tooling to verify that the URLs in it's own documentation aren't 404. Or even put in a redirect to the correct when an old url disappears.
Show this thread
2
11
Replying to
We take great take to do this for the GrapheneOS sites but there are serious browser limitations. We had to make github.com/GrapheneOS/gra to handle section redirects. It's a missing HTML feature. We link to a proposal which would have been a nicer way to handle these redirects.
2
2
Replying to
I'm a little more forgiving of fragments not working as long as it takes me to the correct page, but as I see with grapheneos, you moved data off a page, and so fragment detection was necessary.
1
1
Replying to and
For example, content may get moved between the features overview, usage guide and FAQ pages. It's also likely the FAQ and usage guide will end up needing to have portions split out into other pages since they're going to keep growing and some content may deserve a dedicated page.
1
2
Replying to and
This also happens a lot on Wikipedia as another example. Sections are renamed and moved between pages. Those anchor links end up breaking and you often get sent to a page where the content isn't present anymore or has been completely redone / renamed so it's hard to find it.
2