There was lameness
So, Blogger - ya know, normally I love ya. But when you lost your ability to publish my content and waited nearly 16 hours before putting up a status message - that's lame. This is the same problem I've reported three times before - and each time received a response that "it must be something on my end."
So, when the same ineffectual, passive error message appeared yesterday -
- I had to think to myself, what a load of Microsoft-worthy spin-zone bullshit that is. "There were errors" is like those old cascading Windows errors that would announce "a fault was detected because an error occurred,' or when the Pentagon explains away a domestic accident helicopter crash with "mistakes were made." What errors? Socket is not established? Is that my fault or Blogger's?
Turns out, it's theirs. Some 16 hours after I first found out that "there were errors," and after pulling my hair out looking at my computer, router, cable, and web hosting configuration, this appeared on Blogger's status board:
So, when the same ineffectual, passive error message appeared yesterday -
- I had to think to myself, what a load of Microsoft-worthy spin-zone bullshit that is. "There were errors" is like those old cascading Windows errors that would announce "a fault was detected because an error occurred,' or when the Pentagon explains away a domestic accident helicopter crash with "mistakes were made." What errors? Socket is not established? Is that my fault or Blogger's?
Turns out, it's theirs. Some 16 hours after I first found out that "there were errors," and after pulling my hair out looking at my computer, router, cable, and web hosting configuration, this appeared on Blogger's status board:
Yeah, but some fundamental service problems remain. Blogger: There are errors.
leave a response