Friday, March 11, 2011

Inferring that coincidence may indeed be causality

Google's latest Chrome 10 browser apparently can ask the mothership whether my sluggish response from the server is related to a possible problem on the server side.

This morning I received the following error message while pressing "reload":

Oops! Google Chrome could not connect to

Other users are also experiencing difficulties connecting to this site, so you may have to wait a few minutes.

The Google knoweth all (or at least more than you might think!) ...

1 comment: