Skip to main content

Posts

Showing posts with the label Blogger Milestones

HTTPS Availability For All All Blogger Blogs

After years of waiting, this blog is now readable, using HTTPS. This blog, and others published using properly setup custom domains, now provides optional HTTPS connectivity - joining BlogSpot published blogs.

Would Be Followers Being Blocked By Blog Owners

This month, we have a few reports, in Blogger Help Forum: Get Help with an Issue , about problems Following some blogs. Why am I being blocked, from Following? Some would be Followers are taking this personally. Please, don''t do that.

"Export / Import" Is Now "Import & back up"

Blog owners who need to export blog content are reporting confusion, in Blogger Help Forum: Get Help with an Issue . I'm trying to export my blog, but when I click "Settings > Other", there is no "Export" option! Not all blog owners realise that the "Export" wizard is now "Back up". Changes in functionality may perplex blog owners, too.

Dear Followers Of This Blog ...

If you did not use a Blogger / Google account when you Followed this blog, years ago, you are probably not Following now . During the past month or so, this blog has gone from 5,300 to 4,800 Followers . Owners of other blogs have reported similar reductions. Look at the Reading List, in the Blogger dashboard - if you use Blogger. Is this blog listed? If so, you are Following this blog, using a Blogger account. If not, you may want to add this blog to your Reading List .

The "Recently Updated Blogs" Display Is No More

In 2006, we discovered an interesting feature of Blogger, which let us monitor blog publishing activity , in real time. Sometime last year, " Recently Updated Blogs " stopped working. Last month, we reported the outage, to Blogger. Recently, Blogger Support described "Recently Updated Blogs" as an "experimental" feature, which won't be restored, for reasons of privacy / security. R.I.P., R.U.B.

bX-sp4hmm

A quiet evening at home? Not Tonight. We're sorry, but we were unable to complete your request. When reporting this error to Blogger Support or on the Blogger Help Group, please: Describe what you were doing when you got this error. Provide the following error code and additional information . bX-sp4hmm Additional information uri : /2006/12/connecting-two-dissimilar-networks.html host : nitecruzr.blogspot.com This information will help us to track down your specific problem and fix it! We apologize for the inconvenience. So much for using PChuck's Network for giving advice tonight. And I'm apparently not alone , either. Looks like it started about 17:35 PST . Doesn't affect all blogs, either - PChuck's Network (my exemplary victim, here) is down, but The Real Blogger Status is up. Both are New Blogger with Classic templates. The Real Blogger Status - Beta , New Blogger with Layout template is also up. 3 hours later, nothing in Blogger Status . And I don...

Say Goodbye To Old Blogger

The migration to New Blogger 2006 is in its final stages. If you haven't gotten the monolithic demand, you will any day. Move your account to use the new Blogger No "Please", no "Soon". You may, for a limited amount of time, have one last chance. There are two possible web site addresses, to login from. http://www.blogger.com/home , where you are forced to migrate. http://www.blogger.com/ , where, if you have an unexpired cookie, appears to still lead to your Classic dashboard. Let's see how long the latter remains operational. And don't logout, or you're done. If you have a blog with team relationships, you would be very much better off migrating NOW, while you can plan the migration properly . But before you get to this point, please organise your accounts - make sure that all account names and passwords are up to date. You won't even be able to migrate your blog to WordPress , if your account / password isn't up to date. Now, some of ...

Blogger Issuing Diagnostic Codes

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.