The LightBox Image Display Option Stopped Working, Recently

Last week, the popular display option, Lightbox, used for showing full size images in Blogger blogs, stopped working.

Anxious blog owners reported that full size images are now being displayed in a normal browser window, with the browser back arrow required to return to the blog display - instead of the elegant black background overlay with the mysterious "X" which closes the overlay. The problem appears to affect all images in the blogs affected.

An immediate sampling of the forum problem reports suggested that it's likely that all Blogger blogs are affected. Since not all blogs may contain enough images, and be owned by people who are attentive enough, we are not seeing massive volumes of problem reports.

We did open a rollup discussion, in Blogger Help Forum: Something Is Broken, where we are gathering a good sample of the blogs involved. To date, no obvious affinity has been discovered, in the over 100 responses posted.

Today, we have a mysterious suggestion, posted in a forum discussion, which may provide a workaround for the problem.

We are advised to add a brief snippet of code to the template.

<script src='http://www.blogger.com/static/v1/jsbin/2321381434-lbx__fr.js' type='text/javascript'/>

The snippet in question is added to the very end of the template, using the "Edit HTML" option, in the dashboard Template wizard, after </body>, and before </html>.

</script>
</body>
<script src='http://www.blogger.com/static/v1/jsbin/2321381434-lbx__fr.js' type='text/javascript'></script>
</html>

I added this snippet of code to the template for this blog. I don't use a lot of images in this blog - but you may examine one previous post, where you will find a picture. If you click on that one picture, you will see the full size image displayed in Lightbox format - which was not the case, earlier today.

The code snippet in question is hosted in "blogger.com", so it should be safe. And, it's not difficult to add - or to remove. That said, I have no idea if it may conflict with other code - so anything is possible. It is marginally more reliable than third party code.

I've done no further testing of this fix, so I'll await your feedback. You may comment here - or in the rollup discussion.

When You Setup A Custom Domain, Please Know And Observe Your Limits Of Expertise

Too many blog owners, when they setup a custom domain for their blog, do not consider the details.

We see signs of the problem, too often, in Blogger Help Forum: Something Is Broken.

Can someone give me step by step instructions for setting up a custom domain with xxxxxxx registrar? I contacted xxxxxxx customer service - and they told me a lot of things I didn't understand! Would it be easier just to transfer the domain to GoDaddy?

The short answer here would be

Yes, it would be easier just to transfer the domain to GoDaddy.

Unfortunately, that answer is not completely correct - and the correction may leave you with a broken domain.

Too many blog owners, eager to setup a non BlogSpot URL for their blog, do not consider the details involved, when they bypass "Buy a domain".

Part of the blame, for this problem, has to fall onto Blogger's head. People using "Buy a domain", for their first domain purchase, see the domain purchase as such a simple process. They never become aware of the complexities involved in a domain purchase, until they setup their second domain, and decide to "roll their own".

Let's look at the levels of experience needed.

• Beginner: Use "Buy a domain".
• Intermediate: Use the Google Apps or Google Wallet wizard - or alternately, buy a domain from one of the 8 identified registrars.
• Advanced: Buy a domain, directly, from any of the thousands of registrars, worldwide.

---

As of 2013 June, "Buy a domain" is not offered, as part of "Add a custom domain" - although blog owners, in the USA, may use Google Domains. This will leave people outside the USA with one option - "Advanced".

---

Beginner blog owners are strongly advised to use "Buy a domain". Choose an available domain, provide payment details, and your domain is setup. Wait until Transition expires, and get to work referring your readers, search engines, and other Internet services, to your new, non BlogSpot URL.

Intermediate blog owners, able to understand simple instructions, should be able to use the wizards provided by Google Apps or Google Wallet. Alternately, Blogger provides reasonably complete and simple instructions for setting up a domain with the 8 most popular registrars.

Advanced blog owners are free to choose any registrar, of the thousands out there. But beware! You are on your own, when you do this.

• Use of any non designated registrar does not free you from the constraints of the three custom domain models.
• It will be your responsibility to determine the syntax used by the Zone Editor, that's provided by the registrar.
• It will be your responsibility to ensure that the registrar, that you choose, can provide the required DNS address entries.
• It will be your responsibility to verify the precise sequence used, in any DNS host / registrar setup task.
• It will be your responsibility to research the details, before you start.
• Once you have purchased the domain of your choice, that domain will remain with that registrar, for 30 to 60 days. Very few registrars let you buy a domain - then immediately transfer registration.

So choose your registrar according to your needs - and according to your skill level. Don't start a custom domain project, before verifying that your experience is complete. Make the right choice, before you sign on the dotted line.

If You Comment On Blogs Extensively, You Should Consider Using Google 2-Step Verification

One recently identified cause of deleted Blogger blogs appears to involve brute force hacking against our Blogger / Google accounts.

We've known, for some time, about blog owners receiving alerts about "suspicious" / "unusual" account activity. The alerts frequently involve locked or deleted Blogger / Google accounts - and generally include the owner having to change their password, solve a CAPTCHA, and / or provide their phone number (mobile or home phone) to login.

Later, people started reporting that their blogs were being deleted - possibly as a result of having to change their password, solve a CAPTCHA, and / or provide their phone number.

I've been observing - and blocking - an annoying style of comment based spam, which I have termed "nice blog" spam, for some time.

Nice blog. I will keep visiting this blog very often.

This style of spam, from what I can tell, has been published by the millions, in various blog comments, on both Blogger and non Blogger platforms.

The reason for the spam always intrigued me. Observing that the spam was published in the millions, suggested to me that it had a special purpose, intended by its creators. Looking at a typical spam message, in my email (since I moderate before publishing), I could see no consistent type of content.

• Some messages would contain links, others not.
• Some messages would mention what looked like commercial products, other references were obviously imaginary targets.
• Some messages would appear to be mere babble.

Recently, I discovered one strong possibility for the purpose of the spam - a very ingenious form of email address mining. The spam comment is only needed to allow a hacker to subscribe to a given comment stream, using the "Email follow-up comments to ..." option. It's possible that the subscription is not even affected by moderation - whether the blog owner is moderating, either before or after the comment is published to the blog, the hacker remains subscribed to the comment stream.

All that the hacker / spammer has to do is to publish a spam comment, select the "Email follow-up comments to ..." option, and watch while his Inbox fills up with subsequent comments from other Blogger / Google / OpenID account owners. Any comment containing an email address, and linking to a Blogger blog, would go straight into the hackers database.

Later, the hacker could go to work against the Blogger accounts referenced in the comments. In some cases, this would result in successfully hijacked Blogger blogs, which would become part of a spammers blog farm where advertisements of various nature could be hosted. Valuable blogs, with established reader populations, could also be used to serve malware (and more hacking) to unsuspecting readers.

The demographics of some hijacking attacks provide interesting clues. In one episode, we had a significant number of home / personal / small business blogs that had been hijacked by one specific individual. Many of the victim blogs

