All Mobile Computers Are Not Created Equal

We've seen a few questions about comments, supposedly published - but vanishing, when using a mobile computer, in Blogger Help Forum: Something Is Broken.

This symptom, as reported, reminds us of the long ago reports of "vanishing comments" - but using desktop computers.

At least one of the folks who isn't able to comment said she was attempting to do so from her mobile phone. Is Blogger now losing comments from mobile devices?

The answer here is not quite so ominous, though the situation is still frustrating - to both the blog owner, and the various visitors.

Blogger comments are offered in three "desktop" computer styles, selected by the blog owner.

• Embedded, positioned below the posts.
• Full screen, on a separate page.
• Popup, in a separate, miniature window.

Each of these choices have their own special advantages and disadvantages, which vary in relevance, according to the blog reader population.

On a "mobile" computer - and with the "mobile" template enabled, there is yet a fourth style.

• Embedded, in a special "mobile" dialogue.

The comment entry process, in general, involves at least four distinct steps.

• Authentication. Where required by the blog owner, and / or preferred by the blog visitor, the visitor may provide personal identification.
• Entry. The comment is entered, and edited.
• Preview. The visitor can view the comment, as entered, before actually publishing it.
• Verification. Where required by the blog owner, the visitor solves a puzzle, aka "CAPTCHA", to prove that he/she is not using an automated script.

Entry and Preview goes back and forth, at the preference of the comment publisher, until satisfied.

Depending upon the "mobile" computer and template in use, any of the four comment entry styles may be a problem, for any of the four steps identified. If you are familiar with the comment entry process, in general, consider the various controls and objects involved - and when each object is presented to the visitor, attempting to publish a comment.

Consider three different possible ways of presenting the various controls and objects, involved in publishing comments.

• Everything "visible" simultaneously, with the display zoomed out so everything is visible. On anything but a large screen tablet, you would probably need a magnifying glass, to read the captions, instructions, and labels.
• Everything "visible" simultaneously, but with most objects off screen, until each is needed. Scrolling is done using finger gestures, not using scroll tabs - and it's never obvious where any "missing" objects may be, at any time.
• Everything visible in sequence, one step at a time. Extra controls, to move forward and backward in the sequence, are required. To someone not familiar with the comment entry process, in general, some controls may not be obvious.

None of these three options provide perfect solutions. Even being experienced in the commenting process, I have found no obvious excellent choice, when using a "mobile" computer.

Besides the various control and display issues discussed above, consider the effects of cookies and scripts, which may or may not be supported by any given "mobile" computer - and layered security, which is a challenge, on every computer. Both may be a special problem, on "mobile" computers.

Until "mobile" computers are developed, with controls and displays equal to (better than) to those of "desktop" computers, I suspect that there will always be problems with commenting on "mobile" computers - just as there are problems with use of "mobile" computers, and with commenting on all computers, in general.

>> Top

Reverting Your Blog Back To Blogger Comments, From Google+ Comments

We're starting to see regular evidence of dissatisfaction, in Blogger Help Forum: Something Is Broken, about Google+ based Blogger commenting.

We've known about some undesirable features of Google+ commenting, for a while now.

• No ability to moderate comments, made against your blog, before they are published.
• No ability to moderate comments, from the dashboard.
• No controls for moderation, or for notification, of comments.
• No ability to view all comments, made against your blog.
• No ability to block all undesirable comments, made by people who don't like your blog.

These are just the undesirable features which directly affect commenting.

Not every blog owner realises that anybody in Google+, able to view their blog, can make comments about their blog. Unfortunately, just as you can't see the posts made in Google+, by people not in your circles, neither can you see comments made by people not in your circles - even if their comments are published against your blog.

Deciding that Google+ comments may not be their cup of tea, some blog owners decide to revert to Blogger native commenting, and recover normal commenting features.

Reverting the blog, to use Blogger based comments, is simple enough - in most cases. From the dashboard Google+ menu entry, look for the selection "Use Google+ Comments on this blog". Un checking that selection, your blog is back to native Blogger comments. To verify success, you may need to clear browser cache, and restart the browser.

Some blog owners think that deleting their Google+ profile, or simply reverting their Blogger account, will immediately recover control of commenting. Having deleted / reverted the Google+ profile, however, the Google+ dashboard menu entry disappears - but the blog continues with Google+ based comments, and with no dashboard selection to "Use Google+ Comments on this blog".

For any blog owned by a Blogger account with a newly deleted (reverted) Google+ profile, the blog owner must now again upgrade the Blogger / Google profile to Google+, and create a new Google+ profile. With the Blogger account again using a Google+ profile, the dashboard Google+ entry, with the necessary "Use Google+ Comments on this blog" option, will be restored - and Google+ comments can be disabled.

