What we got here is... failure to communicate.
Blogger Support wrote some interesting guidelines about Blogger Status.
Blogger Status: This venue is used by the Blogger Team to report production outages, such as database problems. This is not a place where we report known application issues.
The people who depend upon Blogger Blogs known nothing about application issues vs production outages. They just know that they can't login, can't publish, whatever. Then they go to Google Blogger Help - Something Is Broken, and they see a dozen other folks reporting the problem, and nothing being done. And when there is a 3 day discussion about a problem, and nothing is done for 3 days, and then we see a Blogger Status post like
Wednesday, August 30, 2006
Posting to the Blogger Atom API (e.g. via a third-party website or desktop client) is not working properly. We are investigating.
Update, 11:24AM: This has been fixed.
Posted by Pete at 10:54 PDT
there is an example of the problem - failure to communicate.
How many problems take 30 minutes to be analysed and fixed? What went on, in Blogger Support, during the previous 2 - 3 days of discussions in Google Blogger Help?