• Contained details relevant to the owners, which provided clues to passwords used by the owners.
• Were owned by people who used commenting extensively, for networking both with friends, and with business targets.
• Were read (and commented upon) by similar people, who similarly provided password clues in their own blogs.

Having been part of the restore process, both with people who had their blogs hijacked, and who had their accounts locked and blogs deleted, I observed that the former (hijacked blogs) seem to have decreased in volume as the latter (accounts and blogs locked / deleted) increased in volume. I don't think that the relationship is coincidental - or spurious.

My opinion is that the locking of Blogger / Google accounts - and subsequent deletion of blogs - directly results from detected attacks against the accounts in question ("suspicious" / "unusual" activity). Noting that the attacks seem to be more common to people who comment on blogs as a form of networking, it appears that commenting can lead to accounts and blogs being locked or deleted, as Google protects us against hacking.

Considering this possible cause and effect relationship, Google 2-step verification is a good idea. Click here, for Google instructions on setting up 2-step verification.

Use of 2-step verification helps safeguard our accounts against brute force hacking. This will help anybody who is anxious about accounts and blogs being deleted or locked, as a result of "suspicious" / "unusual" activity. If you own a blog which is subject to this threat, you should consider using 2-step verification.

The sanity (heart attack, ulcer) that is saved may be your own.

>> Top

Stats Displays Pageviews - Not Unique Visitors

Too many blog owners do not understand the unique capability of Stats - nor do they understand its limitations.

We see the periodic question in Blogger Help Forum: How Do I?.

How do I find out how many actual people are viewing my blog?

Stats does not provide unique visitor counts - Stats provides pageview counts.

It's simply not possible to determine, with 100% certainty, how many different people are viewing your blog.

Consider these environments, where multiple locations, or people, are involved.

• A single person can use multiple computers, simultaneously.
• A single person can use a mobile computer, moving from one cellular connection to another.
• Multiple people can view the same computer, simultaneously.
• Multiple people can share the same computer, serially.
• Multiple people can share the same Internet connection, serially.

There are other visitor meters besides Stats - and some other such products will provide "unique" visitor counts. Each product, which claims to provide "unique" visitor counts, will do so based upon specific limitations and techniques.

One of the most obvious ways to determine unique visitors is by comparing IP addresses. Surely, two pageviews from the same IP address will be one person - and two pageviews from two different IP addresses will be two people, right? Wrong.

• One person can use two computers, simultaneously.
• One person can use a mobile computer, moving between two locations (each location will have a different IP address).
• Two people can use the same computer, at a library or Internet cafe.
• Two people can use the same mobile Internet connection.

In each of these cases, one person may look like two people - or two people can look like one person.

It's even possible that two people can access the same page, from the same computer, one after the other. If the first person does not properly clear the computer, after use, the second page access will be from cache - and will not access the server. The second person, using that computer, will not show up in a Stats log. Again, two people can look like one.

Some visitor logs will drop cookies onto a computer. Detecting a cookie already in place, this indicates one person, returning - and successfully dropping a cookie, indicates a different person, right? Wrong, again.

• Again, a shared computer is a possibility.
• Not all computer owners will permit unknown websites to drop cookies, onto their computers.
• And some owners, when they permit cookies on their computers, will periodically clear cookies.

Some very sophisticated visitor logs can compare demographic details, similar to the Stats Audience display. Besides IP address, what can be determined?

• Operating system, brand, model, and version.
• Browser brand, model, and version.
• Maybe, location (possibly determined by IP address, again).

And finally, some visitor logs will compare IP address, over a given time interval. Arbitrarily deciding that all activity from the same IP address, over a period of 30 minutes, represents a statistical "single person", is a known technique. This is not a legally significant technique, however.

The bottom line is, as I state repeatedly, you simply cannot compare numbers from any two visitor logs or meters, with any degree of usefulness. Each product will have its own way of determining unique visitors - when they even suggest a "unique" visitor count. Stats simply avoids the uncertainty, and only provides pageview counts.

>> Top

If You Use CAPTCHA Screening On Your Blog, Try Publishing A Comment, As A Guest

Not all Blogger blog owners, using CAPTCHA screening to reduce abusive comments on their blogs, know first hand what the typical CAPTCHA puzzle can be like.

We're seeing a few concerned blog owners, in Blogger Help Forum: Something Is Broken, asking why they're seeing fewer comments on their blogs.

I'm hearing from people that they can't post comments on my blog. I tested, and comments are working just fine. What is the problem, here?

Not all blog owners bother to test the CAPTCHA, on their blogs - or even know why they don't see one, when commenting.

Not all blog owners, enabling Word verification in their blog commenting settings, bother to read the tool tip behind the "?".

Show word verification
This will require people leaving comments on your blog to complete a word verification step, which will help reduce comment spam. Learn more.
Blog authors will not see word verification for comments.

The simple advice

Blog authors will not see word verification for comments.

does not sink in, to everybody.

This leaves many blog owners unaware of how frustrating it may be, for their guests to comment, on their blogs.

If you're a blog owner, musing whether to add word verification to your blog, in an effort to cut down on the spamming and trolling going on in many blog comment threads, maybe you should try posting on your blog, as a guest. With "Show word verification" set to "Yes", logout from Blogger - or clear cache, cookies, and sessions (yes, all 3!) - then restart the browser, and try leaving a comment on your blog.

What you discover may not please you. Then ask yourself how many of your readers will have the patience, to solve a CAPTCHA, every time they wish to publish a comment?

As a blog owner, you have 3 settings which are used, in proper combination, to provide a safe environment for your readers to leave comments.

1. Authentication.
2. CAPTCHA Screening.
3. Moderation.

Consider using one or both of the other two options, if possible.

>> Top

Renaming Your Blog Requires Choosing An Available Blog Name

Like creating a blog, the task of renaming your blog involves one very important step - choosing an available blog name.

When you rename your blog - as in change the blog address - you have to pick a name (address) that's not in use. Both creating a blog, and renaming a blog, suffer from one key detail - you can't identify an available address before you get started.

When you create, or rename, a blog, you can only get to the task at hand, and start with the best choice.

Like "Create a blog", you'll only find out about an available URL after you have successfully chosen that URL for your blog. Unlike "Create a blog", the Blog Address wizard does not verify availability in real time.

1. Paste or type the desired blog name (Only the "yyyyyyy" in "yyyyyyy.blogspot.com").
2. Hit Save.
3. If the name was available, you'll be looking at the initial Blog Address display, with the new address "yyyyyyy.blogspot.com" identified - and "yyyyyyy" will now be unavailable.
4. If the name is not available, you'll get the sad news

   Subdomain: yyyyyyy is not available.

   And now, go back to Step #1, and try again.

If you want to do the rename with the least stress, you make a list of possible choices before you start, and sort the list in decreasing preference. Decide which names you like the most, before you start. Then start the above process with Step #1, and your top choice. If you end at Step #4, pick the next choice in the list, and go to Step #1, again.

