This is quite weird, I was never able to access it with TBB nor with any proxy without the cloudflare captcha page popping in.
The Wayback Machine requires your browser to support JavaScript, please email info@archive.org if you have any questions about this.
From what I understand, the date selector (/web/*/...) seems to require JS now, although I haven't tested JS turned off.
(Also - if I can ask/clarify a couple things I've been curious about for a while: based on released info, I get the idea that the Lua part of the WAF is mostly regexes and "precompiled"/predetermined-ahead-of-time-based-on-past-incidents "possible issue" flagging, and a bunch of Go code (which I theorize runs slightly behind realtime, but not too far) follows up on those flags and makes the actual executive decisions about blocking/tracking/dropping/etc the Lua-generated event. I've also learned (from solving an ISP glitch with the guy who coincidentally manages the WAF!) that your copy of Lua is a bit special (although I don't know specifically how). I just wanted to let you know that there are people out there very interested to learn more about the "boring" (non-proprietary) parts of the CF stack. "Go/no-go within 999 nanoseconds" is amazing, I'd love to learn more about it. It's a cool platform.)
There's nothing special about 'our copy of Lua'; we use LuaJIT and all changes we've made have been contributed back.
Have you seen the talk I have on this? https://www.youtube.com/watch?v=nlt4XKhucS4