If you decide that Google+ based comments don't suit your Blogger blog, you can recover normal Blogger comments - but please recover carefully. Always uncheck the dashboard option to "Use Google+ Comments on this blog", before doing anything else.

>> Top

CAPTCHA Verification Is Broken, For Some Blogs, In Various Applications

We're seeing a number of problem reports, in Blogger Help Forum: Something Is Broken, about various problems which involve CAPTCHA verification processes.

The symptoms are fairly diverse.

• Some blog owners report problems with commenting, on their blogs.
• Some report problems with high posting volumes.
• Some report problems getting abuse review requested, for their blogs falsely accused of hosting abusive content.

The reporting volumes, and perceived urgency, for each case, will vary.

The known problems involve various bX codes, issued in place of the CAPTCHA form.

• An unverified code is being seen, by people trying to post comments, on blogs using CAPTCHA screening.
• Blog owners are reporting various bX codes, when trying to post high volume blogs.
• Other blog owners are reporting "bX-niui1k", when trying to request spam review, from the dashboard "Deleted blogs" list.
• It's possible that there are other CAPTCHA applications, also seeing bX codes.

The audience observing the bX codes will differ - because the relationship of the people needing to use the CAPTCHA, and the volume of CAPTCHA use by the affected people, will differ.

People observing a bX code, when trying to post a comment, will be guests on blogs which use CAPTCHA screening - since blog members and owners are not subject to comment screening. CAPTCHA screening is optional for comment moderation, in general - and it's possible that many blog owners are not using CAPTCHA screening on their blogs.

It's also possible that only blogs which use the full page and popup comment forms are vulnerable, to this problem. The report volumes involving bX codes involved with comment moderation are low - and this will make affinity analysis difficult.

People observing a bX code, when trying to post at high volume, will be blog owners who post frequently. The reports of this problem are low to medium volume - possibly because many blog owners avoid posting excessively. This may be because we have observed that repeatedly solving a CAPTCHA will be inconvenient.

The people who report this problem are fairly insistent that this problem needs to be solved. Since the bX code is observed repeatedly (once for each high volume post attempted), by the blog owners affected, this case will involve the most controversy. Several blog owners have reported seeing differing bX codes.

People observing a bX code, when trying to submit an abusive blog review request from the "Deleted blogs" dashboard list, will be blog owners whose blogs were deleted or locked, spuriously, for abusive content (aka "spam hosting"). These people will post in the forums, and can be helped fairly easily, by our promptly offering a manual review, submitted to Blogger Support.

This case represents the most frequently reported symptom - but since the people affected can be helped with minimum fuss - and since this case is only observed once for each blog involved, this case will involve less controversy. This case has been reported, as noted, consistently producing the "bX-niui1k" code.

It's possible that CAPTCHAs are used in other unidentified applications - and we may yet have other cases to discuss, if the base problem is not resolved fairly promptly. Blogger Support is currently aware that there is a problem - and hopefully, where the problem lies.

>> Top

Problems Being Observed, In Blogs Now Using Google+ Comments

A few blog owners, eagerly opting to use the latest Blogger enhancement, Google+ Comments, are seeing some changes which they did not anticipate.

Even after checking all of the settings, some blogs, with Google+ Comments enabled, may not show the comment form - or may show the form, but comments may not be visible. Besides the visibility of the form, there are other changes which some blog owners don't appreciate.

In many cases, Google+ Comments, like other new features, require an updated post template. This will be seen in blogs with customised post templates, most frequently - although newer, less customised blogs also may need a post template reset.

After getting Google+ Comments working in general, some blog owners find other unexpected changes.

• Almost the entire "Comments" section, in the dashboard Settings - "Posts and comments" wizard, will disappear - though "Comment Location" will remain - and will default to "Embedded". None of these settings are relevant in Google+ Comments. On some blogs, there may be no "Comments" dashboard menu entry at all.
• There are no controls for moderation, or for notification, of comments.
• There is no ability to moderate comments, from the dashboard. Moderation is done under each post, one post at a time.
• As a blog owner, you have no special ability to moderate comments, made against your blog.
• There may be some comments, which you may not be able to moderate - but will publish against your blog.
• If you Block somebody from Following you, that person may still be able to post a Comment on your blog. When you look at the comments, you will only see

  This post is hidden because you have blocked the author.