As with "Create a blog", you should plan to go through your list as promptly as possible. Hesitate too long, when making the next choice, and your alternate choices could be unavailable.

If your choice of name will affect design work on the existing blog, yet you wish to change the blog design before renaming the blog, setup a stub blog - and pick the best available name for the stub blog, now. Once that's done, make the necessary design changes on your current blog - then swap names between the stub blog and your current blog. You'll likely use the stub blog, later.

As with creating a new blog, please note that addresses previously taken will not be reissued to you by Blogger - a 10 year old blog remains valid, whether published once daily for 10 years, or once 10 years ago and never again.

And as soon as you get the new name successfully chosen, be prepared to continue the renaming process, as promptly as possible.

>> Top

Blogger Blogs Displaying Mysterious "SECURITY WARNING" Popup Boxes

This week, we're seeing a few concerned blog owners, in Blogger Help Forum: Something Is Broken, asking about a mysterious SECURITY WARNING popup box, on their blogs.

Like the earlier concern about the transparent boxes covering the blog, this appears to be another broken FaceBook Connect gadget.

The mysterious SECURITY WARNING isn't too hard to resolve.

Generally, the problem will start with a new FaceBook accessory, recently added.

<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = "//connect.facebook.net/id_ID/all.js#xfbml=1";
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

<div class="fb-like-box" data-href="http://www.facebook.com/xxxxxxx" data-width="265" data-show-faces="true" data-stream="true" data-header="true"></div>

If you can identify the problem gadget in your blog, you can edit the gadget, and Remove it. Some owners have installed the code in question, in a specific post.

As an alternate solution, you may add CSS which will hide the warning. Using the "Add CSS" wizard in the Template Designer Advanced menu, add the following code:

#fb_xdm_frame_http, #fb_xdm_frame_https
{
 display:none !important;
}

As always, after you add or remove the code in question, and save the changes, you will need to clear browser cache and restart the browser, to accurately test success in resolving the problem.

>> Top

Recovering A Deleted Page Or Post, Chapter 2

Blog owners have been deleting their pages and posts, then changing their minds later, since Blogger started providing the ability to delete pages and posts.

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts. The easiest solution, in the long run, is to recover the PageID / PostID, and re publish the deleted page / post.

When the deleted page or post cannot be re published, the next option is to re build the page / post, possibly using feed cache.

Using this technique, you'll have to reformat the post content, as feed content is formatted relatively simply. When you publish the post, it will publish as a new post, with a new URL - so any external references to the missing post URL will still be broken.

Thanks to the recently offered Custom Redirects option, though, we can make this latter choice slightly less undesirable.

When a deleted page or post has to be rebuilt from the beginning, the classic prognosis was not good.

1. The content is retrieved or rewritten, then re formatted.
2. The page / post is re published, but under a new URL.
3. The readers, and the search engines, adjust to the new URL being used.

For many blog owners, issue #3 is the cruelest blow - as the blog suffers reputation loss, from readers and search engines seeing

404 Not Found

for the deleted page / post.

Given enough determination and time, the blog owner can get through issues #1 and #2 - but issue #3 is the gift that just keeps on giving. Using Custom Redirects, though, that does not have to be the case.

It's a simple solution - and your readers and the search engines don't have to do anything unusual.

1. Rebuild the page / post, using a carefully chosen Title / URL.
2. Add a Custom Redirect.
   • From: The deleted (previously published) URL.
   • To: The new (re published) URL.
3. The readers, and the search engines can view the re built page / post contents using the old URL - and update their record of the URL, as convenient to them, to point to the new URL. And the page / post never goes offline.

And you, the blog owner, can get back to work on new pages and posts.

>> Top

Confusion About Advice "If you bought your domain name from Blogger, you won't need to create a CNAME record."

To Blogger blog owners who want their new non BlogSpot URLs to display their blogs, this conflicting bit of advice provides only confusion and doubt.

If you bought your domain name from Blogger, you won't need to create a CNAME record.

That advice was written to advise the use of the Blogger "Buy a domain" wizard, which provides non BlogSpot URLs for Blogger blogs, through a simple 15 minute purchase process. In September 2012, that simple process changed, slightly.

If you are trying to re publish your blog to a non BlogSpot URL - and you are seeing an "Error 12" / "Error 32", or similar message in the Publishing wizard display - you need to add a second "CNAME" address to your domain.

The new "CNAME", added in September 2012, allows you to verify ownership of the domain to the Publishing wizard. Any time you re publish your blog to a non BlogSpot URL, you have to verify ownership. This prevents people who are not you from deviously publishing their Blogger blog to your domain.

If you are reading this, and you are the owner of any website which provides advice on how easy it is to purchase a non BlogSpot URL for a Blogger blog - and part of your advice mentions

If you bought your domain name from Blogger, you won't need to create a CNAME record.

Please, edit your instructions to reflect the reality of domain ownership verification.

If you are reading this, and you know of a blog or website which provides the confusing advice

If you bought your domain name from Blogger, you won't need to create a CNAME record.

let us know, below.

Try and reduce the confusion, when people have to re publish their blog, after using the Blogger Publishing wizard - or possibly after buying directly from a registrar. Help us, to help you.

>> Top

Accounts Locked For Unusual Account Activity

One of the more intriguing tales of Blogger blogs, currently being explored, involves blogs mysteriously deleted by Blogger.

My blog just disappeared from my dashboard - and no, it's not listed under "Deleted blogs"!

In some cases, the owner knows more than is implied, from the obvious wording of that problem report.

As Blogger / Google continues to improve the hacking / malware detection and removal process, they are making the recovery of accounts locked for "suspicious" / "unusual" activity easier - and more transparent. The increased transparency may, in some cases, cause mystery.

Diagnosing the many mysterious blog disappearances, currently being reported in Blogger Help Forum: Something Is Broken, may involve what the blog owner does not report - as much as what the owner does report.

Hacking Detection / Recovery is constantly being improved.

Blogger / Google is constantly refining the hacking detection / recovery process, to both improve the possibility that any activity will be detected, and to make it easier for the victims of the hacking to deal with the recovery process. As they make it easier for the owners to recover the accounts locked, they make it less likely that the owners will mention the locked account recovery, when later reporting the blogs, mysteriously missing from the dashboard.

Some owners will provide vague clues, alluding to hacking detection.

In some cases, the blog owner will provide vague clues, which refer to an immediately previous account unlock.

• Required to change the account password.
• Required to provide a phone number - and receive either a text or voice message with a recovery code.
• Required to solve a CAPTCHA.

All of these clues can be relevant to a locked account, or to various other anti-hacking / anti-spam activity by Blogger / Google - and can be overlooked as a locked account symptom, when stated in a forum problem report.

Other times, only the circumstances identify the situation.

In other cases, the only clue provided will be that the blogs in question are missing, and not listed in any dashboard list - "Deleted blogs", "Locked blogs", or "My blogs". In cases where we've simply reported missing blogs for malware / spam review, to Blogger Support, we're later advised to instruct the blog owner to recover the account.

