Day 131 - October 24 - Where'd who go?

Many of our keen-eyed observers traveling with us on ConnorWatch noticed that not much as been posted in the last 24 hours. I probably wouldn't have noticed either if Eric hadn't been complaining...er...attentive to the status of ConnorWatch around the clock. Regardless, nobody has been able to post since yesterday at 3:11 A.M., so some of you were getting nervous. That's good - thank you for your concern and prayer. I'm pleased to report that we were successful in restoring the blog to full functionality, and everything should be right as rain as far as ConnorWatch goes.

For all those who want to know what happened...well...it's technical.

Eric hoped I could sum it up in two or three sentences, so I said, "well, I'm not an engineer, but what the hey, I'll give it a shot."

As best as I can tell, at approximently 11:58 Universal Coordinated Time, October 23, the ConnorWatch blog, through no fault of its own, other than being a somewhat complex piece of software residing on a new server in Pennsylvania , where it organized data related to Connor Williamson in response to the HTML requests of various and sundry computer users around the world, and enduring the attention of Connor's uncle Brad, who was always concerned, some would say overly, that either the ConnorWatch server would not have adequate horsepower to support the simultaneous requests from ConnorWatch users on six of seven continents, or that he would inadvertantly destroy 130 days of ConnorWatch blog entries and the associated comments by a careless keystroke, which, of course, was patently not a concern had he only read the hosting provider's standard back-up plan and compared it to his own practice of backing up the blog routinely, suffered an inadvertent heavy neutrino interaction.

It would have been the only neutrino identified that day at the CERN Large Scale Sub-Atomic Particle Detector (LSSAPD) in Switzerland, had it not collided with an errant electron in the 18th logical bit in the third chip on the second of four dual in-line memory modules, whacking it silly, and changing the associated byte from a logical 1 to a logical 0, which consequently caused the termination of a critical subroutine and the associated failure of the ConnorWatch blog to update, and then, without any apparent loss of momentum, deflecting through downtown Encino where it left a molecular distortion in the plastic of a Seven-Eleven sign and a microscopic hole in a paper cup that would persistently irritate Delmer Schafly, a local software engineer, who having spent his last ninety-nine cents in change, scraped from the ashtray of his 1995 Geo Metro, on a large cherry slurpie, would notice red stains on his only white work shirt for the rest of the afternoon, and would wonder silently to himself where on earth they could have come from, as he had been very careful with both the lid and the straw, while the rest of his co-workers continued to mock him, as they usually did after lunch, rather than pursue their assigned task at the California division of Labsoft, a provider of scientific software to the research industry, where, interestingly enough, they were revising the code for heavy neutrino detection at the CERN LSSAPD.

Later it would be discovered, through a remarkable series of coincidences, that Connor's father's name, Eric, and the word blog both have the same number of letters.

Uncanny.

I hope that clears it up.

Brad

Michigan

----------------------------------------
Print This Page