• People without Google+ accounts won't be able to make - or view - comments (since comments are Circle dependent).
• Visibility of the comment form, as with all embedded comments, is sensitive to cookie / script filters, on the client computers.
• Comments posted outside Google Comments may not be immediately visible, though the comments remain in existence. Resetting various sections of the template may resolve this, when observed.
• If you change the blog address - with either a simple BlogSpot address change, a non BlogSpot address republishing (aka "custom domain"), or export / import - existing Google+ Comments may not remain visible, with the blog. This may be a similar problem, with URLs subject to Country Code Aliasing.
• With a blog using Google+ Comments, the Comments newsfeed will not be published. Any "Recent Comments" gadgets will be useless.
• The "Export blog" wizard, which used to export both comments and posts, will only export posts.
• The comment count, as displayed in the blog main page display, may show "0 comments" - even with comments actually present, and visible when clicking on "0 comments".
• You may or may not get email notification of comments, when comments are not shared specifically with you - even if you own the blog. Other people, who do not own the blog, may get notifications when you do not.

Fortunately, in most cases any prematurely made decisions are reversible. Go to the dashboard Google+ menu entry, and unselect "Use Google+ Comments on this blog". The blog will simply return to native Blogger based Comments. Any comments made under Google+ will not be visible to you, from the blog - but everything else should return to normal.

I've now added a Problem Rollup discussion, in Blogger Help Forum: Feature Suggestions and Feedback, where your opinion is appreciated. Please be objective.

See my test blogs Google+ Comments, Dynamic Template Test and Google+ Comments, Simple Template Test if you wish.

Click here, for instructions to revert back to Blogger based comments. Note that you will lose ability to view all Google+ based comments - though the comments will still exist.

>> Top

Blogger And Google+ Continue To Move Ever Closer Together

Today, Blogger announced the most innovative step in integrating Blogger and Google+, since sharing of Blogger posts to Google+.

The December 2011 sharing option lets us publish our blog posts to Google+. Today, Blogger added the ability to do the same - and more - with our blog comments. Like basic Google+ post sharing, Google+ Comments will be shared, and be visible, on a Circle by Circle basis.

The ability to post a comment, against a Blogger blog post shared in Google+, and have the comment publish to the blog will make for interesting comment based conversations.

There will be challenges to this feature, however. One of the most annoying problems with Blogger comments, right now, involves the embedded comment form, and security limitations caused by cookie filtering on many readers computers.

This blog uses a full page comment form, because too many of my readers need to post comments, in spite of the cookie filtering on their computer. Blogger Google+ Commenting requires use of the embedded comment form.

Google+ Comments lets you bring the following conversations together in one place, right under your blog post:

• Comments made on your Blogger blog post
• Comments on the blog post that you’ve shared to Google+
• Shared content on Google+ that links to your blog post

Readers will need a Google+ page or profile to comment on your blog.

Anybody who publishes a blog, and has readers who do not understand the reason for allowing third party cookies, will not want to use an embedded comment form - and won't benefit from Google+ Commenting, either. Until either

• Blogger resolves their "third party cookies" problem, with the embedded comment form.
• All Blogger blog readers resolve their issues with filtering "third party cookies".

Google+ Comments will have a limited audience.

Many blog owners may find a problem, in the moderation process.

Once you enable Google+ Comments, you can moderate comments within the blog post itself.

Owners of large blogs may not enjoy having to check each post, one by one, to moderate comments.

I check my dashboard Comments menu, several times daily - and see all comments posted to the blog, in one convenient place. Having to look at each post, to moderate comments, won't be as convenient.

A third challenge will come from blog owners who want everybody to be able to comment, on their blogs. Requiring a Google+ account to comment won't be widely accepted by blog owners who have readers who comment either Anonymously, or using an OpenID.

One of the benefits of Google+ Commenting will be a reduction in comment based spam. The increasingly annoying "nice blog" spam - and the accompanying security risks from having it published on our blogs - should be eliminated, from blogs using Google+ Comments.

Google+ Comments is a feature that is needed, on some Blogger blogs - but it needs to remain optional, for some time.

If you're in one of my Circles, and wish to test this new feature, see if you can comment, on my recipes blog, Chuck's Kitchen.

>> Top

If You Use CAPTCHA Screening On Your Blog, Try Publishing A Comment, As A Guest

Not all Blogger blog owners, using CAPTCHA screening to reduce abusive comments on their blogs, know first hand what the typical CAPTCHA puzzle can be like.

We're seeing a few concerned blog owners, in Blogger Help Forum: Something Is Broken, asking why they're seeing fewer comments on their blogs.

I'm hearing from people that they can't post comments on my blog. I tested, and comments are working just fine. What is the problem, here?