Every owner does not always appreciate the diagnostic process.

Since immediate review of any blog cannot be always guaranteed by Blogger Support, it's to everybody's benefit that we request clues to verify the problems being reported. Unfortunately, the questions asked may not always seem relevant to some blog owners, unhappy about the mysterious loss of their blogs - even though they may contribute to the problem, inadvertently.

All owners won't even get email, alerting them to action taken.

And thanks to the possibility that not all blog owners may even get a notice when their accounts are locked, owners with multiple accounts may not even realise that a given Blogger account is locked. These owners find out that a given blog has been deleted, only after it goes offline and expires from cache. This will make some blog owners even less cooperative, when asked to provide diagnostic details about their problems.

Comment Moderation Provides Limited Movement Between Queues

Not every blog owner understands the limited ability to moderate comments - and to correct a moderation decision, previously made in mistake.

We see occasional evidence of confusion in Blogger Help Forum: Something Is Broken.

I deleted a comment by mistake. How do I get the deleted comment back?

and

I marked a comment as "Not Spam" - but now it's not in "Awaiting moderation"!

The ability to move comments, in the moderation queues, is limited - and it's asymmetrical.

There are 3 queues, which are visible from the dashboard Comments wizard.

1. Published.
2. Awaiting moderation.
3. Spam.

Besides the 3 queues, there is a fourth possible state - Oblivion, which is not visible, and from which comments cannot be moved. Some blog owners may confuse Oblivion with a desktop computer standard - "Trash Can". This confusion can cause problems.

1. The contents of "Trash Can" can be viewed. Comments in Oblivion cannot be viewed.
2. The contents of "Trash Can" can be recovered. Comments in Oblivion cannot be recovered.

A comment, starting out in the "Awaiting moderation" queue, can be moved in several ways.

1. Into "Published", using the "Publish" button.
2. Into Oblivion, using the "Delete" button.
3. Into "Spam", using the "Spam" button.

A comment, in the "Published" queue, can be moved in two ways.

1. Into Oblivion, using the "Delete" button.
2. Into "Spam", using the "Spam" button.

A comment, in the "Spam" queue, can be moved in two ways.

1. Into "Published", using the "Not spam" button.
2. Into Oblivion, using the "Delete" button.

It's apparently possible to move comments back and forth, between "Published" and "Spam". Presumably, either movement provides some training of the comment spam filters.

1. From "Published" to "Spam", using the "Spam" button.
2. From "Spam" to "Published", using the "Not spam" button.

There is no similar symmetry of movement, for the "Awaiting moderation" or Oblivion states.

1. A comment in "Awaiting moderation" can be moved into either of the other 3 states - Oblivion, "Published", or "Spam". Once moved, a comment cannot be moved back into "Awaiting moderation".
2. A comment can be moved into Oblivion, from any of the other 3 states - "Awaiting moderation", "Published", or "Spam". Once moved, a comment cannot be returned from Oblivion.

If you're moderating comments, you need to understand the asymmetry. Once you move a comment, and you recognise a mistake, you cannot always move it back to correct your mistake.

>> Top

What Are The Mysterious Turning Gears?

This is a question, occasionally seen in Blogger Help Forum: Something Is Broken.

I cannot view some blogs - all that I see are gears, turning endlessly. What is going on, here?

The gears are animation, displayed by Blogger, while a dynamic template and blog content loads on the computer being used. Generally, the gears will play for a few seconds, then the blog will be seen. For an example, check out my Musings blog.

Sometimes, all that you will see are the gears, endlessly turning - waiting for the templates and blog content to download.

The dynamic templates, used by some Blogger blogs, represent an innovative approach to providing web content.

Normal web content, provided in Blogger blogs which use Classic, Designer, and Layout class templates, consists of comments, gadgets, posts, and templates, arranged together in pages (dynamic and static).

Blogs which use Classic (HTML only) templates arranges everything when the blog is maintained. Blogs which use Designer / Layout templates (HTML / XML) arrange the content when the blog is maintained - then build the individual pages when the blog is read by each viewer, dynamically. For all 3 classes of templates, the content is served from Blogger / Google servers, in individual display pages.

The Dynamic class of Blogger templates take the concept of dynamic publishing to another level. Dynamic class templates load a significant amount of script code (the template) directly to each client computer. Instead of reading the pages of blog content from a Blogger / Google blog server, a dynamic template script, running on the client computer, reads the published blog feeds from a newsfeed server - then turns the feed content into a display.

A Dynamic template is a specialised Newsfeed Reader, similar to the dashboard Reading List, or to Google Reader.

By offloading a large amount of the publishing process to the client computer, and by using the blog comments and posts feeds, Blogger provides blogs which can be viewed in a number of different ways - selectable by each individual viewer, and at the convenience of the viewer. This selectability is not without cost, unfortunately.

• The templates require a significant amount of script code.
• The templates require the blog comments and posts newsfeeds.

For most blogs using a dynamic template, and being viewed on most computers, the "turning gears" icon plays briefly, while the template code, and the blog comments and posts newsfeeds, are downloaded. As soon as downloaded, the content is assembled into a display, and the viewer can view the blog. This does not happen, in all cases.

• Some client computers may filter the template code.
• Some client computers may not have a fast Internet connection.
• Some blogs may not publish a full newsfeed.

If the client computer has a slow Internet connection, the viewer may watch the turning gears for more than a few seconds. If the computer filters scripts aggressively, or if the blog does not publish a full newsfeed, the gears play, endlessly, while the computer waits for the scripts and newsfeeds to finish downloading. In the latter case, the viewer can only find another blog to view.

If you encounter one or two Blogger blogs playing the turning gears, endlessly, then you are experiencing the reality of dynamic templates - some blog owners do not realise that they have broken their blogs. If you encounter a large number of Blogger blogs doing this, then you might want to check the filters, on your computer - including, but not only, the browser cookie and script filters.

>> Top

Blog Owners, Unable To Request Restore Of A Blog

One of the more intriguing issues, seen in Blogger Help Forum: Something Is Broken, involves people unable to recover control of their blogs.

I recently changed ISPs, and now I can't login to update my blog.

Occasionally, this issue becomes more complicated, because the blog is deleted - and the owner can't request that it be restored, using the automated review request wizard. Sometimes, the would be blog owner may to try to bypass the current blog recovery policy, by claiming special circumstances.

The blog has been deleted. I received no suspicious activity or password change notification emails, or emails of any kind related to my blog.

What is the story here? Can blogs just disappear from the Blogosphere, without the involvement of the blog owners - and be unrecoverable?

Recovery of a deleted blog starts with the requirement that only a blog owner can un delete a deleted blog - and this is where many mysterious disappearances start.

Only the blog owner can initiate hacked blog unlock review.

Since a Blogger blog is the property of the owner, and the owner is allowed to delete a blog any time required, it would not be right to let people who are not the owner un delete a blog - or demand that the blog be un deleted. To enforce this requirement, Blogger added the dashboard based Restore wizard.

