Conversation

John-Mark Gurney 🗑️🔥
@encthenet
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
John-Mark Gurney 🗑️🔥
@encthenet
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
Daniel Micay
@DanielMicay
Replying to
@encthenet
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.
github.com
grapheneos.org/redirect.js at main · GrapheneOS/grapheneos.org
Main website servers. Contribute to GrapheneOS/grapheneos.org development by creating an account on GitHub.
2
2
John-Mark Gurney 🗑️🔥
@encthenet
Replying to
@DanielMicay
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
Daniel Micay
@DanielMicay
Replying to
@encthenet
If it's moved within the same page, it's possible to create additional elements to provide legacy anchors but we don't really want to add a bunch of those and it doesn't address moving content across pages. It's going to be very common for us to move sections between pages.
1
2
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
and
@encthenet
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