Noted above that the "mudcat clock" appeared to be 12 hours off, but it now seems to be 24 hours off - unless I'm in a time warp of some kind.

My clock is showing 1:00 pm 17 August 2011
Mudcat time would be 2:00 pm 17 August 2011
Last post shown (when I started this post) was 1:56 pm 18 August 2011.

No big deal, until the server clock corrects itself or somebody gets around to a correction. (I don't think Max picked up and moved to a different time zone, but he may have thought about it.)

Based on the timestamp for the last post that was aparently prior to the BIG ZAP, the disaster was at about 14 Aug 11 06:56 PM.

For those who just can't stand having a discussion interrupted, the "active threads" displayed then would have been those less than "1 day" (24 hours) old BZ (Before Zap). Refresh 3 days back doesn't pick up any additional threads working, so a "7 days" back Refresh is needed to see all that were up at ZAP TIME. There were about 69 threads in the top section and about 25 in BS - minus those already having new post AZ.

Posting a list would have made a very long post.

It appears that a few people knew how to look up threads "across the great divide," as some have been brought back to life, but it appears that "all has been saved," (is a "Hellelujah!" required?).

Startup traffic appears to have been heavy, since quite a few posts got on while I was still getting "no response" errors, probably just time-outs for the last several due to traffic.

Anyone who can't read this post should of course "just keep trying." (I've been reading too many software manuals, so I know that the advice "if your email quits working you need to send an email to your ISP" is standard computer stuff - hope it's not too techie.)

John