Since only the owner will have the deleted blog listed in their dashboard "Deleted Blogs" list, only the owner can request restore of the blog in question.

Dashboard requested restores have multiple purposes.

The dashboard Restore wizard serves blog owners, with blogs deleted under various circumstances.

• Deleted by the owner.
• Deleted by Blogger, as a suspected spam host.
• Deleted by Google, for TOS Violation.

Any deleted blog will appear in a special dashboard list, "Deleted Blogs" or "Locked Blogs" - when it can be recovered. If the blog is not recoverable by the owner, there may not be a link.

Dashboard requested restores may not always be successful.

There are specific cases where a deleted blog may not be recoverable using the recovery wizard.

• The blog is locked, pending integrity check (following account lock for suspicious activity).
• The blog is owned under a different Blogger account, and is listed on another dashboard, under "Deleted blogs".
• A blog owner deleted the blog, long ago - and the blog is no longer recoverable.

A blog locked, pending integrity check, cannot be requested for restore.

Dashboard requested restores start with owner requested unlock.

The owner has to first have the owning account unlocked. Similar to the account recovery process, Blogger / Google will require that the owner provide proof of ownership, before the account will be unlocked. Only if the account can be unlocked, security specialists will inspect each blog owned by the account, and verify that each does not contain evidence of tampering by a temporarily successful hacker.

With blog security review in progress, the blog will be offline and invisible.

While a blog is under integrity check, it won't be listed on the dashboard of the owner - either under "Deleted blogs", "Locked blogs", or "My blogs". Neither the owner, nor any third parties, will be able to do anything except wait, patiently.

Blogs found to contain malware can be locked as TOS Violations, with the owner later required to remove the malware found. This requirement will apply for malware installed by the owner (intentionally, or unintentionally), or for malware installed by a hacker.

With blog malware review in progress, the blog will be offline - but visible.

With a blog locked pending malware removal, the owner is given the benefit of the doubt, and allowed to simply remove the malware, no questions asked. In some cases, Blogger may be able to assist by providing specific identification of the malware found - but this won't happen, consistently.

A blog owned under another account must be un deleted by the owner of the other account. Again, only a blog owner can have a blog restored - whether deleted by an owner, or by Blogger / Google.

A blog deleted over 90 days previously cannot be recovered. It won't appear on the dashboard of any (former) owner, since it can't be recovered.

It's dead, Jim.

Either way, you the owner have to wait for review to complete.

The basic rule is simple. If your blog was deleted, and if you're able to un delete it (or request un deletion), you'll have a link on your dashboard. If a blog is not listed on your dashboard, you can't request, with any predictable success, that it be un deleted - any more than you can demand that a non deleted blog be restored to your control.

Confusion About The Post Feed Redirect Feature

The world of Blogger blogs contains a lot of confusing terminology.

Some Blogger features don't even have names. Some names, which I use, are terms which I made up on my own, years ago - simply because Blogger did not provide a name, at that time. One term, which Blogger did give us, still causes confusion. The term "Post Feed Redirect" seems to describe an option, in Blogger, to redirect the post feed to a different URL.

The Post Feed Redirect feature is used by some confused blog owners, improperly.

There are several specific cases, all too common.

• Change the URL of the feed. Redirecting the blog feed, to simply change the URL, causes the feed to redirect to non existent content - or a dead feed.
• Publishing the blog to a non BlogSpot URL. Custom domain publishing provides automatic redirection of the blog URL - and by extension, the blog feed URL. Adding a feed redirect causes an infinite loop.
• Randomly expose the blog to new audiences. Redirecting the blog feed to a random redirector causes the blog readers to report a hijacked Reading List - and later, to simply remove the blog, using a redirected feed, from the Reading List.

This redirection, contrary to the term "Post Feed", also affects the comments feeds and the labels feeds, relevant to the blog where the setting is used.

Besides the fact that the option in question affects all feeds in the blog, the biggest confusion is that using the option does not actually redirect the feed - it redirects the references to the feed. People use this option in the expectation that it will change the URL of the feed. This option does not change the URL of the feed - it changes the URL used by references to the feed.

To change the feed references, successfully, you must have the URL mentioned by the setting already published, in a separate effort.

• If you renamed the blog to a different BlogSpot URL, you can redirect the feed reference, from a stub blog, to the feed published under the new URL.
• If you used a different service, like FeedBurner, to create a reformatted feed replica, you can redirect the feed reference to the FeedBurner feed URL.
• In either case, the URL has to exist, from a separate effort.

If you are reading this post, look down the page, after the "Newer Post Home Older Post" links.

Subscribe to: Post Comments (Atom)

There is an example of the original feed reference. The purpose of the post feed redirect feature, long ago, was to let the blog owners generate a different feed for the blog - maybe a FeedBurner republished post feed - and force that link to reference the FeedBurner republished feed.

If you use that link, and subscribe to the feed from this blog, you should get a subscription offer, using the FeedBurner feed for this blog.

The Post Feed Redirect simply lets people setup and use an alternate feed URL, without having to update the code for all links which reference the post feed - such as that link.

That's it - pure and simple.

If you have - even unintentionally - misused the post feed redirect in your blog, it's easy to correct the mistake. Just understand why you should correct the mistake.

Clear, Or Set, The Post Feed Redirect

One of the most mysterious settings, in our blogs, is the ability to redirect references to the blog feed.

Some people use the "Post Feed Redirect" setting improperly. When this is done, the problems created can be easily solved, by clearing the setting.

1. Go to the dashboard menu Settings - Other - Site feed.
2. Look at the entry for "Post Feed Redirect URL".
3. If that option is incorrectly set, click on "Remove".
4. Click on "Save settings".
5. You're done.

If you actually need the feed redirected, it's similarly simple to set it.

1. Go to the dashboard menu Settings - Other - Site feed.
2. Look at the entry for "Post Feed Redirect URL".
3. If that option needs to be set, click on "Add".
4. Paste or type the correct URL, into the box.
5. Click on "Save settings".
6. You're done.

The setting, for this blog, for instance, is:

http://feeds.feedburner.com/Nitecruzr-Blogging

Just understand what the setting does, how to clear, and how to add, the setting - and when you should use it, or not use it.

Google+ Circles Is Replacing Following / GFC

Those of you who have been Following this blog, in the past, may have recently noted a new gadget in the sidebar.

Just below the "Follow Me" gadget, you'll see "+Follow Me". The latter gadget looks similar to the former - but has some subtle differences. Some differences are visible, others not so visible. And some differences are not visible to the eye - but will still affect your access to this blog.

The Google+ Circles gadget, which on this blog is labeled "+Follow Me", appears similar to the Following / Google Friend Connect "Follow Me" gadget - but appearances can be very misleading.

The larger pictures are one obvious difference - but that's not the most significant difference. Some difference need to be discussed now, rather than later, for maximum benefit.

Blogger Followers lets your Followers Follow one specific blog.

