Tuesday, March 31, 2015

Stats Displays Are Significant, In Their Own Context

Some blog owners want significant details, from Stats.
How do I get all posts listed, with pageview counts?
or
How do I get a specific time period, from last month?
or
How do I filter out the bogus counts?
Not everybody observes that Stats gives us specific details, based upon what's generally useful, or what is possible to keep, easily.

Some details are not provided, because Stats provides details that are significant, in the right context. Other details are not provided, because they are not retained, from day to day (week to week, month to month, or year to year).

Some blog owners carefully check their Stats logs, daily, and copy the contents into spreadsheets, and add up all countries. Or, they add up the last weeks totals, for any one post.

They may ignore the fact that Stats provides only the top 10 entries, for any time period - and that the top 10 will change - from day to day, week to week, and month to all time.

They may also ignore the fact that Stats time periods don't, necessarily, add up into other time periods.

  • "Now" is simply the last 2 hours, at any time.
  • "Day" is simply the last 24 hours - and "Today" may be anywhere from the last 1 minute (at 00:01), to 1440 minutes (24:00).
  • "Week" is simply the last 7 days. The current "day" may, or may not, consist of the most recent 24 hours, in the "Week"
  • "Month" is simply the last 30 "days". This won't be the last 4 "weeks", exactly.
  • "All time" is what it says.

Recalculations and resets won't occur according to local clock / calendars.

At any time of the day, week, or month, this week, month, or year may include some portion of another day, week, or month. The statistics for each day, week, month, or year may or may not be reset at the same time as the day, week, or month that just ended.

"Today" does not end precisely at midnight, for 23 / 24 of the worlds population - nor does it end at midnight for the same population, 100% of the time. If you think about it, the displayed "Week" may not be exactly the last 168 hours, either. Nor is the displayed "Month" going to be the last 720 (or 744) hours (does this month have 30, or 31, days?). Each time period is simply significant, in its own context.

All Stats displays are limited to the 10 entries reflecting the highest pageviews.

Any blog of any size will have more than 10 posts - and there will always be some posts that are more interesting to the readers, and get more traffic. Instead of using displays that could be infinite in size (how many posts would be part of any given blog?), they display the 10 most significant.

All Stats displays include pageview counts affected by referer spam.

Some "pageviews" may simply be referer spam, and may not indicate actual traffic. Referer spam follows no observable pattern, it simply appears as noise.

Posts with a low (or zero) level of organic activity are just as likely to attract referer spam, as posts with a high level. And blogs with low organic activity will show devious / low level referer spam more naturally.

Referer spam causes spikes in Stats logs, both when it is attempted, by the spammers - and when it is removed, by Google.

Spikes in Stats logs are more interesting, for posts with a low level of genuine visitor activity - and for blogs, in general, with low levels of genuine visitor activity. Like worrying about ones own pageviews, worrying about referer spam is more important to newer blog owners.

Fluctuations are more significant for blogs with low reader activity.

Most experienced blog owners don't worry about their own activity, or about imaginary activity - they focus on genuine visitor activity. Similarly, more experienced blog owners focus on the posts with more visitor activity.

You cannot add counts for the most 10 significant posts (pages), and compare to any traffic source, or audience. A spike in the reader activity for a given page may, or may not, correspond to a similar spike in the audience. You cannot correlate posts to audience, and deduce that any one post is more interesting to readers in a given country.

What you can do is examine the 10 most significant countries, during the last week - or the 10 most significant posts, during the last month. Neat month, you can compare the 10 most significant posts, against totals retained from this month.

You cannot extract this months totals, from 12 months ago, for comparison - nor can you extract all posts, for today, to add up. Nor will adding anything up tell you anything useful.

Accept a Stats component or display, for what it is.

Monday, March 30, 2015

Observe The Spirit Of The Law, Not Just The Letter

We see too many problem reports, in Blogger Help Forum: Get Help with an Issue, about inconsistent content penalties.
My blog was deleted - then I got a letter of apology from Blogger. But my blog was deleted, again!
and
My blog does not contain copied content, why was it deleted?
These blog owners, and others, are complying with the letter of the law - as they see important.

Unfortunately, other blog and website owners have rights too - and Blogger will also enforce their rights - now, and in the future. To have a righteous blog, you have to remain innocent of all possible TOS violation categories.

The actual authoritative documents, to identify TOS Violations, are Blogger Content Policy, and Google Terms of Service.

If both you, and the owners of the blogs and websites that you offend, simply comply with the letter of the law, you, and your blogs, will still be vulnerable. If you repeatedly push the limits, your Blogger account and blogs will be vulnerable, as a repeat offender.