Not all blog owners bother to test the CAPTCHA, on their blogs - or even know why they don't see one, when commenting.

Not all blog owners, enabling Word verification in their blog commenting settings, bother to read the tool tip behind the "?".

Show word verification
This will require people leaving comments on your blog to complete a word verification step, which will help reduce comment spam. Learn more.
Blog authors will not see word verification for comments.

The simple advice

Blog authors will not see word verification for comments.

does not sink in, to everybody.

This leaves many blog owners unaware of how frustrating it may be, for their guests to comment, on their blogs.

If you're a blog owner, musing whether to add word verification to your blog, in an effort to cut down on the spamming and trolling going on in many blog comment threads, maybe you should try posting on your blog, as a guest. With "Show word verification" set to "Yes", logout from Blogger - or clear cache, cookies, and sessions (yes, all 3!) - then restart the browser, and try leaving a comment on your blog.

What you discover may not please you. Then ask yourself how many of your readers will have the patience, to solve a CAPTCHA, every time they wish to publish a comment?

As a blog owner, you have 3 settings which are used, in proper combination, to provide a safe environment for your readers to leave comments.

1. Authentication.
2. CAPTCHA Screening.
3. Moderation.

Consider using one or both of the other two options, if possible.

>> Top

Blog Readers Report Comments, Supposedly Published Using A Mobile Computer, Appear To Disappear

Recently, we've been seeing a few problem reports in Blogger Help Forum: Something Is Broken, mentioning mobile computers and problems publishing comments on Blogger blogs.

My readers tell me that they can't comment on my blog, using an iPad. Comments disappear, when they try to publish them.

As with a previously explored problem with comments on a non mobile computer, this problem may involve unfamiliarity with the publishing sequence.

The dialogue involved in publishing a comment, when using a desktop computer with a full size display and a non mobile Blogger template, is not simple. Depending upon the various commenting options selected by the owner, the publishing sequence may be even more complex. Blog owners may need to consider the additional details involved in comment publishing, when using a mobile computer.

Using Blogger on a mobile computer involves various compromises - and the comment publishing process on a mobile computer even more compromises.

• The small display size, on a mobile computer, makes finding the various controls involved a challenge. Both the small size of everything involved, and the necessity of repeatedly scrolling around the screen, looking for the controls used in comment publishing, is frustrating.
• The "mobile template" is an attempt to make up for the small display size. The mobile template puts the various controls on a series of displays, with various buttons and links used to move from display to display.

People unaccustomed to the sequence of steps involved in the comment publishing process may not see all of the controls required, when using a mobile computer. Neither the wide non mobile template, nor the deep mobile template, displays the comment publishing sequence easily. People who are not very experienced with the comment publishing process, in general, might become confused with the displays.

As an example, let's look at the basic comment entry dialogue. So simple - when you are used to it, and can see all of the components.

• On a desktop / full function display, you'll see an entry box, and a "Publish" button beneath the box. You use the keyboard and / or mouse to enter text into the box, then click on the "Publish" button.
• When the required display space is larger than the physical screen space, you'll have a horizontal and / or vertical scroll bar, indicating that scrolling is required, to locate other display content. You'll use the mouse to manipulate the scroll bars, and make other portions of the display visible.
• A mobile display will have an entry box, and an on screen keyboard. The onscreen keyboard will occupy a fixed amount of display space, with the entry box occupying the available remainder.
• The mobile display won't have scroll bars - if other portions of the display are not immediately visible, you'll use your finger to scroll around the screen. If you are not familiar with screen layout, you'll have to scroll around, aimlessly.
• The "Publish" button will be somewhere near the entry box - but depending upon screen size and orientation, may not be immediately visible. You may have to scroll around the screen to find the "Publish" button.
• People not used to using a mobile computer may be unable to find the "Publish" button. Finding other display content that may appear to replace the "Publish" button, they may be confused when their comments are not published, and report that their comments disappeared.

Both the authentication sequence (when authentication is required), and the CAPTCHA entry sequence (when a CAPTCHA is involved), when involved in mobile computing commenting, will make the comment publishing process even more complicated. The authentication sequence may be more complex, if the browser in use has a problem with Blogger authentication - and "third party" cookies.

Since most blogs are designed primarily for non mobile computer use, commenting using mobile computers may not be obvious, for a while. Many readers may simply not publish comments, to the same activity level, when using their mobile computers.

>> Top

Comments Posted, Using Google / Google+ Profiles, Use "noreply" Email Addresses

Recently, we've noted a number of complaints about Blogger commenting, in Blogger Help Forum: Something Is Broken

