Using A Killfile, To Filter Blogger Comments

We periodically see hopeful - yet naive - requests from blog owners, in Blogger Help Forum: Learn More About Blogger, asking about comment moderation improvement.

How do I add a disruptive commenter to a killfile list - and never see his/her nonsense ever again, without moderating every comment, being published?

This would be a popular feature - if it could be provided, in any way that would achieve results.

Using a killfile, to filter disruptive / malicios commenters, is not a likely possibility.

Anybody who does not want to be identified can comment as desired.

It is not possible to reliabily identify a comment publisher, who does not wish to be identified.

• Blogger / Google identity.
• IP address.

Disruptive individuals can't be identified, with any chance of success. Anybody who wants to publish comments can do so, using multiple accounts, and / or IP addresses.

Both Blogger / Google accounts and IP addresses can be easily cloaked.

Using either multiple Blogger / Google accounts - or IP addresses - is a trivial exercise for anybody who is determined enough to persistently publish unwanted comments.

Given the impossibility of identifying people who don't provide effective identification, Blogger is unlikely to provide a feature that would accomplish nothing - and possibly interfere with legitimate commenting.

The only solution for blocking unacceptable comments will always involve collaborative, fuzzy filters, trained by each blog owner.

---

Some #Blogger blog owners would like to use a killfile, to filter unacceptable comments. They don't understand that anybody who wants to persistently publish disruptive or malicious comments can easily mask their identity - and make killfile use an exercis in futility.

Read More

Blogger Magic - Stats Accuracy And Consistency

One of the least understood Blogger features is the Stats visitor counters, and the various displays.

We see the confusion, in Blogger Help Forum: Get Help with an Issue, periodically.

The "weekly" Stats numbers don't add up, properly!

or

Why is "Popular Posts" so out of touch, with reality?

Magic is fun to watch, when it's just for amusement. When your numbers seem to have magical quality - changing from day to day, or display to display - it becomes annoying.

With its many lines and pages, the various Stats displays look like they could be part of one big balance sheet - but they are not.

With a balance sheet, you'll have detail lines in one page, that can be added up and reconciled against totals, in another page. This makes some balance sheet components redundant.

With Stats, nothing is redundant. Whether provided in a dashboard page, for you to examine - or in a gadget, to encourage your readers - all numbers are significant, exactly as displayed.

What you see for each day cannot be added up and balanced against a week - nor can a collection of weeks add up to a month. Nor can detail lines in "Pages" add up to totals, in "Audience".

• Components and features are provided for different purposes.
• Different dashboard pages reflect different details.
• Time periods do not begin and end equally.
• You may, or may not, be able to ignore your own pageviews, consistently.

Components and features are provided for different purposes.

The "Popular Posts" gadget displays popular posts, for the convenience of the blog readers - and there is no "Popular Pages" gadget, for people who choose to build a blog, based on static pages. The dashboard Stats pages are displays for informing the blog owner.

The (3) time range selections in "Popular Posts" also differ from the (5) selections in the dashboard Stats pages - further preventing comparison between Popular Posts and dashboard displays.

Different dashboard pages reflect different details.

The "Posts" dashboard page lists (only) the 10 most popular posts ("dynamic" pages), and the 10 most popular pages ("static" pages). "Pageviews today", and "Pageviews yesterday" reflect all blog activity - all index pages, all "pages", and all "posts" together.

Time periods do not begin and end equally.

"Pageviews today", and "Pageviews yesterday" counts are reset based on the global day - not on any local clock. Your "today" will never be the same, all days of the year - if ever. 23 / 24 of the world will never see their "today" equal to "Pageviews today", and "Pageviews yesterday".

And everybody knows that weeks, months, and years never begin and end in synch. You cannot add up weeks into months - nor months into years.

"Pageviews today", and "Pageviews yesterday" are the best known objects of confusion - but by no means the only - in the Stats data complement.



You may, or may not, be able to ignore your own pageviews, consistently.

Even given the recent improvement to the "Don't track" option, not all blog owners will be able to ignore their own pageviews. Every blog owner has their own required complement of performance and security products, which may interfere with the Stats "Don't track" code.

The bottom line.

Everybody needs to accept reality - that Stats will simply perform differently, for every different blog, and for every different owner of every team blog. Enjoy and use Stats for what it is.

---

Many #Blogger blog owners become concerned, when they add up detail Stats numbers on one display, and find the numbers do not agree with the totals from another display. They do not notice that the numbers have different origins, and purposes - and simply cannot add into any different display, with any degree of accuracy.

Read More

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

Read More

Visitor Logs Cause Undue Concern

We see periodic concern, expressed in Blogger Help Forum: Something Is Broken, over apparent visitor access to blog maintenance wizards, using the Quick Edit icons.