The DMCA Claim process includes a "false accusation" penalty.
Please note that you will be liable for damages (including costs and attorneys' fees) if you materially misrepresent that a product or activity is infringing your copyrights.
TOS Violation, in general, provides no similar protection - and if you offend somebody (even while staying within the letter of the law), the other party may report you.

The closer you approach the limits, the more carefully your blog must be judged - and the longer your blog will be down, while being judged. If "time" == "money" for you, the longer the blog remains offline, the more money you lose.

The FAQ, What Types Of Blog Content Are Considered Abusive, By Blogger Spam Mitigation Policy?, provides examples of known TOS Violation problems. It's not all inclusive - or final.

Very few blogs will be guilty of all of the examples, described in the FAQ - or even all possible complementary examples. If you have a large blog, with nothing but syndicated content, please don't claim innocence, of one unrelated category.
I never publish porn!
And if your blog contains monetised porn, don't claim
My content is all my own! I never steal content, from other blogs!!
Also, if your problem is with copied content, please don't just delete, when sent a DMCA notice - and please, don't repeat! Either mistake will, eventually, leave you with a deleted Blogger account.

And don't be offended if you don't get advance warning, properly delivered to your email Inbox, in time for you to conveniently remove your abusive content.

Remember, even if you are judged innocent, eventually, you may have to deal with the penalties. And similar blogs, confirmed as legitimately abusive, will subject your blog to confirmation.

Sunday, March 29, 2015

Replace "No Comments" With A More Friendly Caption

Ever since Blogger improved the comment count caption / link, they have gotten criticism.

They just replaced the vague 0 comment count, that was originally part of the link to the comment form, with a more indicative caption "No Comments" (or whatever language equivalent may apply, on your blog). But they cannot please everybody.
People think I don't want comments, what can I do?
I think the old saying
Don't try to please everybody!
applies here, in spades.

So people ask, periodically, in Blogger Help Forum: Learn More About Blogger, about template customisation.
How do I replace "No Comments" with something more reader friendly?
And the first question needs to be
Are you comfortable with editing the template?
This can be a rather forbidding question, to some blog owners.

If you don't like "No Comments" (or whatever local language variant your blog uses), you can replace the "No comments" caption with any phrase that pleases you. This may be better if your reader population is concentrated around one language - and if you are able to edit the template.

The comments link caption is accessed, in your template, as "post.commentLabelFull". You will want to find

<data:post.commentLabelFull/>:
and replace it with

Dude, hit me with a comment!
Or whatever friendly greeting you have in mind.

You'll currently find the comments link caption, in your template code.

<b:if cond='data:post.commentSource == 1'>
<span class='cmt_count_iframe_holder' expr:data-count='data:post.numComments' expr:data-onclick='data:post.addCommentOnclick' expr:data-post-url='data:post.url' expr:data-url='data:post.canonicalUrl'>
</span>
<b:else/>
<a class='comment-link' expr:href='data:post.addCommentUrl' expr:onclick='data:post.addCommentOnclick'>
<data:post.commentLabelFull/>:
</a>
</b:if>
And there is your target. Just a simple change is all you need, for most templates.

<b:if cond='data:post.commentSource == 1'>
<span class='cmt_count_iframe_holder' expr:data-count='data:post.numComments' expr:data-onclick='data:post.addCommentOnclick' expr:data-post-url='data:post.url' expr:data-url='data:post.canonicalUrl'>
</span>
<b:else/>
<a class='comment-link' expr:href='data:post.addCommentUrl' expr:onclick='data:post.addCommentOnclick'>
Dude, hit me with a comment!
</a>
</b:if>
Search diligently! Some templates may have more than one instance of

<data:post.commentLabelFull/>:
As always, I suggest that you backup the template - before and after you make this change.

Just please keep in mind that you will be editing the post template - and the post template is subject to update, by Blogger. If your change causes a problem, you may end up having to reset the post template, and start over.

Saturday, March 28, 2015

Adding An HTML / JavaScript Gadget?

Some blog owners try to add a new gadget to their blog, unsuccessfully.
When I try to add my own gadget to my blog, it won't accept it. It says
We are sorry, this gadget appears to be broken.

This gadget has errors and cannot be used until fixed.
I've seen the gadget used, on other blogs. Why not, on my blog?
There is a small problem in understanding, how to add gadgets.

Blogger lets people add HTML / JavaScript based gadgets, provided by various developers and non Google services - and they let people make their own, XML based gadgets. Some people confuse the two types of gadgets.

Most people know about adding HTML / JavaScript gadgets.

Besides the previously discussed problem with adding / editing the "HTML/JavaScript" gadget, not everybody may know to select the right gadget. Almost everybody should use "Add a Gadget", select "HTML/JavaScript" from the "Basics" tab - then add the HTML / JavaScript code made by / supplied to you.



Add an "HTML / JavaScript" gadget, using "Basics".


You can, alternately, write your own gadget, using XML. If you wish to write an XML gadget, you select the "Add your own" tab, in "Add a Gadget" - then enter the URL of the XML code.


Add an "XML" gadget, using "Add your own".

Just don't select "Add your own", if you want to add HTML / JavaScript. "Add your own" is for XML coded gadgets, that you write.

Friday, March 27, 2015

Labels Searches, And Case Sensitivity

We see confusion, from time to time, about label searches in Blogger Help Forum: Get Help with an Issue.
Why don't my labels work, consistently?
or
Why don't all of my pages work?
Looking at a blog with the problem, we'll frequently see lack of consistency in label case - some labels appear in lower case ("label"), some in upper case ("LABEL"), some in sentence case ("Label"). This might seem like an insignificant personality issue - but it's not.

Label searches are case sensitive - that is, upper case letters are different from lower case letters.

People who do not write natively, in languages which use the "Latin" alphabet (is that the correct term?) are not always attentive to case variations. We observe this frequently, with people who DO NOT UNDERSTAND THE PROBLEM WITH SHOUTING, in forum discussions.

In a label search, "Case Sensitivity" and "case sensitivity" will produce different results. Click on the two links, and check out the different results.

If you are going to use labels effectively, in your blog posts, you must be scrupulously consistent with use of mixed case.

Choose your preference when using lower / upper case characters.

Some people use all lower case letters, some UPPER CASE, others use Sentence Case, in their labels. I feel that the latter makes my posts easier to read, so that is how my labels are entered. I do the same, with my posts, and the sentences.

To illustrate the problem, I tried to labeled this post with both "Case Sensitivity", and "case sensitivity" - but was blocked, by Blogger. You can click on the example links - but one will yield no results.

Be aware of "case preservation" vs "case sensitivity".

Case sensitivity is a subject of some controversy. Some people confuse the issues of "case preservation" and "case sensitivity".

There are two competing conventions, used by the two competing server operating systems, "Linux / Unix" and "Windows" - and comparisons between the two sometimes involve discussion about "case preservation" vs "case sensitivity".

The latter issue becomes important, because both Unix and Windows servers are used in DNS and other Internet infrastructure applications. This includes applications which will resolve "blogging.nitecruzr.net/search/label/Case%20Sensitivity" and "blogging.nitecruzr.net/search/label/case%20sensitivity", as different addresses.

This issue has been explored previously, as a problem with custom domain publishing - and before that, with "FTP" Publishing.

The difference between "case preservation" and "case sensitivity" has history.

When Blogger Engineering developed labels for Blogger blogs, and added various gadgets like "Labels" (aka the "Labels Index"), they did not decide to make "Case Sensitivity", and "case sensitivity", differently unique, on a whim. It took several months, before they got all of the issues straight.

And even now, we have people who can't get their label searches correct, and try to index "Case Sensitivity" with some labels entered as "case sensitivity".

Make your own choice - and be consistent in your choice.

When you setup labels, in your blog, decide on a convention - then stick to your convention, consistently. Or, deal with the problems, periodically.



All #Blogger blog owners do not instinctively understand the "Latin" alphabet, and its conventional mix of lower and upper case characters.

Inconsistent use of mixed case can be a problem, with various Blogger blog features. Using labels is one example of this problem.

Thursday, March 26, 2015

Comments Subscription Options For A Blog

We see occasional questions from blog owners, and readers, about options for reading comments, and comment updates, from a given blog.

The most obvious way to read comments - or replies to comments - is to read the individual posts. If a blog that interests you uses Google+ hosted comments, reading either on the post, or in the Google+ stream, may be your choice.

For Blogger hosted comments. both owners and readers have a few more possibilities.

As a publisher (administrator / author / owner) of a public blog, you can subscribe to comment moderation or notification streams, by email. Note the delivery irregularities, associated with both comment moderation and notification email.

Private blog subscription options are extremely limited.

Private blogs will be relatively limited in options.

Blogger hosted comments produce newsfeeds, Google+ hosted comments do not.

Any publisher or reader can subscribe to various comment related newsfeeds, published by a blog using Blogger hosted comments. Blogs using Google+ hosted comments, again, do not publish comment newsfeeds.

With Blogger hosted comments, you may choose from several newsfeed streams - the per blog posts feed, the per blog comments feed, and the individual posts comments feeds. As a blog publisher, you may offer various subscription accessories on your blog - and as an experienced blog reader, you can select any feed, from any blog, and display it in your newsfeed reader.

The Blogger dashboard Reading List is one newsfeed reader, of many.

Blogger supplies the dashboard based Reading List - but there are alternatives to Reading List. And, there are different community building accessories - both email and newsfeed based.

FeedBurner redirected feeds offer many possibilities for comments newsfeeds.

Using a feed reference redirected to FeedBurner, you can have any feeds delivered by email - or you may view a FeedBurner reformatted newsfeed, using your chosen feed reader. FeedBurner provides a wide array of formatting and distribution options - which you, as a blog publisher, may select.

Even with FeedBurner redirection offered by a blog publisher, you may avoid feed redirection, on an individual subscription - if you choose. Alternately, you may use FeedBurner redirection - even if not offered.

The Blogger native "Notify me", a per comment selection, is popular.

Besides newsfeed subscriptions, blog readers, having published a comment, can subscribe to the comment email stream - using the "Notify me" option (for the embedded form), or the "Email follow-up comments" (for the full page and popup-window forms). Email stream delivery is similarly subject to some inconsistencies.

Know the possibilities, and create your own selections.

Complementing the various posts subscription options, there are various options which you, as a blog publisher, may offer, for comments subscription. As a novice blog reader, you may accept the options offered by the blog publisher - and as an experienced blog reader, you may create your own.

Wednesday, March 25, 2015

BlogSpot Country Domains Blocked By StumbleUpon

We've seen a few recent reports, in Blogger Help Forum: Get Help with an Issue, about problems getting StumbleUpon to accept Blogger blogs.
Every time I try to put a blog into StumbleUpon, it replies that it does not accept Blogger site submissions.
And the URL, when stated, will be a non "BlogSpot.com" country code alias.

StumbleUpon Support has provided an official response, shedding some light.

In StumbleUpon Help: Blogspot.com.[country] submissions - Unable to add, we see an Official Response.
We have, at this time, excluded content from the various blogspot.xxx country domains from being added to StumbleUpon.
If you're trying to add your blog to StumbleUpon, and you're seeing
We don't accept submissions from this site.
Just provide the "blogspot.com" URL alias for your non custom domain published blog, when submitting to StumbleUpon. That is where the Blogger traffic goes, any way. If your blog is published to a custom domain, you'll see no problem.

StumbleUpon is simply one more Internet service that does not support the Canonical tag, as used by Blogger in their BlogSpot country code aliased URLs.

Tuesday, March 24, 2015

Retrieve The PageID / PostID Of A Deleted Page / Post

I've previously provided instructions for recovering a deleted page (static page) or post (dynamic page).

Retrieval of a deleted page / post involves editing the deleted page / post, using a URL which contains the BlogID, and the PageID / PostID. It's easy enough to get the BlogID - the source listing for any blog page will have multiple places where the BlogID can be found - but where can one find the PageID / PostID?

The PageID / PostID can be found - given a small amount of effort, for any well indexed blog. Any cached copy, of the deleted page or post, will provide the PageID / PostID - once you know what to look for.

Start by knowing 3 details.
  1. BlogID. This is easily retrieved, as explained above. This is useful, for scanning a blog feed cache listing.
  2. Post Title. This is useful, when scanning a blog feed cache listing.
  3. Page / Post URL. This is necessary, for searching either an archive cache or search engine cache.

There are three major sources, for retrieval of cached blog content.
  1. Archive Cache.
  2. Blog Feed.
  3. Search Engine Cache.
If you can locate a given post in any of the three, you can retrieve the PostID, for a deleted dynamic page, easily enough. The comprehensive cache retrieval CachedView.com may be a good place to start.

The PageID, for a deleted static page, may be a bit more challenging. Static pages are not found in newsfeeds - and may not always be cached by a search engine.

Archive Cache stores and retrieves content based purely on the URL of the content. The best known archive cache would be The Internet Archive, aka the "Wayback Machine". The Wayback Machine is a search engine independent archive, with content that can be retrieved based on the URL, and content stored by date.

Multiple versions of the same URL may have been stored. When stored, the various versions are displayed for retrieval using a calendar - and a menu for each day on the calendar, when multiple versions were stored on the same day.

The PageID / PostID never changes, so any selection which yields content will do, as well as any other selection. In some cases, you will find that the archive will index a deletion - so if a given archive entry yields the well known Blogger "Deleted content" advice, search the archive for a previously indexed version.

If the URL of interest is in archive cache, simply display a cached page, and examine the page source. The PostID will be at the beginning of the post, in the source.

Blog Feed Cache uses the posts newsfeed, which is generally limited to the last published 25 posts. If you subscribe to your own blog, using Reading List or a similar newsfeed reader, you likely have the last 25 posts of your blog in cache there.

We have discovered, generally to our dismay, that deleting a post does not remove it from the newsfeed. In this case, that shortcoming will be an advantage.

Simply view the content of the newsfeed using a text based browser, and examine the newsfeed source listing. Find the post in question. The PostID will be just above the post title, in the source.

Search Engine Cache uses the post content, as cached by any available search engine. Search engine cache saves the most recent copy of any saved post, and indexes the post by URL - or many different keyword searches.

I generally use Google Search. Just type "cache:", followed by the URL of the deleted page or post, to see if the page or post is (was) indexed.

If the post is indexed, you can, like with Wayback Machine content, view the indexed page, and look at page source. And just as with Wayback Machine retrieved content, just look for the beginning of the post, and the PostID.

Once you have the PageID or PostID, just build the post editor URL, edit the page or post, and Publish.

Monday, March 23, 2015

Adding Pages To A Dynamic Template

We all know the limitations of the dynamic template - how you can't easily edit dynamic template HTML code, or accessories as freely.

At one time, you could switch back to dynamic view, for the comments and posts - and view the complete blog, using a non dynamic template. That ability was taken away, in early 2014.

That doesn't mean that you have to give up completely, however, on adding pages - though this may not yet provide a solution for a custom home page.

As with every Blogger feature, Blogger has been working on the dynamic templates.

Dynamic templates support the Pages gadget, installed in the link bar.

If your blog has been published to a dynamic template, for a while - or if you don't use the Pages index in the tab section of the blog - you may not know that the dynamic templates will now provide a Pages "tabs" menu bar. You'll see a "Pages" style menu bar on some blogs, published to a dynamic template, with the dynamic view selector in a pull down list.

If your blog, published to a dynamic template, doesn't have a pages menu, in the menu bar, you can always index the pages in your blog, from a linklist in the sidebar. Or, you can upgrade your blog. It's your choice.

First, add the Pages gadget (if not already in place).

If you want to upgrade your blog to index pages in the menu bar, use the Template wizard, and select a non dynamic view, to start. With the blog using a non dynamic template, use the Layout wizard and add a Pages gadget into the tab section of the template - or relocate the Pages linklist from the sidebar.

Remove the Views menu, if desired.

If you don't need the Views menu (which will be a drop down list), use the Template Designer "Add CSS" wizard, and add the CSS rule.
 
#views {
display: none !important;
}
 

If there is code already present, add the leading blank line above / below the new code.

Use "Configure Page List", and add dynamic and static pages.

Once you have a working Pages gadget, add dynamic (external links and label searches) and static pages - and add any gadgets into the static pages - as you like. Then, make sure that any static pages are selected, under "Pages to show".

Test the new Pages gadget, and make sure the links work.

Checkout the blog, using a non dynamic template, and make sure that the new pages (dynamic and static), and the Pages gadget, works as expected. Once you have what you like, go back to the Template wizard, and re select the dynamic template.

Return the blog to using the dynamic template, and check again.

With the blog once again using a dynamic template - and if you added / relocated the Pages gadget into the Tabs section of the template, you should now see the pages, indexed in the linkbar, just below the title section of the blog.

And consider the other possibilities, using Pages.

This still won't let you add every page feature (it does not appear that redirected home pages will display on a dynamic view) - but it should give you a few possibilities - such as adding custom gadgets, or label searches - or plain old static pages.

Sunday, March 22, 2015

Make The Stats "Don't track ..." Option Work

Some blog owners, having published their blog to their new custom domain, find that the Stats "Don't track my own pageviews" option has now stopped working - and their activity, on their blog, is being counted.

Owners of custom domain published blogs, who consider their own activity to create significant inaccuracy in Stats figures, may not be pleased to discover Stats unable to ignore their activity - even if they did previously select the "Don't track ..." option. Finding it inconvenient to locate the misbehaving filter that prevents the Stats "Don't track" cookie from being installed on their browser, they will complain in Blogger Help Forum: Get Help with an Issue.