Following / Google Friend Connect lets your acquaintances Follow a single blog. I have several blogs, and a different group of Followers for each blog. The Google+ Circles gadget shows everybody in all of your publicly visible circles, merged together. The merged concept may, or may not, be to your liking.

Google+ Collections now let you separate different content - so you can share one blog to one Collection, and specific people can Follow ("Circle") one Collection. I'm not convinced though that all of my Followers understand this distinction.

Blogger Followers let you use email and newsfeed subscriptions.

With Following / Google Friend Connect, your Followers can use email, or any number of newsfeed clients, to read the complete content of your blog - including each complete post, if you setup the blog feed that way. Google+ Circle members can read a snippet of any blog post intentionally Shared, in their stream - but will have to click on the link to the blog, in the snippet, to read the entire blog post. If you have read this far, that's what you have already done.

Following / Google Friend Connect works best for public blogs - and supports a reader audience of unlimited size. A Google+ Circle, likewise, supports a reader audience of unlimited size.

With a properly setup Google+ Circle, and a Blogger blog with a list of designated readers - and your readers properly accepting the emailed membership invitation, up to 99 of your designated readers can Follow your blog. As before, the limit for private blog distribution, as for any team blog, is still 99 members.

Anybody Following a blog, using the stream of any author of the blog, will see a snippet of each post Shared in their stream. To read the complete post, they will have to click on the link in the snippet. With a private blog, the reader will have to be a blog member, to read the complete post.

Many Blogger blogs have a lot of Followers, which will be missed.

Many publicly visible Blogger blogs have Following communities which vastly exceed my 4700 member population (my "Follow Me" gadget, as of April 2013) - and the possibility of losing those communities will not be willingly accepted by everybody. The integration of Following with the newsfeed subscription - and with the dashboard Reading List - is not automatic with Google+ Circles.

A blog with multiple authors (aka "team blog") will have either a Google+ Circles gadget for only one author - or multiple Circles gadgets, to fairly let people subscribe to the various authors Google+ streams. Neither solution will be exactly equal to the Following / GFC blog feed subscription - especially if the various team members are similar to me, and my range of interests.

Right now, it appears that a blog can have just one Circles gadget. How team membership blogs will use Google+ is another question to ask.

Many blog owners have multiple interests - and publish multiple blogs.

Similar to the team blog, we may wish to consider the multiple interests of each blog owner. I am one person, with a number of interests.

People who have intentionally subscribed to the newsfeed from this blog, and are specifically interested in my blog about Blogger blogs, may not be extremely interested in my blog about cooking - nor in my blog about jokes, pranks, and miscellaneous ramblings. Unfortunately, if you Follow my Google+ stream, you'll get a bit of each subject.

Some people may use Google+ Collections, to separate their different interests. It's possible that some Google+ Followers are now Following my RBS Collection.

Again, the Google+ Circles gadget appears to contain the total Followers for one person, for all interests of that one person. I have not yet found a tool that will allow me to analyse the interests of each of my Followers, and to accurately determine the specific areas of overlapping, between my own personal interests and theirs.

It will be impossible for many blog owners to keep an accurate Circle complement, and segregate each circle according to interest, so they may Share only relevant material with the specific members of each different Circle.

Integration of Blogger Follower, and Google+ Followers, requires compromise.

As the Google+ Circles gadget evolves, some significant improvements - and some compromises - will be required. Like the Internet, Blogger, and Google, are constantly evolving. This may require compromises by many Blogger blog owners.

We now have a rollup discussion, where each blog owner is asked to provide their thoughts about the above described issues - and possibly, others that concern you. Anybody who experienced the Blogger GUI upgrade of several years ago may, from experience, realise how much better off we may all be, with these issues discussed now - rather than later.

If You Are Not Planning To Renew Domain Registration, Give Your Readers Advance Notice

One of the saddest answers given in Blogger Help Forum: Something Is Broken starts with the naive query

My domain registration expired last month, and my blog is now offline. How do I redirect the domain back to the blog?

The answer here is simple, and does not provide a lot of promise, to the blog owner.

If possible, you may be able to publish the blog back to BlogSpot - but the blog will have to be re indexed from the beginning.

Once the domain registration expires, you cannot use the domain address for reputation or traffic source. Any search engine hit entries, to the domain URL, will be 404 - and there is nothing that you can do, if you no longer own the domain.

If your blog depends upon reputation, or search engine listings, for reader activity - and you are contemplating changing from a non BlogSpot domain address back to a BlogSpot address - you need to plan this change, before you start.

Successful publishing, back to BlogSpot, starts well before registration expiration.
A successful change, back to a BlogSpot URL, starts before the domain registration expires - while you can use the domain to provide reputation, and search engine hits, to the BlogSpot URL. I like to advise people to allow at least a month for any blog to be fully indexed by search engines, when a blog is new.

If the blog is mature, and is indexed under a non BlogSpot URL, the process of re indexing under the BlogSpot URL may be only slightly briefer. A mature blog will have one thing going for it, that a new blog won't - inherent reader reputation.

Reader reputation will help some blogs - not all - survive the transition.
Unfortunately, reader reputation will be good for one thing, when re indexing your blog under the BlogSpot URL - links on the readers blogs, to your blog. If your blog has readers who don't publish blogs, or their own reader list, publicly - or if you let the domain registration expire before starting the process of re indexing the blog - you won't gain a lot from reader reputation.

All of the links on your readers blogs, just like all of the links in the search engine result pages, will be

404 not found

This sight will not provide you with reader traffic, or with any reputation.

Start at least a month before registration expiration.
If you must move from a non BlogSpot URL back to a BlogSpot URL, the time to start is a month before the domain registration expires. This is one of the few times when I will tell you to use domain forwarding. Use the Domain Manager wizard, hopefully provided by the registrar, and setup a "301 Moved Permanently" redirect to the BlogSpot URL - if the domain host allows this.

You'll also want to add a notice on the blog, announcing the change - again, well before the domain registration expires. An HTML / Text notice, visible on all pages, would be best.

This blog will move back to a native BlogSpot URL on (date). Please update your bookmarks now!

Plan the migration, and keep your readers - and maybe your readers readers, who use the links on your readers blogs to find your blog.

If you wait until the last minute, you'll be starting over - completely.
If you wait until the domain registration expires, you'll have nothing to do but publish your blog with new content - and hope that the search engines will continue to pick up the new content under the new URL - the old BlogSpot address. And maybe your current readers will find your blog. Maybe.

Some Blogger Blogs Being Locked As Malware Hosts

For a long time, we've been dealing with various malware / spam mitigation issues, in Blogger Help Forum: Something Is Broken.

Recently, malware detections, long simply identified as "Malicious JavaScript" in the well known Spam Appeal Guidelines, was given its own identity, and a separate classification / appeal process. We're now seeing several common types of JavaScript, included in blogs which are typically mentioned in forum reports.

It may be helpful to describe some examples of JavaScript code being seen, so blog owners can avoid making the same mistakes, by not including these scripts in their blogs.