I found this entry, in my StatCounter log. How did this person get access to my blog?

http://www.blogger.com/post-edit.g?blogID=7834826019588534175&postID=890014875501476492&from=pencil

Was my blog hacked?

This may not be a justified reason to panic, however. One may first wish to check that Stats (or whatever visitor log is in use, in this case) is properly configured, to not track your own activity. The link that you see may reflect your activity.

Even if the visitor log entry in question does not appear to reflect your own activity - even when allowing for the vagaries of geo location, you may still do well to remain calm.

Thanks to the unpredictable nature of cache, some blog artifacts may be visible to people other than blog owners.

Cache in your browser, on your computer, or even on your network, may cause the Quick Edit icon - which provides you with access to the sensitive wizards, which control the content of your blog - to also be visible to the casual visitor to your blog. Any idly curious visitor may even click on such an icon, when visible.

However, visibility of the icon does not guarantee access to sensitive blog controls. Here's what I saw, when I clicked on the link above.

D'Ohh!!!

Maybe, you'd like to verify that your blog is safe?

1. Extract the URL, from a Quick Edit pencil, or screwdriver / wrench, on your blog.
2. Verify that the link works, by testing it in your browser. See that you can access the post editor or the wizard, for the pencil or screwdriver / wrench.
3. Save the verified URL, somewhere safe.
4. Clear cache, cookies, and sessions (yes, clear all 3!).
5. Restart your browser, and do not login to Blogger.
6. Load the saved URL.
7. What do you see?

If the above suggestion isn't interesting, I'll let you try to attack my blog.

Similar to the problem with phantom visitors reading a private blog, or maybe seeing your email address where other people can see it, or even porn sites linking to your blog, this may not be an issue to concern you. Calm down, and get back to work.

Read More

Use Free Online Website Display Services, To Diagnose Browser Related Problems

Look at the Audience display, in Stats. How many different entries do you see, in "Pageviews by Browser" and "Pageviews by Operating System"? Stats lists are limited to 10 entries, each. Do you ever wonder if those lists, like the other Stats lists, should be longer? How do we ever hope to observe our blogs, and see what they look like, for our many different readers?

One of the challenges of publishing a Blogger blog is developing a blog that looks good, on every reader's browser and computer. The number of combinations of operating system times browser brand times browser version - any of which can create a display oddity, when viewing any blog or website - is staggering.

How can we ever hope to produce a blog that's universally readable? We can always (depending upon the capacity of the computer(s) which we may use) use different browsers, to monitor ongoing issues which might affect our blog's legibility. Knowing the real number of combinations that may affect our readers, will using one or two alternate browsers (on one single operating system) really accomplish much?

One way that we can keep some running idea what our blogs look like, in different browsers, is to use an online browser display analysis service. This is an essential part of verifying proper formatting, as we make changes.

Free online services, like AnyBrowser or BrowserShots, will show you what your blog looks like, by simulating it on different browsers. Their displays, on your browser and your computer are obviously subject to peculiarities of your browser and computer, of course - but their services are a good start.

For in depth research, the W3Schools Online Web Tutorials will identify, in detail, which features are supported, in different browsers.

>> Top

Read More

Fluctuations In Stats Pageview Counts And Newer Blogs

Some owners of newer Blogger blogs spend time reading their Stats logs, and worry that their "All time" pageview counts don't always go up - they go down, too.

Why do the counts go down? Is there one number, that I can believe?

They don't understand that with Stats, you need to look for trends - not absolute readings. In the beginning, fluctuations are more obvious, and trends are less obvious.

Thanks to the referer spam war, and to normal visitor activity, even the "All time" numbers will go up and down - for newer blogs, which have less genuine and constant visitor traffic. And the constant rise and fall is scary - until you get used to it.

Newer blogs have less established readers, which makes spikes in both the periodic referer spam, and normal visitor activity, more visible.

With the 4 limited time ranges (Now, Day, Week, and Month), the spikes will "move" in and out of context - and make pageview counts in these time ranges fluctuate. When a spike in numbers "moves in" to a time range, the pageview counts will rise, suddenly. When a spike "moves out" of a time range, the counts will fall, just as suddenly.

With newer blogs, the fluctuations exert a "double whammy".

1. The fluctuations are more visible, because overall genuine visitor activity is lower. Less readers = less visitor activity.
2. Worrying over the fluctuations takes time away from working on the blog. Less time working on the blog leads to less blog content, attracts less new readers, and leads to less visitor activity.

More experienced blog owners know to use Stats to watch for trends - not immediate numbers.

The answer here is simple. Monitor Stats periodically - not constantly. Watch for trends, and learn how to interpret the trends. Spend more time working on your blog, because that's where the value of your blog lies.

Read More