We now see a possible workaround, for this problem.

If you can't get the Stats "Don't track my own pageviews" option working in your browser, using the dashboard Stats - Overview wizard, you may be able to create the required cookie, manually.

Copy and paste the URL below, into the address window in your browser - and substitute the URL of your custom domain published blog, for "www.mydomain.com".
www.mydomain.com/b/statsBlockingCookie?action=SET&callback=__gwt_jsonp__.P2.onSuccess
Note this cookie will need to be created on each browser and computer that you use. If your cookies are personal by computer user - as in Internet Explorer on Windows computers - this cookie will be likewise unique.

Like all cookies, the cookie created won't be permanent. If you clear cookies, you will have to recreate this cookie.

As with many Blogger problems, this workaround may not work, for everybody.

If your problem involves a misbehaving script filter, a manually created cookie may or may not be useful. A manually created Stats cookie will also provide you no help with problems with any of the many Blogger dashboard utilities - or with Commenting, or Reading List.

The manually created cookie will simply allow you a workaround, for a misbehaving cookie filter, that prevents Stats from installing a "Don't track ..." cookie on the browser in use, for the blog owner in question.

Saturday, March 21, 2015

How To Logout From Your Blogger Account

Occasionally, we see confusion in Blogger Help Forum: Get Help with an Issue?, about a rather obvious process.
How do I logout?
The blog owner, here, is not being completely facetious, or obtuse.

Many applications, on the web and in other scenarios, have a "Logout Complete" display - maybe with a link, to login, again.
You have now logged out of XXXXXXX. Thank you for visiting!


>> Login
And "Login" would be clickable, and would take you back to the Login screen.

Google, on the other hand, takes you, immediately, to the Google "One account" display, after you click on "Sign Out".

They show an empty "Password" box, and a button to "Sign in" - and that is supposed to indicate that the Blogger / Google account is now loggedout (logged out? signed out? signedout?).

In other cases, the Google "One account" display may not be shown - and the account owner may remain logged in. This may involve aggressive cookies / script filters - or possibly malfunctioning Google code.

Some people may not notice the "Sign in" button, when the display is shown - and think that they are still signed in. Others may not notice the link
Sign in with a different account
- and this may cause more confusion. And a few may have my concerns, about what they are doing - whether I should logout, log out, signout, or sign out. And in 2011, Blogger infrastructure problems prevented successful logout for some account owners.

I'll observe here, that the Navbar (when present) contains a link captioned "Sign Out", which links to
http://www.blogger.com/logout-redirect.g
With interesting prefixes and suffixes. There we see Blogger using "logout" and "sign out", in the same process. I try to use "login" / "logout", consistently.

All of this is more details, which Blogger / Google never manages to concern themselves with, when they design their glittery displays and wizards. And all of this may cause some confusion, with blog owners who are just learning to turn their computers on.

So considering all of these concerns together, it may be possible for some blog owners - particularly this with multiple Blogger accounts, unintentionally setup - to have a normal reason for confusion.
How do I logout from my Blogger?
or maybe
I can only use my new account, the old account is gone!
They're not being completely obtuse.

In some cases, having overlooked the Blogger "blind login" policy, the simplest solution may be to just logout then login, again.

Friday, March 20, 2015

Add Your Twitter Feed To Your Blog

Some blog owners, who also have activity in Twitter, would like to display their Twitter feed on their blog.

This is not at all difficult. Twitter will custom build you an HTML gadget, using a wizard in their website.

Twitter Help: How to embed a timeline explains the process.
  1. Sign in to Twitter.
  2. Go to your settings and select Widgets.
  3. Click Create new.
  4. Choose the type of embedded timeline you’d like and start to configure it:
    • For User Timeline, enter the username of the user whose Tweets you want to display.
    • For Favorites, enter the username of the user whose favorites you want to display.
    • For List, select a public list that you own and/or subscribe to in the drop-down menu.
    • For Search, enter your search query (for advanced searches, use Twitter’s search operators).
    • Make sure to select Safe mode if you want to exclude sensitive content, profanity, etc.
  5. Customize the design by specifying the height, theme (light or dark), and link color to match your website. You can also configure your embedded timeline to auto-expand Tweets containing media.
  6. Click Create widget and then copy and paste the code into the HTML of your site. You’re done!

For your blog, just use the Layout dashboard wizard, and "Add a Gadget". Add an HTML / JavaScript gadget, and paste the code from Step #6, above. Then, position the new gadget, and Save.

Look at the sidebar in my Buzz blog, for a demonstration of two of many possibilities.

Now, to complement FeedBurner / TwitterFeed, which lets you publish Blogger content to Twitter, you can display Twitter content on your blog. Just be careful, and use the Twitter content as an accessory or decoration - not as a major content source.

Thursday, March 19, 2015

Disable / Enable The Navbar, On Your Blog

Occasionally, a blog owner wants to login to Blogger from the blog - but there's no link to login.
I can't get to my dashboard! How do I login to Blogger?
The simplest solution is to just use the Blogger login link
https://www.blogger.com
Bookmark that, and you can login any time - using either a Designer / Layout, or a Dynamic, template.

A long term solution would be to have the Navbar enabled, on the blog. All blogs can't use a navbar, however.

You disable or enable the Navbar, using the "Navbar Configuration" wizard.

You can use the Navbar Quick Edit link (if Quick Edit is enabled) - or the "Edit" link for the Navbar, on the dashboard Layout page - to access the "Navbar Configuration" wizard. Either should work - when you are logged in using the right Blogger account.


Click on "Edit", for the navbar gadget.



Select 1 of 6 styles, to enable the Navbar. Select "Off" , to disable the Navbar.


For this blog, I use the "Transparent Light" style. See how nicely it blends into the wallpaper, at the top?