There are several common types of JavaScript applications, found in many blogs with the owners requesting review / unlock action.

1. CPA / Cost Per Action.
2. Multiple popups, such as a generic "Welcome!", followed by "Like my blog, before you read it!".
3. Password protection, on a page basis.
4. Security warning popups, suggesting that you need to install a recommended security software.
5. Social networking popups, demanding "Like my blog, before you read it!".
6. Traffic Redirection, targeting other blogs / websites.
7. Traffic redirection, targeting the canonical URL for the host blog.

CPA / CPALeads / Cost Per Action, and similar online marketing terminology, involves providing a reward for viewing a blog, or for subscribing to the blog feed. Some CPA scripts may be used to collect email addresses, also known as "email address mining", later used for hacking activity or spam distribution.

CPA scripts present another problem. Since Blogger blogs are intended to reward the readers by providing interesting and unique content, blogs which use CPA may be improperly designed or maintained. Blogger wants the blog owners to publish blogs which entertain or inform their readers - not blogs which require artificial or ingenious techniques to generate traffic, and visitor activity.

Multiple popups, such as an initial "Welcome to my blog!" greeting, followed by the well known FaceBook "Like my blog, to read my blog!" demand. If multiple popups should become an established practice, it's possible that malware producers could enjoy this technique, to conceal a malware installation.

Password protection, on a page basis, is an attempt to make a blog (or blog portion) private, by using a password. This protection is easily defeated, as the password is provided in the page (post / template) code, as plain text - and can easily be identified by anybody knowing how to view page source as text.

Besides the "protection" being easily bypassed, this is a problem because security scanning programs - such as the malicious scripting bot - can't pass through JavaScript code easily. When encountering this JavaScript application, your blog will be righteously classified, as a malicious script host.

Security warning popups, suggesting that your computer is infected - and offering, for immediate installation, the perfect tool to remove the claimed malware. Security experts know that this is similarly a favourite malware installation technique, where the computer owner would give permission to have the offered software installed - and the installed software would later install a botnet client or similar malicious trash.

Social networking popups are an arrogant way of wasting your readers time, and guaranteeing eventual malware classification of your blog. Popular among some WordPress blogs, the circular FaceBook "Like my blog, to read my blog!" demand is a good way to make genuine readers go elsewhere.

If you want genuine readers, who read a Blogger blog because of thoughtful, unique content, you will not get them by demanding that they boost your FaceBook popularity, before reading your blog. This is just another way of buying "Likes" - and it belongs in WordPress, not in Blogger.

Traffic Redirection, targeting other blogs / websites is a technique attempted by many hackers and spammers. The use of some blogs as gateways, leading to redistributors, which in turn lead to payload blogs or non Google websites, is part of many hacking / spam attacks. Google is trying to restrict the use of Blogger blogs as malware / spam hosts - and actively prevents scripts, which only shuffle readers from one blog to another, without choice.

Even though Blogger will not encourage you to move your blog, to Tumblr, Weebly, WordPress, or wherever, you are allowed to do this - if you feel the need.

Hello, faithful readers:

This blog is now hosted at my new blogging host. Please update your blog lists and bookmarks!

If you must do this, it's OK to post a notice, in your Blogger blog. You can even put a link, to the new blog, in the notice. You just can't use JavaScript, to automatically redirect the reader to the new blog.

Traffic redirection, targeting the canonical URL for the host blog, is a technique used by some blog owners who perceive Country Code Alias Redirection to present a problem. Some accessories installed on their blogs, and various non Google services which may be used to provide activity on their blogs, may not properly reference the canonical URL tag included in all Blogger blogs.

Since Blogger / Google wants all Blogger blog owners to benefit from improved world wide access to Blogger blogs, blogs which employ automatic canonical URL redirection may damage the effect of CC alias redirection. Blogs which host scripts which immediately redirect readers to the canonical URL, and are considered undesirable by any host government, may force an offended host government to block the entire Blogger service, in their country.

To prevent malicious misuse of Blogger by hackers and spammers, and to encourage effective long term use of Blogger by legitimate blog owners, Blogger / Google may detect any blogs which use these types of scripts as part of their general malware / spam classification strategy. Given the ability and willingness of the blog owner, to remove the JavaScript code in question, most blogs can be returned to service - but each blog will remain offline, until the removal is verified.

It's to everybody's benefit to identify, and to avoid use of, these scripts in our blogs, before it's too late. If your blog contains one of these scripts, why not remove the problem now, instead of waiting until you too have to post your problem report, in the forum

Help me! My blog was just locked for

MALICIOUS JAVASCRIPT

What do I do, now?

Blogger And Mobile Computers

Using the term "mobile computer" is an example of the challenges involved, in using this variety of computer.

Even identifying this device, which is present in so many different manifestations, is confusing.

• Mobile Computer.
• Mobile WiFi device.
• Personal Digital Assistant.
• Pocket phone.
• Smart Phone.
• Tablet.

As the use of mobile computers becomes more common, we're seeing more and more problem reports and questions, from people unable to use Blogger.

• Some folks would like to maintain and publish their own blog.
• Others would like to post comments to their friends blogs.
• And still others don't understand why all of the various gadgets on their blog don't work for their friends, who are also using their own mobile computers.

One of the challenges of mobile computers involves the use of smaller displays, and the need to simplify the content displayed. This requires the use of special browsers and templates, which are designed to accommodate the limitations. The need to support additional browsers and templates creates more work for Blogger Engineering, who now has more different products to support.

Also, many mobile computers are designed to work over proprietary networks, provided by various "phone" companies. Blogger has traditionally supported use of alternate services - email, and SMS - for publishing posts to their blogs.

All of these differences create complexity, and additional possibilities for failure. And we see more problem reports, attributed to use of "mobile" computers.

Full function ("desktop" / "laptop") computers have challenges - but they are still easier to use.

We know about the different major browser brands, and the differences created by the use of each browser, on our desktop and laptop computers.

Chrome, Firefox, Internet Explorer, Opera, Safari all have their various peculiarities. These differences are multiplied, when considering the issues involved in developing new features - and in keeping up with new browser versions, and continually updating the various Blogger features and wizards, when required.

Besides the various different browsers, we have to consider the different activities involved in using Blogger. Browsing blog posts, browsing comments, publishing comments, maintaining the blog, and publishing posts, are all different activities - and have their own different needs.

The relative lack of limitations in "desktop" / "laptop" computers still makes each different activity simpler for the blog owner or reader. The process of developing and supporting the different Blogger features is easier for Blogger Engineering. These differences are not so transparent, when using a "mobile" computer.

Mobile computers have known limitations.

• Reduced display size.
• Reduced display colour depth.
• Reduced processor speed.
• Lack of various system features and utilities.
• Lack of a physical keyboard.

All of these details require mobile browsers and templates which operate differently, and the various Blogger features and processes must be used differently.

