Skip to main content

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.

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.