If your blog uses a Dynamic template, you won't have a Navbar - and you'll want to bookmark the Blogger URL to login.

Without the Navbar, you'll lack the other gadgets and links. The Dynamic template will provide you a "New Post" pencil icon, when you are logged in to the blog (only when logged in using the right Blogger account) - but only "New Post".

If the blog uses a Designer or Layout template, though, it's in your best interest (possibly your reader's best interest, too) to enable the navbar - but it's your blog, and it's your choice.

Wednesday, March 18, 2015

Solutions, To The Spam Problem, Start With You

This year, we are finally seeing the beginning of the end, of one problem, in Blogger Help Forum: Get Help with an Issue.

Spam reports - both righteous and spurious - are steadily slowing down. They are not at zero level yet, but there is a distinct decrease.

Now, we are seeing questions from people who actually can do something, about their personal contributions, to the problem - borderline spam blogs, with blog owners possibly able and willing to clean up their act.
I look in Google Search, for my blog, but it's not listed. Please help me, what is the problem - how can I get my blog listed?
This blog owner has the right attitude - if not the right training.

Some of the latest problems, like this, are simply blogs that lack original content, published by people who simply listen to the wrong advice.

One popular blog subject, with some borderline spam blogs, is wallpaper - libraries of identical photos, shared between dozens of blogs - and offered for download to various readers, for display on their personal computers.

Some blogs are nothing but pictures. There is no indexable, unique content - but there are ads.

These would be blog publishers have to understand about duplicate content - and about attracting readers and search reputation.

Somebody out there is telling people that they can "make lotz ov muny", by throwing together a blog, scraping articles and pictures, from all over the Internet onto the blog, and adding ads. Then you get paid for the ads.

You are simply a pawn in the game - and like most pawns, you are expendable. The "king" or master spammer sits back in his castle, and rakes in the bucks - while you do the work.

If you want to develop a blog, you need to write about what you know.

That's where you start. What you write about has to be unique - not the same as dozens of other blogs, offering "free wallpaper to download". What you write about may not make big bucks - but that's where you must start.

Tuesday, March 17, 2015

Ridicule By Friends Does Not Justify Blog Removal

We see occasional tales of woe, in Blogger Help Forum: Get Help with an Issue.
My friends are making fun of me, because my name, when searched in Google, comes up on a non complimentary blog. The owner of the blog has forgotten the password, and can't recover control. How do I convince Blogger to have the offending blog removed?
The answer, here, is not promising.
You can't. No laws have been broken, nor has Google TOS been violated.
That's harsh reality, that is going to happen, a few times.

One cannot judge a blog, based on humourous remarks from one's friends.

The owner of a blog, who lists public details such as name, address, and educational status, has not broken privacy laws. A blog that lists your name, and other public details, is not unlawful.

If the owner has not broken any laws - and if he is truly unable to recover access to the blog, it's probably going to stay there, for a long time. Blogger will protect that blog from theft, to their best ability - just as they protect all of our blogs.

Google can't legally censor such a blog, or delete it, because it's content is not unlawful.

We get reports daily, from people who published a stupid blog years ago - where they now need to remove the blog, because it comes up in a name search, and subjects them to bad reputation. We also get posts by people who find their blogs offline, because somebody has claimed they are illegal.

To protect against the latter, there will be more of the former.

If you feel victimised by these circumstances, you will probably need a court order, issued by a sitting judge. That will require that you hire a lawyer, and that you prove that the blog is injurious to you.

Barring a court order, Google is unlikely to do anything, because they have no way of verifying your status.

There have been too many blogs stolen from their rightful owners, or deleted by Blogger unfairly, for them to simply act on your complaint without investigation. I'm sure that this is not a pleasant reality for you to face - but that's one of the problems.

You may have to endure the ridicule of your friends, until somebody else does something stupid, when you will be ignored - and hope that your prospective employer has more business smarts than to judge somebody unfairly, based on a stupid prank, from 10 years ago.

Sunday, March 15, 2015

Your Friends Email, Stolen, Could Endanger Your Blog

One of the hottest US National news stories, this month, is about Hillary Clinton and how she endangered the security of this country by using an insecure email address.

One of her mistakes involved her having a friend who had her email address in his address book, when his email account was hacked. And that is how your friends email accounts can be used, to attack your email account.

Even if your email account is not revealed, openly, a friend - or fellow blog owner - who reveals her / his email address, can have his / her Blogger account, blog, and email account stolen. And with the possibility that you and your friend exchange emails, there is vulnerability to your email account, your Blogger account, and your blog.

The lesson that we should learn from Hillary is that your friends can be your (second) biggest mistake.

Not only is revealing your email address a security risk, having friends, who reveal their email addresses, can present a similar risk. Their mistakes can endanger your account and blogs - and your mistakes can endanger theirs.

Hillary had an advantage, that you won't have. Once she discovered the intrusion, she simply reset her email account, changed the password (we hope!) - and got back what the hacker did not destroy.

She was lucky - her hacker only wanted to "poke around", and see what he could find. Theft for ransom, a popular blog hacking scenario, is what you may experience.

If your Blogger account, GMail account, and / or blogs are stolen, don't count on help from Blogger / Google. They don't know you, personally - and to them, you could be a would be blog thief.

More than ever, we see the need for everybody to use Google 2-Step Verification. If not for your own sake, help to protect your friends.

Saturday, March 14, 2015

"Similar Posts" Gadgets, And Blog Changes

In some blogs, a popular accessory is a dynamic "similar posts" index, with image captioned links to other posts. Sometimes, the links can rival the usefulness of label lists.

"Similar Posts" is not a Blogger feature - but there are several third party services which provide this feature, generally used in blogs which consistently use photos in the posts. This feature will be more useful, with photo rich blogs - and less useful, with label rich blogs, and blogs which link to other posts in text (like this blog).

We see occasional reference to this feature, from people who are not aware of how search engines work, in Blogger Help Forum: Get Help with an Issue.
Why is my "Related Posts" display blank?
and
My "You may also like:" accessory links to deleted posts!
These blog owners are not familiar with how search engines index posts.

"Related posts", "You may also like", and similar accessories are specialised search engine indexes.

The Google "Custom Search Engine" lets you search your blog, against key words, supplied when necessary. "Related Posts", and similar features index your posts according to subject matter - then compare a post being displayed against similar posts in the blog, and display a list of 2 to 5 similar posts.

That's the difference between the Custom Search Engine, and "Related Posts" et al. The similarities are what is most telling. Each of these accessories depend upon search cache - and this dependency creates cache latency.

Cache latency means
  • If you rename your blog, the blog has to be re indexed.
  • If you delete posts, the blog has to be re indexed.
Re indexing is not instantaneous - and there is the cause of the empty gadget (following a blog rename), and links to deleted posts (following post deletion).

The larger the blog, or the more posts deleted, the longer it can take to recover from a change. Renaming a newer (smaller) blog, or deleting a few posts - and recovery can take less time than renaming an older (larger) blog, or deleting more posts.

Search engine cache is just one more detail, in the process of renaming or of deleting posts in a blog - and one more need to plan a rename, or a deletion.

Friday, March 13, 2015

The Blogosphere, And The Registrar Zone Editor

Sometimes, we see the frustration, in Blogger Help Forum: Get Help with an Issue, about custom domain setup.
I try to publish my blog to my domain, and I get
We have not been able to verify your authority to this domain. Error 14.
even when I know I have added the necessary DNS addresses. Why does Blogger ignore my addresses?
When we check, using multiple tools - such as DigWebInterface, or Kloth, or WhoIs, we see no addresses. Even, in some cases, when the blog owner is thoughtful enough to include well displayed copy of the zone editor display.

One of the biggest challenges in custom domain publishing involves registrars who use unique addressing syntax.

Any registrar is entitled to setup a zone editor, and use any syntax that they wish, to describe key domain settings.
  • Host Name ("Name" / "Label" / "Host").
  • Host Target ("Data" / "Destination" / "Target" / "Points To").
  • Latency ("Time To Live" / "TTL").
  • Record Type ("Type").
Note even the different terms used to label the settings - which exemplify the confusion.

Let's look at the Google Domains zone editor, as a reference.

Here's the Google Domains zone editor, for instance. The 4 x "A" + "CNAME" tag complement is pretty standard - but the labels and syntax, will vary, by registrar.

The "TXT" tag is my attempt to stay ahead of "SPF" email spoof filters.


The domain owner is responsible for determining the syntax used, in the zone editor provided by the registrar. If the domain owner gets the "Host Name" syntax wrong, and the zone editor adds a Host Name that does not match the host name needed, the "Dig" utility won't, intuitively suggest what host name to lookup.

This is similar to using a dictionary, to verify how a word is spelled. The "Dig" utility will only lookup the host name that is requested, using character by character matching.

If the domain owner adds the wrong host, while using incorrect syntax, all that we can learn from Dig is just what the Blogger dashboard Publishing wizard tells us,
There is no address for that host!
or
We have not been able to verify your authority to this domain. Error 14.
There is no Dig utility that will enumerate all hosts setup in a given domain. Many online Dig utilities have warnings, which forbid automated, persistent lookups.
Please do not abuse. No automated queries. No bots.

If you add a host to your domain, and 2 or 3 different Dig lookups do not find that host, it's up to you to contact a CSR at your registrar, and ask them what you did wrong, when entering the host Name and / or Target. Nobody can do this, for you.

Thursday, March 12, 2015

Anonymity And The Blog Feeds

Some blog owners have found out, to their dismay, that the blog feeds contain details about them, that they supposedly blocked from their blogs.

Blog owners, who are trying to publish blogs anonymously, have to work hard, to stay anonymous.

When you setup a new blog, you'll have a number of tasks, to remain anonymous.

If your blog uses a non dynamic template, you can carefully remove gadgets like "About Me" / "Profile", which may contain information that you don't want seen by the public. If you look at your blog, using a dynamic template - or in a feed listing - you'll see the details, that you thought had been removed, when you deleted the gadgets.

The sensitive content, like your name, is one detail which Blogger Engineering thought was being hidden, when they decided to prevent reader chosen switching from a non dynamic template to a dynamic template - in the cause of "privacy issues".

The immediate solution is to change the Blogger profile content, and remove your name and other details. But having done that, you'll find that the blog feed does not get updated, when the profile is edited.

To update feed content, in the blog, you have to shut down and restart the feed - and make changes with the feed shut down.
  1. Disable the feed, on the blog, using Settings - Other - "Allow Blog Feed".
  2. Set "Blog Readers" to "Private", using Settings - Basic - Permissions.
  3. Edit the profile, and change "Display name".
  4. Set "Blog Readers" to "Public".
  5. Re enable the feed.
  6. Publish a post.
  7. Disable the feed (if you decided it's not needed).

With the feed cleaned then refreshed, you have the best chance of feed content, in cache on your subscribers computers, being updated with your new, non sensitive details.

If you were going to shut down your feed, as in Step #7, you might wait a period of 2 to 4 times as long as you normally take between posts, following Step #5. That would give you a better chance that all current readers might update their cache, and flush out all previously published sensitive content, previously in your feed.

Of course, you might publish one last post, informing your subscribers why you are shutting down the feed.

Wednesday, March 11, 2015

Comment Moderation Conversations, In GMail

If your blog does not get a lot of comments, you may be unused to receiving multiple comments, for the same post, in one day.

If you do one day get multiple comments, in the same day, for one post, you may not be prepared for the effect of Conversation email formatting, used by GMail. When an email message is received in your Inbox, on the same day as a previous email message with the same Subject line, GMail will display both email messages as one message, in a "Conversation".

This gives you two or more email messages - such as comment moderation (or notification) - displayed under the same GMail index entry. When you click on the index entry, you will see both comment moderation (notification) messages displayed, one after the other, in the "message".

The conversation display may lead some blog owners into expressing concern, in Blogger Help Forum: Get Help with an Issue.
Why do I see one person, intercepting un published comments, and displaying them in his un moderated comment?
Some blog owners may think that a series of comments are being read, and sent for publication, by a third party - whom they may or may not know.

Long ago, unmoderated Blogger comments could be read by enterprising spammers, and mined for email addresses, unwisely included by unwary blog readers. Blogger Engineers found out about this technique, and put an end to it, right promptly.

Unaware blog owners may think, when viewing comment moderation (notification) "conversations" in GMail, that spammers have found a new way to read un published comments. And by extension, spammers are again trying to mine their comment streams, for unwisely revealed email addresses.

Fortunately, this is not the case. You're just seeing two comments in the same day, for the same post, displayed together.

Once again, get back to work on the blog - so you get more readers, and more comments. And eventually you should get used to seeing comment moderation (notification) email messages, displayed in conversations.

Tuesday, March 10, 2015

Google Domains Provides Personal Support

One of the more promising features of Google Domains - besides the ability to access the Google Domains dashboard using a normal Google account - may be a recently discovered option.
I could not make my domain work, so I contacted Google Domains Support. They provided a simple adjustment, that actually worked!
Google Domains Support appears to be available, to anyone who purchases a domain, using Google Domains.

Google Domains Support is available, starting from a dashboard link.

Just login to Google Domains. At the bottom of the dashboard, you will see "Help".

Clicking on "Help", then "Support options", you have several options.

  • Help articles
  • Email us
  • Chat with us
  • Call us

And, we see some very promising advice.

The Google Domains Support Team is available every day:
  • For 24 hours by chat and email.
  • From 6:00 AM to 9:00 PM US Pacific time by phone.


Click on "Help" at the bottom of the dashboard.




Click on "Support options".




"Thank you for using Google Domains!"




The Google Domains Support Team is available every day:

For 24 hours by chat and email.
From 6:00 AM to 9:00 PM US Pacific time by phone.



Initially, the most extensive advice, that has been described in Blogger Help Forum: Get Help with an Issue, was to

Change "ghs.google.com" to "ghs.googlehosted.com".

That simple suggestion, however, has worked for 2 blog owners that I know of.

Most recently, they have been providing immediate resolution for new domains that would go offline, sometime after being properly setup - because of an ICANN required domain lock.

We'll keep an eye on this new option, for the disappointed domain owner. And we'll continue to suggest that non USA residents wait patiently, for their chance.

Note that the Google Domains dashboard appears to be JavaScript based - so the blog owner will need cookies and scripts enabled, for "domains.google.com" - at a minimum.

Sunday, March 8, 2015

Defect In The Watermark Template Tabs Section

Occasionally in Blogger Help Forum: Get Help with an Issue, we see a report of template inconsistency, in the Tabs Menu.
Most of the tabs links work fine - the pages pop right up. The two tabs on the far right, you can't click them and they don't act as links.
When we check the published blog code, the pages gadget looks normal - the two tabs reported just, mysteriously, refuse to operate.

The easiest solution, to this problem, is just to make the tabs section narrower.
Change the tabs captions, make all of the tabs smaller, and the ones on the right will be fine.
This strategy works OK, if the pages, indexed in tabs, can be renamed. But not all owners are interested in re captioning their tabs - and some tabs can't be easily re captioned.

Fortunately, there is an easier way to fix this. The problem here is with the code, in the Watermark template - and a simple CSS fix will take care of the problem.

To correct the problem, use the "Add CSS" wizard, in the Template Designer Advanced menu, and add two rules.


.tabs .widget ul {
width: 100%;
overflow: visible;
}

.main-cap-top .cap-left {
z-index: -1;
}

Copy the above two rules, plus leading and trailing blank lines, into the "Add CSS" window. Then hit "Apply to Blog" - and test your change.

And please, as always, backup the template before and after making this change.

Saturday, March 7, 2015

Don't Redirect The Post Feed, Redirect The Reference

Occasionally, we see concern, in Blogger Help Forum: Learn More About Blogger, about continuing to serve the readers of a blog, after renaming or replacing with a new URL.
How do I let my existing subscribers read the feed, with the blog published to a new URL?
This blog owner is planning ahead - which is a good idea whenever renaming a blog.

The Post Feed Redirect is a key tool, whenever you rename or replace your existing blog, with a blog published to a new URL.

If you use a Post Feed Redirect, however, you need to add it to the old blog - or to a stub blog, published to the old URL - not to the new blog. You redirect from the old URL, to the new URL.

Don't redirect the feed, for the new URL.
But how do I serve both the readers subscribed to the old URL, and those subscribed to the new URL, if I redirect the feed?
Don't make this mistake, and redirect the new blog (URL) feed. This blog owner is taking the name "Post Feed Redirect" literally.

The name "Post Feed Redirect" is misleading. You do not use the "Post Feed Redirect" to redirect the feed - you use it to redirect feed references.

Anybody subscribed to the old feed URL has the subscription (ie, the reference) redirected, to the new URL - if you add a Post Feed Redirect to a stub blog, published to the old URL.

Look below the post, here - near the bottom of the page. Do you see
Subscribe to: Post Comments (Atom)
That is a comments feed reference. It lets people subscribe to the comments newsfeed, for this post.

Look at the main page for this blog. At the bottom of the main page, you will see
Subscribe to: Posts (Atom)
That is a post feed reference. It lets people subscribe to the blog posts newsfeed.

If I was to rename this blog, the URL of the feed would change. I could then add a stub blog, published to the old URL - then redirect the feed reference, using a PFR, for the people who are subscribed to my blog under that URL.

That's what the Post Feed Redirect does - it redirects the feed references - when you set it properly.

Friday, March 6, 2015

Use Of "Third Party" Cookies Is Not The Problem

The controversy over "third party" cookies, and filtering, continues daily.

Today, a blog owner suggests that solving the problem of inability to comment, by "requiring" each reader to un filter "third party" cookies, is unacceptable - because each reader has to take action, to solve the problem.

Another blog owner, asking why Blogger won't ignore his pageviews when visiting his blog, takes only a couple hours to read and to diagnose the problem, then dismisses the advice

That didn't really help.

Both blog owners are ignoring the actual problem.

Blogger did not create a requirement called "third party cookies". Blogger, like Google, and like most Internet services, use cookies to retain information, from each of us, as we use Blogger.

When you use your favourite website some time, for more than just viewing, look at what you are doing.

When you use Blogger, you enter data on one screen, and use it from another.

You enter data - maybe login, maybe compose a post - on one screen. You press "Enter" ("Publish", what have you), and you see another screen.

How does the information get read on one screen, then displayed, on another screen? You're using HTTP (HTTPS, what have you), to communicate with the server - and HTTP et al is a connectionless protocol. Nothing is stored on the server (so many servers, worldwide), to identify you from screen to screen.

There are two ways to identify you, from screen to screen.

There are two ways of identifying you, from screen to screen.

  • Cookie.
  • URL in stream values.

Take a look at the latter solution, first. I'm editing this post - and here is the URL that's used, by the post editor.

https://www.blogger.com/blogger.g?blogID=24069595#editor/target=post;postID=7677866552420604366;onPublishedMenu=allposts;onClosedMenu=allposts;postNum=0;src=link
What you see there is what is passed, from one screen to another. It tells what I'm doing ("blogger.g"), what blog ("24069595") and post ("7677866552420604366") I'm working on, and what context I'm in ("allposts" , or "The Real Blogger Status · Posts › All"). All of this is public details, I don't mind showing this much.

But there is secure content, that only I can use (through my browser) - that is private to me. That content is stored on my computer, as tiny encrypted files, called "cookies". Why such a cute name, for such a serious detail?

Private details - such as my account name / email address, when I logged in to Blogger, maybe my IP address or hardware address - are stored in cookies.

Look at the URLs, in the address windows, when you use Blogger.

I login to Google, using a display that runs from "google.com". The next time you login, look at the address in the browser window. You'll probably see the same.

I use the Blogger dashboard from "blogger.com". You'll do the same, when you maintain and publish your blog.

I view this blog, as "blogging.nitecruzr.net". Since you are reading this, you are doing the same. 5 years ago, you might have viewed this blog as "bloggerstatusforreal.blogspot.com" (from many countries, such as USA).

Outside the USA, you may have viewed this blog as "bloggerstatusforreal.blogspot.co.uk" (in the UK), "bloggerstatusforreal.blogspot.fr" (in France), "bloggerstatusforreal.blogspot.th" (in Thailand) - or any of several dozen other different countries worldwide, each with a complemntary alias.

Where am I going with this?

  • "google.com"
  • "blogger.com"
  • "blogging.nitecruzr.net"
  • "bloggerstatusforreal.blogspot.com"
  • "bloggerstatusforreal.blogspot.co.uk"
  • "bloggerstatusforreal.blogspot.fr"
  • "bloggerstatusforreal.blogspot.th"

These are all different domains. A cookie, created under any one domain, and read under another domain, is called a third party cookie.

You have to trust Blogger and Google, to use their services effectively.

If you are going to use Blogger, you have to trust Blogger, and Google. That includes trusting any Google domain - and allow them to create and read cookies, between domains.

And allowing Google to create and read cookies, between domains, requires that you - and your readers - allow third party cookies. This is not the same as clearing cookies.

  • Login to Google.
  • Access your favourite blog, behind a Content Warning.
  • Post a comment, on your favourite blog.
  • View your blog, without having Stats count your visits.
  • Edit a post, in your blog.
  • Preview a post, in your blog
  • Preview the template, in your blog.

All of these activities - and more - require that the Blogger script, that you (your reader) run, reads a cookie created in another domain. That is a third party cookie.

Third party cookies are not a devious plot, to violate your privacy.

Third party cookies are not an evil plot, by Google - nor should they require disclosure, in a formal banner. Even though they do, in Europe.

Third party cookies are simply a way of letting you use the many Google services - without endangering your security, by retaining massive amounts of session content in the URL, as you use multiple displays. When you (or a reader) have a problem using or viewing your blog (or Blogger), one of the simplest things to do is to check / correct cookie filters.

Thursday, March 5, 2015

Combining And Managing Multiple EMail Accounts

If you use GMail for your email, you may have seen the opportunities in GMail Settings, which let you manage and use multiple email accounts.

GMail lets you use both GMail, and non GMail, email accounts from one - or from different - GMail desktops. This lets you manage multiple email identities from one single GMail account - and gives you opportunities to cause yourself various problems.

Both problems with account / blog recovery, and email delivery oddities because of addressing confusion, can result from the ability to mix and match email addresses and email desktops.

GMail provides two Settings tabs - "Accounts and Import", and "Forwarding and POP/IMAP", which let you manage and use multiple email accounts, from one GMail desktop. It's likely that other, complementary email delivery services have similar options.

"Accounts and Import" lets you use multiple identities when sending email. "Forwarding and POP/IMAP" lets you automatically transfer email, from account to account. You can use your GMail account to either "pull" / retrieve email from any compatible email account (GMail or non GMail), or "push"/ send email into any compatible email account (GMail or non GMail), in an ongoing basis.

Using both options together, you have considerable ability to use multiple email accounts from one desktop, transparently. Like the many problems with having multiple Blogger accounts, forgetting any multiple EMail account setup can leave you with worse problems.

When you need to recover access to your Blogger account or blog, you are advised to search every email account, thoroughly, for important email. As part of a thorough search, you may be smart to also check the Settings - "Accounts and Import" and "Forwarding and POP/IMAP", for each email account being searched - if you ever use multiple account management options, with either GMail or any non GMail system.

Failure to remember past use of either account import or automatic forwarding, as part of your email account management procedures, could leave you with ongoing problems with either account / blog recovery, or addressing confusion.

Wednesday, March 4, 2015

Provide A Sitemap, To Enable Indexing Of Pages

With (static) pages becoming a popular component in our blogs, we are seeing a few queries about getting pages content indexed.

We see an occasional query, in Blogger Help Forum: Learn More About Blogger, which leads to using the new pages sitemap.
How do I get pages indexed?
Aside from the design issue, where not all blog owners should want pages indexed, there should not be an issue here.

Blogger provides two automatically generated sitemaps, for each blog. This blog has

Most blogs use the posts sitemap - and ignore the pages sitemap.

If you look at the "robots.txt" file for this blog, you see the first sitemap in use. The file for your blog, if standard, should be similar.

User-agent: Mediapartners-Google
Disallow:

User-agent: *
Disallow: /search
Allow: /

Sitemap: http://blogging.nitecruzr.net/sitemap.xml


Note the presence of "sitemap.xml" - and the absence of "sitemap-pages.xml". This blog has no indexable content, in the static pages.

If I wanted to index my static pages- and there are significant differences between pages and posts, that generally makes indexed static pages not so useful - I could add "sitemap-pages.xml", to complement "sitemap.xml".

User-agent: Mediapartners-Google
Disallow:

User-agent: *
Disallow: /search
Allow: /

Sitemap: http://blogging.nitecruzr.net/sitemap.xml
Sitemap: http://blogging.nitecruzr.net/sitemap-pages.xml



Static pages are not indexed, deliberately - but random indexing will take place.

Static pages are not indexed, deliberately - though there can be some random links that lead to indexing. With blogs, search engines index dynamic content - aka posts, deliberately.

If you publish a website as a Blogger blog, you may want the website indexed - and that is why you might use the pages sitemap.

This blog has no indexable static content.

Besides having no indexable static content, this blog has some non indexable static content. I wrote one article, which is carefully mirrored between a page ("static page") and a complementary post ("dynamic page") - which discusses the differences between pages and posts.

Were both the dynamic and static pages of that specific article to be indexed, in this blog, the search engines might levy a duplicated content penalty. Your blog may differ - and that is why Blogger provides "sitemap-pages.xml", and the option to index static pages.

It's your blog - and your choice to make.

Most blog owners will publish posts (dynamic pages) as blog content, and use static pages sparingly, as static (non indexed) accessories. Blogger, as a default, leaves "sitemap-pages.xml" out of "robots.txt" - but you can add pages, as indexed content, if you wish.

Monday, March 2, 2015

Making Threaded Google+ Hosted Comments Work

For many years, threaded comments was a frequently requested Blogger feature.

That option was finally added in 2012. When Blogger added Google+ hosted comments in 2013, threaded Google+ commenting was later added.

Threaded comments, provided as an option in Blogger hosted comments, have significant requirements. Google+ hosted comments have additional requirements - and predictably, threaded comments in Google+ hosted comments have still more requirements.

We have explored the ownership issues of Google+ hosted comments, and similarly, visibility issues.

Google+ Comments involve issues of Google+, and of commenting in general.

In making Google+ hosted threaded comments work properly, one must consider the requirements of Google+, Google+ Comments, and Threaded Comments together. And do not overlook the need for authentication - and proper cookie filtering required for commenting, in general.

Finally, to have a commenting based conversation, you need a relationship between the two parties in the conversation. That relationship, in Google+, is provided by Following, or Circling.

Non public Google+ comments involve circle membership.

Visibility of a Google+ hosted comment, when not published Publicly, requires that the person publishing a comment to have Circled anybody who will read the comment. The ability of someone to reply, in a threaded comment, then requires both parties to have Followed, or Circled each other.

Additionally, since comments (in Google+ hosted commenting) are treated as posts (in Google+ Streams), comment replies (in Google+ hosted commenting) are treated as comments (in Google+ Streams). The publisher of a Google+ Stream post (Google+ hosted Blogger comment) owns the Stream post (Blogger comment) - and controls the settings for that post (comment).

Google+ Commenting involves membership and control issues.

Ownership of a Google+ hosted Blogger comment is the opposite of a Blogger hosted Blogger comment.

With the latter, all comments are owned by the blog owner. With the former, each comment is owned by the comment publisher - except replies are owned by the person publishing the reply (who might be the blog owner, or just as likely a third party).

This complexity is one possible reason why comment moderation is a community based process.