Try performing the various tasks identified above, using your desktop and mobile computer - and observe the differences. You'll quickly realise the differences, when browsing blog posts, browsing comments, publishing comments, publishing posts, and maintaining your own blog.

One of the workarounds, used by Blogger, to deal with the reduced functionality of a mobile browser / computer, is the "mobile" template. The mobile template, which is optional for all modern Blogger blogs, displays only text and pictures - and eliminates the many accessories, gadgets, and shiny formatting which may be seen in any blog with a "normal" template.

The different layouts of the posts and comments, on a mobile template, makes posting comments a different experience - and the lack of the various gadgets will produce different visitor activity.

Alternatively, when one wishes to publish Blogger posts using a "mobile" computer, the "Blogger" mini app - written specifically for the various different "mobile" computer platforms - may be used. The "Blogger" app has its own shortcomings, such as causing posts to mysteriously revert to Draft status, from time to time.

The differences between the various "desktop" browsers are considerably less noticeable than the differences between some "mobile" browsers and computers. Most desktop computers use 3 different operating systems.

• Apple / Macintosh.
• Linux / Unix.
• Microsoft Windows.

Even with the different operating systems, the realities of marketplace competition creates some interoperability between the different desktop operating systems - and the different browsers are similarly common in design.

The better known mobile computers also have 3 major different operating systems.

• Android.
• Apple/iOS.
• Microsoft Windows.

Not all PDAs and smart phones use the standard 3 operating systems, however - some use proprietary browsers and operating systems, unique to the manufacturers. And the proprietary networks, provided by the different phone companies, further reduce the possibility of interoperability.

Lack of interoperability is going to create differences in how well different applications, such as Blogger, operate on the different mobile computers. These differences will be more significant than the differences created by the various "desktop" browsers, and operating systems - and we'll see more complaints from blog owners who can't use Blogger on their tablet, or whose readers can't post comments, using their smart phones.

Increasingly common use of multimedia content (both music and video) on mobile computers - combined with the lack of consistent support for cookies and scripts (and possibly, filtering of cookies and scripts) - will make availability of content differ, from computer to computer. Another problem here is lack of consistent support for the Adobe Flash product - which makes some YouTube content non playable, on some mobile computers.

Also consider the various security issues which may be different with mobile computers. Both the different security threats, and the different protective features, will make secure use of mobile computers a challenge - particularly when carried in public.

Fortunately, as mobile computers benefit from ongoing technological advances, improved design of mobile computers may make some limitations less significant. Improved displays, operating systems, and additional security devices are all coming. Google "Material Design" techniques will merge designs for "desktop", "laptop", and "mobile" variants of various Blogger / Google services.

As people buy and use more mobile computers, the differences between "desktop" and "mobile" computers will narrow. And use of different new desktop and mobile features, like innovative computer desktops, and products like Android Wear and Google Glass, will force desktop, laptop, and mobile computers to converge in functionality.

>> Top

Blogger Blogs Redirecting To "scmplayer . net"

This week, we're seeing a new stream of problem reports, from blog owners whose blogs are, once again, mysteriously redirecting their readers to unknown destinations.

When I open my blog, it automatically directs to another website, which is SCM Music Player.

This appears to be yet one more gadget, willingly installed by many Blogger blog owners, which is now redirecting uninterested viewers. The target of the redirection, in this case, is a website which is simply a commercial advertisement - for the product which was apparently installed, willingly, by the blog owners.

The website in question, "scmplayer . net", unlike some previous episodes of this nature, does not appear to be expired.

Overview for scmplayer.net

Registrar Info
Name  GODADDY.COM, LLC
Whois Server  whois.godaddy.com
Referral URL  http://registrar.godaddy.com
Status  clientDeleteProhibited, clientRenewProhibited,
 clientTransferProhibited, clientUpdateProhibited

Important Dates
Expires On  March 25, 2014
Registered On  March 25, 2011
Updated On  December 13, 2011

If we use a text only browser, such as an HTTP trace utility, the problem code is easily identified. Here's a redacted example, taken from the latest forum problem report.

<div class='widget HTML' id='HTML1'>
<div class='widget-content'>
<!-- SCM Music Player http : // scmplayer . net -->
<script type="text/javascript" src="http : // scmplayer . net/script . js"
data-config="{'skin':'skins/aquaOrange/skin.css','volume':50,'autoplay':true,'shuffle':true,'repeat':1,'placement':'top','showplaylist':false,'playlist':[{'title':'Waves','url':'http://youtu.be/IFS0Eo1eh6Y'},{'title':'Money Trees','url':'http://youtu.be/jSXiNdTbTA4'},{'title':'Keep it Moving','url':'http://youtu.be/XqRC_Fh--js'},{'title':'Find Away','url':'http://www.youtube.com/watch?v=KS6zq6_iMCk'},{'title':'Do your Love','url':'http://www.youtube.com/watch?v=2zVwbgXaMRo'},{'title':'Bitch Don%27t Kill My Vibe','url':'http://www.youtube.com/watch?v=OcYvaLIgjTk'},{'title':'True Livin','url':'http://youtu.be/wMFHqqiR3Co'}]}" ></script>
<!-- SCM Music Player script end -->

From what we've seen so far, identification and removal of the problem code seems to be straightforward - just access the dashboard "Layout" menu wizard, find the gadget identified, and remove it.

As always, you are advised to clear cache and restart the browser, after removal and before testing. If the gadget makes your dashboard redirect before you can un install the misbehaving code, use a well protected browser, like Firefox with NoScript, to block the redirection.

>> Top

eNom Hosted Custom Domains Again Showing Intermittent Connectivity Issues

This week, we have a few reports in Blogger Help Forum: Something Is Broken, about active and mature domains, suddenly stopped working.

I have used my domain with no problems, since last year. Today, it suddenly stopped working, and the browser reports

Oops! Google Chrome could not find www.mydomain.com.

I asked my friends about my domain - and they tell me that my blog is inaccessible to them, also. I didn't change any settings - and it was fine, until last night.

As we reported last year, the Google partner registrar eNom occasionally has a problem with their DNS server complement. Right now, one of their DNS servers appears consistently bad.

Using a comprehensive Dig tool, we can observe a given domain, and compare the DNS addresses being served by all authoritative name servers for a given domain, in a single transaction.

Here's a hypothetical example, of what we're seeing right now, for several eNom hosted domains.

mycustomdomain.com@dns1.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21
mycustomdomain.com.  1800 IN A 216.239.32.21

mycustomdomain.com@dns2.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns3.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns4.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600


www.mycustomdomain.com@dns1.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns2.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns3.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns4.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600

Right now, it appears that server "dns5" is consistently broken.

It's possible that this problem will affect more eNom customers, as the day progresses, cached DNS addresses expire, and readers of various eNom hosted domains request DNS addresses. I hope that eNom Customer Service can react to this problem more promptly than they have reacted to the immediately previous problem.

Watch for eNom acknowledged changes and problems.

• eNom: Maintenance Alerts