.My comments all use a "noreply" email address, instead of my actual email address. How do I have people email their replies to my comments?

These are people who have updated their Blogger accounts, to use a Google or Google+ profile. Neither Google or Google+ profiles provide the option to

Show my email address

It appears that, with the deployment of the new Google / Google+ profiles to Blogger, Google is making yet one more attempt to convince us to network using Google+ - and keep our email addresses to ourselves. If you moderate or monitor comments to your blog, you may have recently noticed many non anonymous comments labeled with a common email address of "noreply-comment@blogger.com", instead of personal email addresses.

People who intentionally wish to expose their email addresses in their comments will need to revert their Blogger accounts to the Blogger profile. If this is a concern for you, go to your dashboard. From the menu attached to the gear icon at the top right, select "Revert to Blogger profile", and you'll have your Blogger profile back. Then edit your profile, select "Show my email address" under Privacy, and you'll be back to sharing your email addresses in your comments.

It's likely that the noreply email addresses are being offered to keep many bloggers from, inadvertently, exposing their email addresses to email mining techniques. In remembering the long ago discovered "nice blog" spam, it's possible that "nice blog" spam was originally developed to help the spammers gather email addresses.

All that an imaginative spammer has to do is to post a "nice blog" comment, select "Email follow-up comments to me" - then watch as the Inbox fills up with follow up comments from bloggers, willingly giving up their email addresses to every stranger also selecting "Email follow-up comments to me", in that comment thread.

The people willingly providing their email addresses, to the world in general, are perfect targets for hackers later trying to brute force access to the Blogger accounts, using their email addresses.

If you decide to revert to a Blogger Profile for posting comments - or even if you don't - consider using Google 2-Step Verification, to protect your Blogger / Google account from hacking.

>> Top

The Latest Round Of CAPTCHAs Left Me Speechless

During the past week, I have seen a small handful of mentions of the latest Blogger CAPTCHA form, so I was not surprised this evening when I encountered one, in real life. In this case, where I was privileged to see these real examples, I suspect that the CAPTCHA itself was only marginally involved, as the cause of the problem being discussed, in Blogger Help Forum: Something Is Broken.

In looking at these three examples, I immediately hit "Publish" on the first two. I attempted the third, simply because I wanted to move forward with the actual problem diagnosis.

The "easy" "words" which contain "characters" in black, on a clean white background, are sort of guessable. I've seen enough of them. They suck - but they are predictable.

The other "words", in the shadow box, with noisy details - I guess represent the latest attempt to keep them from being guessable by automated processes. These, I fear, are simply over the edge.

??? After looking several times, I can see a dim "3" - so I suppose I would guess that, if I was reasonably sure that I had a good chance with the other, relatively easy "word" ("tokshous"?).



????? This one, I cannot begin to see characters. I would immediately pass on this one, every time. Even if "asuchSe" is correct for the "easy" "word" (or might that be "asuch5e"??). FAIL.



I can sort of see characters - possibly all capital letters, and a space in the middle. A guess, fortunately correct, was "AF9" (hoping that the space was not significant). And, hoping "Iflages" to be the "easy" word (that could be "If1ages", just as easily).



You get one chance with each CAPTCHA - a wrong guess, on either "word", simply leaves you looking at a different CAPTCHA. So, you have no opportunity to learn from your mistakes.

The above 3 examples show the "non easy" "word" semi visible, at least. Recently, I have seen some CAPTCHAs where the "non easy" "word" was just a black box on the screen - no content at all visible. In one case, I hit "Publish" 4 times without entering anything - simply because I could see absolutely no detail in the black box. Will your readers be that persistent?

If you are using CAPTCHA screening in the comments, on your blog, you will have to decide for yourself whether you wish to continue doing so. I removed the CAPTCHA from my blog, a month ago. Had I not removed the CAPTCHA a month ago, I would most surely have done so, today.

Were I be idly preparing to comment on your blog (for any purpose not involving me diagnosing a problem for someone), and were I to encounter these CAPTCHAs, this would simply be the last time I attempted to publish a comment, on your blog.

Comment publication I regard as maybe optional - it's no great problem (to me) if I can't publish a comment, on your blog. I have no idea what I will do, when encountering these abominations under a high stress situation, however.

1. Account creation.
2. Account / blog unlock.
3. Two step authentication necessitated re login (which I do see, regularly, when using the forums).

None of those 3 scenarios lend themselves to sitting there and guessing indecipherable puzzles, with marginally predictable outcome. Especially as my suspicion is that CAPTCHAs protect us only from the very simple hackers and spammers.

I don't use CAPTCHA screening - though I will moderate, here.

>> Top