The Real Blogger Status

Everybody who uses a computer - and expects to use their computer for any amount of time - has one or more protective products on their computer. Anybody who publishes a blog, with an audience that has any need for security , is going to receive occasional reports from would be readers. I can't read your blog! My computer displays an "Unsafe website!" warning! All computer security products, unfortunately, will occasionally generate false positives. Analysing false positive malware reports is as much a part of every security product, as identifying the actual malware.

Not all blog owners can successfully add a conditional display of a template object, to their blog. Some owners carefully copy the conditional code that I provide , add it to their blogs - and it does not work (for them). In some cases, it may work, for me, when I check their work. Conditional code, that involves people in countries subject to the country specific domain redirect, won't always be comparing against "blogspot.com". People in the UK may see their blog as "blogspot.co.uk", for instance.

This blog is " blogging.nitecruzr.net ". If I wanted to dress up the URL slightly, I might tell you it's " Blogging.Nitecruzr.Net ". Either URL should work, for reading the blog, equally well - with the domain setup properly. Both blogs published to "blogspot.com" - and to non BlogSpot (aka "custom domain") - URLs are subjected to unexpected mixed case variations , from time to time.

We're seeing a few questions recently, in Blogger Help Forum: Something Is Broken , about FaceBook, and their treatment of Blogger URLs that are subject to local country domain redirection. When I share a post on FaceBook, the URL used for my blog ends with "blogspot.in" instead of "blogspot.com". Some people in Europe observe a variation. When I share a post on FaceBook, the URL used for my blog ends with "blogspot.nl" instead of "blogspot.com".

Some blog owners are seeing the recently added Country Code Top Level Domain Aliases in their visitor logs / meters, and various non Google search engines. Possibly unaware of the aliases, they are afraid that their blog has been hacked. My SiteMeter logs show that I've had incoming traffic from "mybloggerblog.blogspot.in". Clicking on one of the links in SiteMeter, I see my blog, "mybloggerblog.blogspot.com". Has somebody cloned my blog? In reality, the scenario is not so ominous.

This blog is (for those of you not familiar with it) "The Real Blogger Status". The URL of this blog is currently "http://blogging.nitecruzr.net". As long as I publish the blog properly (as "blogging.nitecruzr.net"), I am allowed to advertise the blog using any combination of lower case and upper case letters, that I like. This blog can be accessed as "blogging.nitecruzr.net", "Blogging.Nitecruzr.Net", or even "BlOgGiNg.nitecruzr.net". We say that Blogger URLs are case insensitive. Even with my readers allowed to use any combination of lower and uppercase letters, to access this blog, I don't want the search engines to index (and determine page rank) my blog using the exact URLs, as typed by each different reader. Even with this blog being addressed as "blogging.nitecruzr.net", "Blogging.Nitecruzr.Net", or even "BlOgGiNg.nitecruzr.net", the search engines index this blog as "blog...

As I've said repeatedly, Google Custom Domains depend heavily upon DNS . In the DNS server world, there are two dominant players - Windows (which is provided by Microsoft), and Unix (which is provided by many different players). Just like USA politics (the Democratic party vs the Republican party), USA leading soft drinks (Coco-Cola vs Pepsi-Cola), and other dichotomies, the differences between the players are sometimes subtle (in appearance) but major (in effect). The Windows vs Unix dichotomy has a major effect on the success of your custom domain. The BlogSpot alias for this blog is "bloggerstatusforreal.blogspot.com". That's a mouthful, isn't it?