Hacker News new | past | comments | ask | show | jobs | submit login
The Church of BSD (2005) (unixprogram.com)
34 points by stargrave on Jan 6, 2018 | hide | past | web | favorite | 10 comments

To use (whatever is your provider, often Google's) cache, just replace the protocol with "cache" like this:


Or use the Internet Archive / WayBackMachine (from 5.1.): https://web.archive.org/web/20180105140154/http://www.unixpr...

This is a massive misconstruement.

There's no "cache://" "protocol". This is simply Google's search query parser being extremely forgiving with "cache://" vs "cache:", which is the correct syntax (as documented on various sites on the internet).

When you type "cache:" or "cache://" into Chrome (FF not tested) you'll see the top result it's about to execute is a search. It just sends the string to google.com.

If you go to google.com manually and input "cache:www.example.com" as the search query, you won't get a results page, you'll go directly to the cached page.

Hmm, how does this work? Is it a browser thing, or ISP providing this?

It redirects from a google search.

I put 2005 on this because of https://web.archive.org/web/20050205225509/http://www.unixpr..., but it feels like it might be earlier. Anybody know?


That's the date of an email quoted in the text, so it's really just a lower bound on the article year, no?

That's what Google says, which I thought was based on a "clever look" at Last-Modified or explicit dates in the article. However, the articles mentions Windows XP, which I think wasn't known until 2001. So Google might have just picked the only parseable date from the page.

Edit: After about 5 minutes curl answered: Last-Modified: Mon, 27 Dec 2010 20:40:54 GMT (which is unsurprising given the web.archive.org info showing amends of the page)

Wow. How did you determine this?

aaaand it's down

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact