Skip to main content

We Have To Trust Blogger

A long time ago, if we were setting up trusted hosts, in a browser trust list, we would add "www.blogger.com" to the list. The "www" alias is what would be used by any web services in our browsers.

Then Blogger rolled out New Blogger, and started using "www2.blogger.com" to separate migrated blogs from unmigrated ones. And a lot of Bloggers lost the ability to maintain their blogs, because their browsers were setup to trust "www.blogger.com".

Just recently, when Old Blogger was decommissioned, some ISPs providing access to Blogger as "www.blogger.com" again found their customers unable to maintain their blogs.

Similarly, we have to trust all Blogger content. Some security filters examine each script, one by one, to decide if it is safe to allow on the computer. If Blogger scripts have to be examined, one by one, before being allowed to run, what happens to the programs that are waiting for the scripts to run?

The Blogger dashboard involves hundreds of scripts. Some Firefox users are seeing "WARNING UNRESPONSIVE SCRIPT", because some security programs protect, by examining each script, one by one, to determine if it is safe.

Either Blogger is safe, or it is not safe - but it needs to be considered safe, on a domain basis. Not one script, at a time.
Heuristic Detection is an effective way to locate unknown threats for the most up-to-date realtime protection, but there are downsides.
Obviously this sort of scanning and analysis can take some time, which may slow-down system performance.

If we're going to trust Blogger, we're going to have to trust all content, from "*.blogger.com", or simply "blogger.com". Not "www.blogger.com" - and not by scanning content. We have to be prepared for Blogger to expand use of the "blogger.com" domain, not restrict themselves to "www*.blogger.com".

>> Top

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.