Skip to main content

Blogger, Layered Security, And You

One of the biggest problems with Blogger, right now, is how we allow Blogger programs to run, on our computers.

Whether a problem involves Blogger / Google logins, commenting, Stats, Template Designer, or the Dynamic Templates, Blogger writes the code - and we run the code - when we allow the code to run, without interference.

If we want our computers to remain under our control, and not become part of one or more worldwide collection of computers controlled by hackers, we have to be selective about what code we allow to run on our computers.

In the computer security world, this security policy is called "Deny by default, allow by exception."

Layered Security involves filters, providing various levels of protection.

We are protected by filters, which block both cookies and scripts, in various places.

  • On our networks.
  • In applications, on our computers.
  • In our browsers.

Long ago, this was called "layered security", and was a good thing, since it helped us to keep our computers under our control. Each layer backs up the other layer, in preventing malware from being installed, or from running, on a protected computer.

Each layer of security protects you, when another layer fails or is bypassed.

Layered security is still a good thing, in general. With Blogger becoming both easier to use, and more full of features, Blogger programs, running on our computers, is more susceptible to damage from filter interference. Cookies and scripts, to be useful, must be properly permitted, by our computers.

There are many problems with Blogger, which can be caused by security settings.

When we have a problem with using Blogger


These are all problems with Blogger, possibly caused by layered security, improperly implemented on our computers or our networks. And most of these problems are ones that we need to fix, by allowing cookies to be installed, and by allowing scripts to be run, on our computers.

Similar to problems with filtered cookies or scripts is the decision that some blog owners make, to clear cookies / scripts when restarting the browser. Whether the cookies were never created, or deleted when the browser was closed - if the cookies don't exist when needed, or can't be accessed when needed, an application like Stats or Template Designer won't work properly.

Each layer has to be set, properly, to enable righteous content to be passed.

Every layer in the security strategy must be properly configured, to work with the other layers. Both cookies and scripts must be carefully considered, in the settings for each layer.


URL changes - from "blogspot.com" to a custom domain, and from "blogspot.com" to a country code alias - will cause problems with any domain based filters.

Most layered security is domain specific - and any filter which references "blogspot.com" will need to similarly reference any non "blogspot.com" domain to which your computer is subject. If you are located close to an international border, you may need to reference any nearby countries, as well.

Be selective in accessories that you install, and remember changes.

And as you install add-ons, and change various settings, keep track of what you change - and be selective of what you install. Don't let yourself be forced to sacrifice an elephant, to make your Blogger application work, later.

Know how to diagnose and resolve the problems.

If you have a problem with Blogger - either accessing / using a dashboard page, or using / viewing a blog - first check the browser cookie filters - and then check the browser script filters.

And learn the principles of affinity diagnosis, and of differential diagnosis, and of learn, as you publish.

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.