Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility on Web Archive #638

zarybnicky opened this issue Jun 19, 2018 · 1 comment


2 participants
Copy link

commented Jun 19, 2018

I wasn't very successful trying to use the new LW's Web Archive (

Trying in Chrome - at first, I get a ERR_SPDY_PROTOCOL_ERROR, then what seems like a fallback site kicks in. That looks so-so as it's first loading - some content is shown, even some images - but as the site finishes loading, everything but the title bar disappears.

The content I was trying to access was still accessible via the old LW's web archive, but I expect that sometime in the future, somebody's going to be very disappointed that the content of the new LW is not available there - unless you're gwern and you're archiving everything locally...


This comment has been minimized.

Copy link

commented May 8, 2019

In LessWrong2/Vulcan#61 we tried out a fix based on comparing the expected and actual URLs. The idea wasthat we would abort Javascript (leaving SSR) if they don't match, but first, we put in some instrumentation to find out whether mismatches do in fact happen.

Unfortunately, our instrumentation is seeing a bunch of mismatches. Some of them do match the case we want to handle (eg file:// URLs), but some of them are just random pairs of pages on the site. Sometimes they're pairs of pages that aren't connected by any single click.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.