The Real Blogger Status

One subject of mystery, in Blogger lore, concerns the infamous "bX" codes . One forum personality, long ago, compiled a blog listing several hundred known codes, and their supposed "diagnoses" - and would later use the blog as a reference, when advising how to solve a given "bX problem". That same person showed complete lack of understanding, in a single sentence. It's disheartening to see that the bx error code problems are still existing. The "bX" codes are not problems - they are simply symptoms of problems , identified using a canonical code structure.

One of the reasons why Blogger code is so "unstable" (judging from the threads in the help forums) is that, as I wrote long ago , it involves code and data that starts on Blogger computers ("servers"), but is processed from other computers ("owned" by bloggers) which are connected to the Blogger computers over networks that nobody owns or controls. Some of these factors Blogger can accept responsibility for. Others we (the blog owners, or blog readers) have to accept responsibility for. And still others are the fault of the network owners, and many of those are problems which nobody will accept responsibility for. And that's the problem with diagnosing the ever common bX- codes. Of late, some bloggers are pumping themselves up, and declaring to the world Finally the solution to the BX error codes of blogger.com Don't know who and why it works and why google/ blogger have failed to recognize such simple tricks. But still that doesnt reduce its ef...

In the past - not so long ago, and not infrequently - you might be accessing or updating your blog, and you'd see a monolithic error message that made many bloggers want to tear their hair out by the roots. We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it. If you've been blogging for any past amount of time, I'm sure that you remember seeing that. I know that I do. On January 17, 2007, all of that ended . Blogger replaced that incredibly annoying message with a large series of error codes. Such a simple task, in concept. Each possible failure point in the Blogger codebase was assigned a different bX- code, replacing the old "We apologize for the inconvenience ..." message with a unique failure point code for each different problem encountered. For all of their simplicity though, many bloggers don't seem to see the forest for the trees. it...

In the not so distant past, and not nearly rarely enough, you might be updating, or possibly viewing, your blog, and you'd see a monolithic error message that frequently made many bloggers want to tear their hair out by the roots. We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it. If you've been blogging for any past amount of time, I'm sure that you remember seeing that, more than once. On January 17, 2007, all of that ended . Blogger replaced that single and incredibly annoying message with an almost infinitely large series of error codes. Very simple, that. Each possible failure point in the Blogger codebase was assigned a different bX- code, essentially replacing the old "We apologize for the inconvenience ..." message with individual failure point codes. For all of their simplicity though, many bloggers don't seem to see the forest for...

Not so long ago, many Bloggers would complain, quite frequently of a common problem We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it. After various complaints and suggestions, Blogger seeded their code library and added a seemingly unique error code to each known failure point. Almost overnight, it seemed, complaints mentioning the generic error message quoted above disappeared. A much more maneagable query became common. I have a bX-aaaaaa code - what does it mean? Now, it seems, new Blogger code is being added that doesn't issue a bX- code, and the generic error message is being reported again. >> Forum thread links: bX-*00027 >> Copy this tag: bX-*00027

Hey Guys, Bloggers work, and blog, 24 x 7. Supporting them on an 8 x 5 basis isn't right. Strolling in to work casually today, to find thousands of panicked posts in Google Blogger Help , isn't cutting it. The Blogging world isn't all located in California USA. Your product is used worldwide, and you need to recognise that. Get your act together, please. This was more than a few minutes outage, and an inconvenience . This was a major malfunction . Don't keep doing this. This is not the first time we have had a similar major problem affecting millions of people . (Edit): But thank you for at least providing me a foundation for a nice succinct post title . >> Top

One of the complaints about the mysterious problem codes is that we have no glossary to explain what they mean. All that we really need, though, is the ability to associate the individual problems with each other, and distinguish the different problems from one another. We don't care about the universe of all possible problems, just the problem that we're looking at right now. If we're looking at someone who's reporting a bX-wj8w1r , maybe we want to see everybody else with the same problem. So we search on bX-wj8w1r . We can see all of the cases found, examine the stated symptoms en mass, and see what the actual problem is. Since we know that nobody describes their symptoms the same way, seeing all of the reports of the same problem, together, is much easier if we use the code. One of the problems with problem analysis is that dissimilar problems get lumped together, but similar problems are never reported together. It's impossible to analyse "login pr...

Last week, Blogger changed their system to issue mysterious strings of characters , when specific problems are encountered. The "bx-" codes are cryptic and mysterious, and have motivated much speculation. Problem Census - Blogger can see how many people are experiencing a given problem, and better prioritise resource allocation, to solve each problem. Peer Search - Any of us can search for others with our problem. Solution Search - Any of us, or Blogger, can learn if anybody has discovered a solution to a given problem. Solution Report - Blogger can report a solution, more effectively, if one is found. Problem Census - Blogger can see how many people are experiencing a given problem, and better prioritise resource allocation. Problems with more people reporting will receive more attention. Peer Search - Any of us can search for others with our problem. Misery loves company. Solution Search - Any of us, or Blogger, can find out if anybody has discovered a solution, o...

Exciting news here. It appears that Blogger, in an effort to make it possible to handle the ever increasing problem level, is now issuing problem codes, rather than diagnostic messages, when specific problems are experienced. The old familiar, monolithic We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it. appears to have been replaced by some very unique error codes.

Long ago, and oh so far away (no, that's a popular song from when I was young), I wrote an article Why Do I Do This? . This is not a rehash of that article. I've had a few folks, (maybe misunderstanding my motives, maybe wanting to interfere with my message, who knows?) tell me, in not so many words but close Chuck, you have your head where it won't see any sun. Of Fables And Blogger : Comment #3. To the Blogger Staff Reading This Group Damn, Down Again, Is There Someone Smart Enough to Fix This Mess? It appears that my pointing out that There are no blog hijacks (in these cases) . There is no major outage of Blogger or Blogspot (right now) . Blogger shouldn't be expected to respond to every complaint immediately (without any work on our part) . ... all of these posts, in general, mean that I am trying to be a shill for Blogger. Simultaneously, though, I wonder whether Blogger might become tired of my prodding them. I prod them to get off their coffee breaks and fix...