A Deleted Post Affects The Blog Posts Feed

We've seen a few reports in Blogger Help Forum: Get Help with an Issue, mentioning mysteriously resurrected posts, appearing in email or on peoples desktop displays.

When investigated, the blog owner will observe that a new post, which had been originally published after the one mysteriously appearing, was recently deleted. Further investigation shows that the mysterious post, that just re appeared, was the 26th most recently published post.

With those two details determined, we see that the mystery involves the blog posts feed, and the deletion of a post in the feed.

The blog posts newsfeed contains the 25 most recently published posts.

At any given time, the normal blog posts newsfeed contains the most recently published 25 posts. If one of the 25 posts in the posts feed is deleted, the feed is rebuilt - and will now include the (previously) sequenced 26th post.

If a post from the 25 is deleted, the 26th post becomes the 25th.

With a post present in the feed, which was not there earlier, that post becomes newly visible. That post is then distributed, in a desktop display or in email - because its new appearance is treated as if it was just published.

It's quite simple. Email distribution detects when the feed has changed - and any item now in the feed, that was not previously there, is treated as a new item that needs to be distributed. Anybody subscribed to the feed gets the "new" post, in their feed.

It's mysterious - but obvious - when you see the connection.

Before Starting Recovery, Get Your Facts Straight

We're seeing signs that Blogger is requiring more detail, in the account and blog recovery processes.

Even when able to recover account or blog access properly - using a registered email address or telephone number - Google may ask more questions, to verify identity. Some (would be) blog owners,in Blogger Help Forum: Get Help with an Issue, report that more secrets are required.

I provided my email address - and after I got the recovery email, I was asked when the email account was setup!

and

After I gave my home phone, I was asked for a list of my other Google accounts!

Apparently, Blogger / Google Security is trying even harder, to prevent blog theft.

Blogger is being more and more selective, in providing account / blog recovery - and is requiring secrets that not everybody can remember, as easily as they wish.

Google now requires redundant secrets to verify account ownership.
Some blog owners, even after being able to use an email address or phone (text / voice) number for token transmission, are still asked to provide additional secrets. Being asked to list other Google service accounts (GMail, Picacsa, YouTube) - and to provide approximate dates when accounts were opened - is annoying a few blog owners.

An alternative here might be Google 2-Step Verification - or use of a physical devices like a USB key, which you carry with you always.

Research the obscure account history details, before you start.
If you are preparing to request recovery of your Blogger account - or your blogs - you might do yourself a favour, by doing some research, first. Either your own email accounts - or possibly your friends email accounts - can be mined for valuable details.

If you try to fly by the seat of your pants, and guess the answers, you'll be relying on your memory. If you're here because you forgot your account name or password, are you really going to trust your recollection of when you opened your YouTube account?

Eventually, Google will use stress analysis, to verify righteous recovery.
It doesn't take too much imagination, to see the recovery process judging you by how many details you get wrong - or how long you take to answer. If you make mistakes - and keep requesting recovery - repeated requests may make you look like a hacker, trying a persistent, brute force attack.

Do your research - even plan the recovery process - before you start. It may take longer to recover your account - but you'll do it in a more relaxed manner. And being more relaxed, you'll make less mistakes.

And less mistakes leads to recovery, sooner.

Shall I Move My Blog, To Google+ Hosted Comments?

Just about 2 years ago (give or take a few days), I evaluated Google+ hosted comments, based on moderation / notification options.

A few changes have been made to Blogger - and to Google+ - since then. Some changes affect usefulness of Google+ hosted comments, in Blogger blogs.

I guess to honestly evaluate Google+ hosted comments, I should decide whether to leave this blog using Blogger hosted comments - or move forward.

Periodically, I muse about changing this blog, to use Google+ hosted comments.

I think the decision, of Blogger hosted comments vs Google+ hosted comments, comes down to choice. And, what content and features do you get with one, that you do not get with the other.

Choices for control of content.
With Blogger hosted comments, you can choose comment authentication, comment form location, moderation, and notification. All of these choices give you tools to control comments, in your blog - before, or after, they are published.

Google+ hosted comments give you one choice - comment form location. Everybody authenticates using a Google+ account. Blog owners do not choose commenters, or readers, based on authentication - and have no choices for moderation, or notification.

Choices for distribution of content.
Blogger hosted comments give you a wide complement of subscription choices - using either email or newsfeeds. Google+ hosted comments have neither.

Google+ does give marginally more choice for private blogs - or at least private content distribution - though many options may not involve publishing a Blogger blog.

Control of comments, and of readers.
Google+ hosted comments use community based moderation. You have no control over comments, posted to your blog, more than any other reader of the blog (who can see the comments).

You cannot moderate comments, so you have no need for moderation email. You are notified of comments - but notification relates to who is publishing comments (and you see all of their comments, against your blog and any others targeted by those who you follow), instead of helping you monitor everybody publishing comments against your blog.

Ability to view existing comments.
You can either display Blogger hosted comments - or Google+ hosted comments - on your blog. If you choose Blogger hosted comments, you can view comments on the blog, on your dashboard, and in your email, And you can view any Google+ hosted comments, published by anybody who you follow, in your Google+ stream.

If you choose Google+ hosted comments, you can view Google+ hosted comments on your blog, published by anybody who you follow - or in your Google+ stream. You won't be able to view Blogger comments, period, Old Blogger hosted comments are gone - and there won't be any new Blogger hosted comments.

Reader community commenting options.
With Blogger hosted comments, you can have readers who can comment using Blogger (onto the blog) - and other readers who can comment using Google+ (into their and your streams), With Google+ hosted comments, you'll have only readers who can comment, using Google+.

Comments based newsfeed.
With Blogger hosted comments, you have a Blogger comments newsfeed - and some comments published into the Google+ stream. With Google+ hosted comments, you have only the Google+ stream.

Visibility of comments.
With Blogger hosted comments, you can see all Blogger hosted comments, related to the blog, on the blog, in your dashboard, and in your email (when setup). You can also see Google+ hosted comments, from people who you follow, in your Google+ stream,

With Google+ hosted comments, you can see Google+ hosted comments, from people who you follow and who follow you, in your Google+ stream. You can't see existing Blogger hosted comments - and you won't get any new Blogger hosted comments. The visibility issue causes some confusion, from time to time.

Private content distribution.
With Blogger blogs and Blogger hosted comments, and considering recent private blog access changes, private content distribution is somewhat limited - for large groups of people. Google+ - and Google+ hosted comments - will support groups of unlimited size.

The bottom line.
So having reasoned all of that out, I still see no advantage of using Google+ hosted comments, exclusively, in this blog. People who publish private blogs, with large reader populations, may see things differently.

Maybe given another 2 years, we'll look again.

Private Blog Access Now Requires A Blogger Account

Blogger recently simplified private blog access, and removed some of the ambiguity from the membership invitation acceptance process.

Previously, an invitation to a private blog involved an email message with several options. Besides the expected invitation to join (using a Blogger / Google account), one might find an option to "preview" the blog, and / or view as a "guest" (without requiring a Blogger / Google account).

Both the "guest" and "preview" options caused confusion, for both owners and prospective members.

We might see any of several problem reports, in Blogger Help Forum: Get Help with an Issue?.

• Some would be readers would be confused why their membership had stopped working.
• Other readers would wonder why they could not comment - even with other members commenting.
• Owners would be concerned by complaints from their members, about unexplained membership loss.
• Some owners would be unable to re invite members - even with the "Blog Readers" list populated by less than 100 entries.
• Some owners would be concerned by members unable to comment.

Invited members using "guest" / "preview" would find access was temporary.
All invited members might not observe / understand the difference between the "accept membership" and the "view as guest / in preview" mode. When the temporary membership expired, some former "members" would find themselves unable to access the blog.

Invited members using "guest" / "preview" mode could not comment.
Other "members", who were not actually authenticated, would find themselves unable to comment - even when able to read the blog. This discovery might cause bad reputation for both commenting, and private blogs.

Blog owners could not always re add members, once access expired.
Blog owners might receive complaints from "members" unable to access a blog. In some cases, having invited more members after the former "member" had "accepted" membership, trying to re invite the former member would be unsuccessful, because the membership invitation limit had been reached.

Blog owners might find problems with membership invitation limits, in general.
Some blog owners might intentionally use the "guest" membership as an option to provide access to more than 100 viewers - but be unable to sustain the desired "membership" level, because Blogger had changed limit enforcement policies.

Blog owners would receive complaints from members unable to comment.
Other blog owners might use "guest" membership to provide access for readers who refuse to use a Blogger / Google account - but be unable to provide ability for "guests" to comment.

All of these issues created some bad reputation for private blog membership, in general - and some unnecessary problem reports involving commenting. With Blogger having removed the unreliable guest / preview modes, some blog owners may find themselves with less ability to provide blog access to large crowds of members.

In the long run, this will be a positive move.

People who wish to distribute private information, to large groups of people, will have to use other products. Google+ has been recommended, for several years, as a private information distribution medium.

Simplified options leads to simpler code - and to a more stable product.
Blogger design simply does not support large reader communities, of content requiring restricted access. Cleanup of this option, misused by a minority, will allow Blogger to simplify their code base - and provide a better supported product, to the majority of blog owners and readers.

An owner of a private blog, with more appropriate member population, will simply have to convince all readers to accept a Blogger account, as part of accessing the blog.

A Blogger account does not have to be a GMail account!
Just remember - a Blogger account can have any valid GMail or non GMail email address. A Blogger / Google account does not have to have a GMail email address.

Press "Publish", To Schedule A Post To Publish

People who setup a post for future publication, and who work on the post for hours or days, may overlook the final step in scheduling a post.

To create a scheduled post, there are 3 steps that are essential.

1. Create and edit content. (D'Ohh!).
2. Set "Schedule", with a future date / time selected.
3. Press "Publish".

If you spend hours or days repeatedly editing and Saving your changes, it's possible that the final step may elude you. And this may explain, to some folks, why their scheduled posts don't publish.

Even with the date and time set for future publishing, nothing happens until you actually "Publish".

You can do #1 and #2 in any order that pleases you.

• Some people may make setting future publishing the last task, after the final edit is made.
• Others immediately set date and time, when they start a new post.
• Most of us simply create and edit. Somewhere in the middle of the editing / saving process, when we decide that this post will be useful, we schedule the post - then keep applying final touches.

And there are always final touches, to be made.

Having completed the edits - and having set the publishing date / time long ago, and with date / time checked and verified - it may be too easy to overlook the final step. Instinctively, it seems like a post, with a publish date set, should publish, automatically.

I set it, long ago. Why didn't it go off??!!

If you don't hit "Publish", the post remains in Draft state. Even after "scheduled" date / time has come and gone, if you never hit "Publish", there the "Draft" post sits. In Draft state, with (by now) a past date / time.

If you finally hit "Publish", after agonising over the unpublished post which is now back dated, you get a normal published post, with the "scheduled" date / time as the actual "time stamp". If you never hit "Publish", the post sits there, patiently, waiting.

Forever.

Setup A Custom 404 Not Found Display For A Blog

One of the simplest - and most user friendly - displays that you can add, to your blog, is a custom "404 Not Found" display.

A standard Blogger blog, by default, provides a terse advice, for invalid URLs.

Sorry, the page you were looking for in this blog does not exist.

Would it not be more user friendly, to use relevant slang, maybe.

Sorry, bro - that's not on!

You can do this - and more - with a little imagination.

Blogger gives us a Custom "404 Not Found" display, similar to the customisable comment form message.

Using the "Custom Page Not Found" wizard at Settings - Search preferences - Errors and redirections, you just click on "Edit", and add simple text.

Sorry, bro - that's not on!

That's slightly more interesting, than the default.

The default is boring - and confusing.


Boring - and slightly confusing. Why do I care about "pages"?



How about some bling?


Make the message more relevant, easily enough.


Slightly better!
You can see this tweak, live, in my test blog.

A bit of simple HTML, and you can have something somewhat shinier.

With slightly more effort, we can have something much more interesting.

<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcihmX3DFk2ol3B8Zayl2pKtN3FIIXp5FNqrgWRkAyotXq5gBnkPoQEyRTfTJlesboLWPT7Y7DnyA7wJr6HLAKx0ihbWlrGnXKZvEDhQF_PKAtDNPt-DQ9tHJ4ZjRqQ5_oPKemHrRAdaJr/s400/404%5B4%5D.png" /><br clear=all />Sorry, bro - that's not on!<br /><br />Try the <a href="http://blogging.nitecruzr.net/p/topics.html">Topic Index</a>, instead.

You can see this tweak, live, in this blog.


Now, we're getting somewhere!
It all depends upon the limits in your imagination - or your ability to use Google Search. This example, here, may be a bit off the wall.

If you think about it, a custom 404 page is a good complement to a "Welcome" post, in a stub blog. You can link to an index of the posts, in the new blog, for instance. Similarly, if you migrate a non Google domain, into a Blogger blog.

Push The Limits, Expect Repeated Spam Classification

We're seeing a few blog owners, in Blogger Help Forum: Get Help with an Issue, admitting to casual / multiple TOS offenses.

I have received many DMCA complaints - and I always sort them, as soon as possible. This time, my account was disabled.

How do I get my account back?

Here, there may not be an easy answer.

Blogger does not send out violation notices, so you can just stop what you're doing, when warned by the Policy Review team. They want you to stop what you're doing - and not do other things, that you're doing, that have not yet been detected.

Blogger is trying to eliminate abusive activity, such as copyright violation and spam.

They don't send out DMCA or TOS Violation notices to have you simply remove specific offensive material, from one blog - they send out notices as examples of what behaviour is not accepted, so you can clean up your act.

As they put chronic abusers - such as copyright violators and spammers - on notice, they are tuning the abuse filters.

Fuzzy and heuristic abuse filters will examine your blog, and similar blogs.

The anti-abuse filters are fuzzy, and heuristic.

• When individual blogs are reviewed - and confirmed as abusive, the filters adjust to detect more blogs similar to what was just confirmed. That's "fuzzy".
• When individual blogs are reviewed - and restored as not abusive, the filters adjust to avoid detecting blogs similar to what was just restored. That's "heuristic".

Similar blogs, being reviewed, will make the status of your blog cycle.

If your blog pushes the limits, with features and techniques that are borderline acceptable, the blog status will cycle from "abusive" to "acceptable" to "abusive", repeatedly, as similar blogs are reviewed, and either confirmed or restored.

In some cases, you may have your blog reviewed, and restored - and see it deleted again, later. Since the blog won't be whitelisted, you'll have to get it reviewed, again. It may, or may not, be restored the second time.

If you get repeated abuse / DMCA / spam violation notices, it's up to you to figure out what content / features are borderline acceptable - and remove whatever is causing the problem.

The repeated review cycle will take longer, each time.

If you don't remove what is causing the problem, and you keep stretching the filters, you'll be back in the forums, over and over, asking for help.

Each time that you request review, it will take longer to get reviewed, as the account / blogs are subject to more intense scrutiny. Blogger Policy Review staff want to tune the filters properly, so they look at the blogs more carefully - and that takes longer.

The repeated review cycle will eventually end.

Eventually, one of two things will happen.

1. You will figure out what blog features are borderline acceptable, and remove them. Your blog will cease being a problem, and the cycle will end.
2. Whatever blog features are borderline acceptable will be re defined as a legitimate spam characteristic. The next time your blog comes up for review, it will be confirmed as a spam host, and the cycle will end.

Presumably, you want #1 to happen, before #2 happens.

If You Give Your Friend Control, It's Not Your Blog

Have you ever heard the old saying

I had a friend, and I had a blog. I gave my friend control of my blog - and now, I have neither a friend, or a blog.

If you have a blog, and it's yours alone, then it's yours - for eternity, or until you give up control. When you make your friend a blog administrator, you give up control of the blog.

If you give a friend control of your blog, and he (she) decides to remove you from being an administrator, the blog becomes her (his) property.

You give someone else control, and you have lost control.

Once you give up control, and somebody takes control of your blog, it ceases being your blog. Blogger can legally do nothing to assist you, your only recourse is with your (former) friend.

Disputes over blog ownership

Blogger is unable to mediate disputes over ownership.

A blog ownership transfer is final - regardless of the motivation behind the transfer.

A custom domain published blog has intriguing possibilities.

If the blog is published to a custom domain URL, the published domain URL is now under your friends control, in Blogger. You can change or delete the domain address, using the registrars zone editor - and that will stop the blog from working.

Changing the domain setup won't get you either the blog, the BlogSpot URL, or the domain URL - so you can re use either, in Blogger.

As soon as you setup a new blog, and try to publish the new blog to the domain, you'll see another (not!) old friend

Another blog is already hosted at this address

or

Key already exists for domain ...

Without publishing the Blogger blog back to BlogSpot, before you kill the domain, you will break the Blogger / Google database entry for the domain. And only your (former) friend can publish back to BlogSpot.

You lose both your blog, and your friend.

You can stop the blog from working - but it will be a pyrrhic victory. Neither of you will be able to re use the domain URL - and you will have neither a blog or a friend.

Setting Up DNS Addresses For Custom Domains

One of the biggest strengths of Blogger custom domain publishing is its ability to work with (almost) any registrar in the world.

The biggest strength is also its biggest weakness. The weakness involves language and syntax, as used by each different registrar.

There are no absolute terms used, when diagnosing DNS addressing problems. That is one of the challenges, that I face daily, when telling people why their domains do not work.

When you setup your domain, you use the zone editor to add the needed DNS addresses.

The "zone editor" is the DNS dashboard, that's provided by the registrar. Each registrar has their own zone editor - and each zone editor will work differently. That's one of the challenges.

Access to the zone editor, for your domain, is your responsibility.

If your domain has a problem, and the diagnosis of the problem involves DNS addressing changes, you will need access to the zone editor.

The people in the forums, and using various other online services, will patiently walk you through the task of correcting any DNS addressing mistakes - but any corrections will require zone editor access, by you.

You are the owner of the domain - and it's up to you, to get instructions from your registrar.

• How to access the zone editor.
• How to use the zone editor.

This part is your responsibility, nobody can do this for you. Just as we advise people to never share their Blogger account, we similarly advise you to never share your domain owner account.

We'll use my domain as an example, in this discussion.

Let's look at my domain, and how it's setup. Your domain, no matter what registrar you use, will require similar setup. You'll benefit more from this example, if you understand how to read a Dig log.

A Google Domains hosted domain, for those blog owners able to use Google Domains, will have a different menu / zone editor - but the end results will be similar.

1. The base DNS addresses needed.
2. A Dig log, showing the base DNS addresses.
3. Zone editor displays, showing the base DNS addresses.
4. What comes next?
5. The verification DNS address needed.
6. A Dig log, showing the verification DNS address.
7. Zone editor displays, showing the verification DNS address.
8. Different zone editors have different peculiarities.
9. A typical domain ownership verification "Error 12" display.
10. What comes last?

The base DNS addresses needed.

Here is the DNS address set, for my domain "nitecruzr.co.uk", presented as a Dig log extract.

If I am helping you, in the forums, this is what you will see, as a reference. The Dig log extract, for your domain, will probably be accompanied by a link to this article.

nitecruzr.co.uk. 3600 IN A 216.239.32.21
nitecruzr.co.uk. 3600 IN A 216.239.34.21
nitecruzr.co.uk. 3600 IN A 216.239.36.21
nitecruzr.co.uk. 3600 IN A 216.239.38.21
www.nitecruzr.co.uk. 3600 IN CNAME ghs.google.com.

Your domain, whatever the name, will need this same address set, when published in a typical Asymmetrical DNS Configuration. If you are able to setup this configuration in your domain, you will have the beginning of a properly setup domain.

99.99% of the blog owners, who need help, will be using an asymmetrical DNS configuration. There are two additional address models, which are supported - though seldom in use when help is requested.

• Symmetrical DNS Configuration.
• Additional Virtual Host Configuration.

A Dig log extract is a versatile way of displaying DNS addresses - either to show what is needed, or what is currently in effect. It is the most universally seen display - and is independent of formatting and syntax oddities, which are part of every registrar zone editor.

You can compare the Dig log extract (above), to the full Dig log, and to the zone editor display (both below).

A Dig log, showing the base DNS addresses.

Here is a Dig log for my domain "nitecruzr.co.uk".


A Dig log, provided by DigWebInterface, is one diagnostic reference.

There are dozens of Dig variants. This is the one that I use, whenever it's available.


The Dig URL, for my domain:

http://www.digwebinterface.com/?hostnames=nitecruzr.co.uk%0D%0Awww.nitecruzr.co.uk&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

You can make the same for your domain, just substitute YourDomain for nitecruzr.co.uk, twice.

Zone editor displays, showing the base DNS addresses.

Here are three zone editor displays, provided by my registrar, right now, for "nitecruzr.co.uk".


The zone editor display.

The entry panel for one domain root host.

See "Host", and "Points to"?


The entry panel for the "www" host.

See "Host", and "Points to"?

Compare this entry with the "qxdktlteaotv" host, below.


Note that here, "Hosts" will (almost) always be "www" - and "Points To" will (always) always be "ghs.google.com". Compare this consistency with "qxdktlteaotv" and "lojlkodbmryyvc" (below).

What comes next?

Having setup the base DNS addresses properly, it's time to publish the blog, to the "www" host. With the asymmetrical DNS configuration, the "www" host is the normal target.

Sometimes, the blog will publish.


Sometimes, immediate success!
If your blog publishes successfully, see "What comes last?".

In many cases, you'll have to add a verification DNS address.


An example of the infamous "Error 12".
You may get an "Error 12" - or a similar error value - if domain ownership verification is necessary.

The verification DNS address needed.

Here's the DNS addresses needed, for my domain, with the ownership verification entry added. Do you see the entries for "www" and "qxdktlteaotv" - and how they complement each other?

nitecruzr.co.uk. 3600 IN A 216.239.32.21
nitecruzr.co.uk. 3600 IN A 216.239.34.21
nitecruzr.co.uk. 3600 IN A 216.239.36.21
nitecruzr.co.uk. 3600 IN A 216.239.38.21
www.nitecruzr.co.uk. 3600 IN CNAME ghs.google.com.
qxdktlteaotv.nitecruzr.co.uk. 3600 IN CNAME gv-lojlkodbmryyvc.dv.googlehosted.com.

Some people may refer to "qxdktlteaotv" as the "short token", and "lojlkodbmryyvc" as the "long token", when discussing ownership verification. "gv-lojlkodbmryyvc.dv.googlehosted.com" then becomes the "long token" URL.

If you need to add the second "CNAME", copy and paste the long and short tokens, with extreme care. Don't trust your eyes - or your fingers. One mistake will prevent verification.

A Dig log, showing the verification DNS address.


The Dig log.

See the entry for "qxdktlteaotv"?


The Dig URL, for my domain:

http://www.digwebinterface.com/?hostnames=nitecruzr.co.uk%0D%0Awww.nitecruzr.co.uk%0D%0Aqxdktlteaotv.nitecruzr.co.uk&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

You can make the same for your blog, just substitute YourDomain for nitecruzr.co.uk, thrice - if you get the short token for your domain, correctly inserted.

Zone editor displays, showing the verification DNS address.


The zone editor display.

See the entry for "qxdktlteaotv"?


The entry panel for the "qxdktlteaotv" host.

See "Host", and "Points to"?

Compare this entry with the "www" host, above.


Please note that "qxdktlteaotv" and "lojlkodbmryyvc" is merely an example, here. Compare this with "www" and "ghs.google.com" (above).

Your domain will use different "Name, Label, or Host", and "Destination, Target, or Points to" values.

Different zone editors have different peculiarities.

Every different registrar provides their own zone editor - and every different zone editor will have their own syntax, used when entering the "Host" and "Points to" values. You - and only you - have to accept responsibility for dealing with the syntax peculiarities of your registrar.

Please note that not all zone editors will even label "Host" and "Points to", as "Host" and "Points to".

Also, please observe the "TTL" value. For this registrar, TTL is "1 Hour", or "3600 Seconds". TTL is a tuning factor, set by the registrar, to make their name servers (which support your domain) run as smoothly as possible, across the entire world. If your registrar provides a default TTL, I highly recommend that you use that value.

A typical domain ownership verification "Error 12" display.

Look at an example of the notorious "Error 12" display. Note the pair of column caption triplets.

• Name, Label, or Host field
• Destination, Target, or Points To field

Those captions are not gratuitous or imaginary - each one is used by some registrar, in their zone editor. Your registrar may use one of the three.

It is possible that some unknown registrar may use even another different caption or two. As I said, there are no authoritative terms used.


An example of the infamous "Error 12".
See the captions, heading the columns - "Name, Label, or Host field" and "Destination, Target, or Points To field"?

Here you see an example of the ambiguity - and why custom domain diagnoses, and this article, are so pedantic. I use Dig log syntax, to describe necessary settings. Dig logs are registrar agnostic.

The language and syntax, and the screen prints, used in these examples, may help you - or it may confuse you. If the latter, my apologies. The confusion is part of the challenge. You may need to document your domain, providing similar detail.

Many registrars change their zone editors, periodically. Mine seems to change theirs, at least yearly. You should learn how to use the zone editor - not merely where to click and what to type - if you are going to own and maintain a domain, for any amount of time.

This article provides examples of what you might see.

• In the zone editor, provided by this registrar.
• In the zone editor, this month.

Next month, or if you have a different registrar, you may see a different set of displays. Learn how to read and use the displays - not what you should expect to see, and what to type.

Start by asking your registrar for their zone editor instructions. If you ask for help later, in Blogger Help Forum: Get Help with an Issue, providing a link to the instructions would be a huge help.

When you buy your domain, you can use the Blogger instructions as a general guide. But get detailed instructions, from the registrar, too.

What comes last?

If you just made address changes based on my advice above, allow for the DNS Latency period. Double the DNS value - and wait for that time period, to give your domain changes a chance to be established worldwide.

If the domain verification DNS address was just added, try to publish the blog to the "www" address. And don't forget to redirect the domain root, to the "www" host!

If the blog is now successfully published to the domain, start migration activity.

If you continue to have a problem, read my troubleshooting guide, Troubleshooting Your Custom Domain Problems.

Make Your Own "About Me" / "About Us" Gadget

One of the easiest improvements, in a Blogger blog, is customising the "About Me" / "About Us" ("Contributors" / "Profile") gadget.

The default gadget gets its content from the Blogger profile - and is edited, using the Blogger Profile Editor. With a team blog, the gadget changes to a list of team members - and this cannot be edited.

But given 15 minutes, and some imagination, you can make your own Profile gadget.

The Profile gadget can be easily replaced by an HTML / Text gadget, with content of your own choosing.

Start with an HTML gadget, and contents of the current gadget, edited.

Just add a standard HTML / Text gadget to the sidebar, and fill it with content about you, or the team. For a simple start, just copy the current content of your Blogger or Google+ profile - or the current team roster, with links to individual profiles.

Having created an initial Profile gadget, spend some time and edit what you have. Whatever option you found lacking yesterday, in the default gadget, is now available to you.

Or compose an HTML gadget, using page editor, and Compose mode.

You can use the "HTML" Mode to enter simple HTML and text, or the Rich Text editor. If you really want to go for it, use page editor.

1. Compose your profile using the page editor, in Compose mode.
2. Toggle into page editor HTML mode.
3. Copy the contents in HTML.
4. Return to the gadget editor, in HTML mode, and paste.

Or even publish your profile, as a static page.

Besides adding a sidebar gadget, you can always write "About Me" / "About Us" as a new static page - and link to the page from your new gadget. There's much more room for imagination, in a full page display.

Just be aware, when you edit an "HTML" / "Text" gadget.

Just use caution when creating and editing an "HTML / JavaScript / Text" gadget.

• Select an "HTML" or "Text" gadget, from "Basics" - don't use "Add your own".
• When you edit the gadget, know how to select "HTML" or "Rich Text" mode.

HTML / Text gadgets are not the only possible solution.

If you want, you can produce profile content using any combination of gadgets. Google+ Badge, Image, and LinkList gadgets can all provide parts of a "Profile" section in the sidebar - if that's what you think can provide a description of who you are, and what you do. What matters here is what describes you, to your readers.

Other than the two cautions, the limits are probably in your imagination.

SEO Your Blog With Content - Not Header Sizes

With a static website, you use different sized headers to indicate sections of each page - and how important each section may be.

That helps your readers search each page, and makes them happy - and making your readers happy increases SEO.

With a Blogger blog, what makes your readers happy increases SEO, also. With a blog, you make your readers happy by providing content, for them to read. And you make them happier, by organising the content.

Your blog is organised by posts - and your posts can be dynamically grouped.

You don't need large and small headers, to indicate relative importance of a section of page. With a blog, you have multiple groupings, and content titles.

A website has only static pages. A blog has both dynamic pages (aka "posts"), and static pages (aka "pages") - and both may be indexed, and contribute to SEO.

A static website page can be viewed as a dynamic blog page, in different ways.
With a Blogger blog, each post can be the equivalent of a single section of a static website page. You can view the posts dynamically, in dozens of combinations.

• Most recent posts. The home or main page.
• Older posts. Archive retrievals.
• Related posts, in many groups. Keyword / label searches.
• Single post. Each individual post page.

You make the pages dynamic, depending upon how the reader chooses to read the posts.

You can eliminate most recent posts, using a static main page - or de emphasise most recent posts, using jump breaks. If your posts are not relaxant to the date, you can change, or hide, the dates of the posts.

Your readers can search your blog, using keyword and label searches. Give them the choice.

Your readers don't need large and small headers, they enjoy content. You should do, with your blog, whatever makes the blog look good. And write content, which makes your readers happy.

"SEO" comes from your readers. Google will reflect "SEO" - not determine it.
With static content, as you get in WordPress, you need relative header sizes, to indicate what sections of a display page are more important. You can only do so much, with a static web page.

With dynamic content, as you have in Blogger, each blog owner and reader can make their own decisions. Each blog owner can style their content, dynamically - and each reader can read the content, as they wish.

You can emphasise sections of pages, dynamically.
If you decide that the posts are more important, in a label search, you can add code to the template, to make gadgets - or the entire sidebar - disappear.

That's a way of making the labels index less important. You could use that same principle to make various gadgets less important, on various pages.

With dynamic content, you don't need to limit yourself to changing Header Sizes. You can make whole sections of content appear or disappear, depending upon what page the reader is viewing.

Be thoughtful. Make each page easy on the eyes.
If you're looking for a quick fix to your blog, you could use "H2" for post titles - and "H3" for gadget titles, and for titles of sections, within posts.

Since multiple "H1" on one page will confuse your readers, there is a reason to not use "H1" for post titles. Multiple "H1", in an index (archive / keyword / label / main) page, will not create a pleasant experience.

Google indexes content in posts, and optionally, in pages. The content of the gadgets is only interesting to human eyes. "H1", "H2", "H3" is all the same, when separating gadgets and posts, to Google.

Remember why you publish a Blogger blog.
Keep it all in perspective. Write for your readers. Let Google index the blog, based on what your readers enjoy.

The EPP Code - Key To Any Domain Transfer

Every domain transfer - from one owner to another, or one registrar to another - starts with obtaining then providing the EPP code for the domain.

The EPP code is an ownership certificate, similar to the mysterious second "CNAME", used by Blogger to verify domain ownership. You get the code from the current registrar - and pass the code to the new owner or registrar.

Whether you are moving your domain registration from Blogger to another registrar. or maybe moving from another registrar to Blogger, passing the EPP code to the new registrar is essential, in having the potential registrar accept registration.

Providing the EPP code, as part of a domain registration transfer, ensures that only the legal domain owner can initiate a transfer.

You can keep your domain under your control - or pass it on.

Your domain remains your domain - or permits you to, conveniently and deliberately, pass ownership to another person.

No matter the reason behind the registration transfer.

• A Blogger custom domain, being reused as a non Google website.
• A non Google website, being reused as a Blogger custom domain.
• A different registrar, for the same domain use.
• A new domain owner, using whatever registrar desired.

The EPP code is an essential component. in the transfer.

The EPP code is a 6 to 16 character code, assigned by the current registrar. You simply need access to the dashboard wizard, for the current registrar, to obtain the code.

1. Update all contact information, for the domain. Up to date email addresses are essential.
2. Follow instructions of the current registrar, to obtain the EPP code.
3. Pass the code to the new owner or registrar. You may use email, or a website form, as instructed.
4. You, or the current domain contact, may receive email requesting transfer verification. Correct and unfiltered email is essential.
5. Wait, while the current and new registrar, complete the transfer.
6. If you are transferring your domain to a new registrar, and retaining ownership, follow their instructions to complete registration.

Both "Transfer Out" (from the current registrar) and "Transfer In" (to the new registrar) procedures will be different, for every registrar.

If you plan to pass control in the future, find the code, now.

Note the advice from WikiPedia.

When getting a new registrar, it is prudent to locate the auth-info code and procedure early. Registrars may assume your only interest in the code is so you can take your business away, and might impede your getting your code when you have only a few days left before losing your domain.

It's best to be prepared, in advance. Obtain detailed instructions - "Transfer Out" (from the current registrar) and "Transfer In" (from the new registrar) - before starting the transfer.

Review both sets of instructions, together. Verify that you can do both procedures, in proper sequence.

Providing the EPP code is simply one step, in the process of changing domain ownership, or moving domain registration.

The new owner can keep the domain as is - or move it elsewhere.

With the domain in the hands of a new owner, that person can leave the domain as it is - or transfer to another registrar. With the domain in the hands of the new registrar, somebody needs to setup the domain - then to setup the DNS addresses, as required by the current / new service.

• Using a domain, with Blogger.
• Using a domain, with a non Google service.

Just understand how, and when, the EPP code must be provided - because that is the one constant, between you, a new owner, the current registrar, and / or the new registrar.

A Cookie Is Simply Data, Used By A Website

If you're a repeat customer at some restaurants or shops, you may notice that your return status is appreciated by the staff.

Maybe the coffee shop will make your coffee extra strong, or the waiter will bring you your meal a little more promptly, because they recognise you - and want you to know that they appreciate your patronage.

As you surf your favourite blogs and websites, you may notice similar treatment. Being recognised as a return "customer" is frequently flattering, and may encourage you to return yet a third, fourth, ... time.

Out of the millions of Internet "customers", your favourite blog or website recognises you - and makes your visit a little less impersonal. But how does this happen?

Many websites record your visit - and store records of your visits, on your computer.

Your visits are stored, in each browser, on each computer, in tiny files called "cookies". It's such a cute name, for such a serious feature. And it's a feature mistrusted by some countries - now with an automatic Blogger blog banner notice.

Cookies let you login only once - even if returning, repeatedly.

When you publish a comment, on some blogs, you may notice that you are required to login, to post a comment. Returning later, you may not have to login, again.

Cookies let you store comments, even as you interrupt to login.

You may spend time carefully composing a comment, then hit Publish. If you are not logged in, you may have to do so, to continue. For most people, after you login, you come back to the comment entry screen, hit Publish, and you're done.

Where did your comment stay, while you were logging in? For that matter, how did the comment script know, after you had logged in, who you were? How you login determines what icon goes with the comment, when published. Maybe you've noticed that, from time to time.

Cookies store data, from one screen to the next.

The answers to all of these questions is "cookies". The comment, between entry and publishing, was stored as a cookie. And your identity, provided when you loggedin, became part of your comment - after it passed as a cookie.

The comment text is stored as a "first party" cookie - because the cookie is created, and read, under "blogger.com". Your identity is determined under "google.com", when you login - and is made part of the comment under "blogger.com", when you finally publish. Your identity is stored - and passed - as a "third party" cookie.

That is all that cookies are. Website data stored, on your computer. Even the evil "third party" cookie is stored data - just data created under "google.com", and read under "blogger.com".

The problem with "third party" cookies involves data created under one domain, and read under another less trusted domain. But why are you surfing, to a website that you can't trust?

Let large websites remember your visits - make life simpler.

If you want to use Google, and other large websites, effectively, you have to allow them to store data on your computer - and retrieve the data, later. And that is how cookies are used.

To own - and operate - a Blogger blog, it would be wise to learn how to deal with cookies. If you have a problem, one of the simplest settings to check / correct is the browser cookie filters - then you may need to check / correct the browser script filters.

Using A Non Google Custom Domain In Blogger

Similar to concerns about using a Google custom domain outside Blogger, we have concerns about using an existing non Google custom domain with Blogger.

One of the advantages of the Blogger custom domain feature is that it gives you the option to publish a Blogger blog to an existing domain. The existing domain can be part of a WordPress hosted website, a website hosted by your ISP, or by any registrar - as long as you have access to a domain dashboard (aka "zone editor"), and can add the required DNS addresses.

If the need to use the Blogger blog in the domain is strong enough - and if the existing registrar does not provide dashboard access, or the necessary addresses - you may be able to transfer domain hosting, to a more suitable registrar.

The process of publishing a Blogger blog, to an existing domain used outside Google, will vary, depending upon how the domain is currently hosted - and requirements to retain an existing non Google website.

Consider The Options.

There are several ways to add / substitute a Blogger blog, into a domain originally purchased for use outside Google.

1. Transfer domain registration, to a Blogger compatible registrar.
2. Update domain DNS, with the current registrar, to only point to your Blogger blog.
3. Update domain DNS, with the current registrar, to also point to your Blogger blog.

Within these options are additional possibilities.

Transfer domain registration, to a Blogger compatible registrar.

In the long run, and for the most predictable results with Blogger, it will be best to transfer domain hosting to a Blogger compatible registrar. This will require that you obtain the EPP code, from the current registrar.

For Blogger blog owners in the USA, you may be able to use Google Domains as the new registrar. Google Domains is the preferred registrar, for any Blogger / Google custom domain.

• Google Domains provides a dashboard, which has features which support setting up Blogger custom domains.
• Google Domains provides real time support (15 hours daily), by online or voice chat - and email based support.
• Google Domains staff is specifically trained in the needs of a Blogger / Google custom domain.

For Blogger blog owners located outside the USA - or if Google Domains is not usable - you may use either eNom or GoDaddy. Both eNom and GoDaddy have some familiarity with hosting custom domains. GoDaddy is known to provide aggressive domain acceptance, for transferring hosting into their care.

If you cannot use either eNom, GoDaddy, or Google Domains, you may use any registrar able to provide required DNS addressing, who can accept domain hosting transfer. Note as with any third party registrar, you may be required to deal with various oddities of the registrar.

The latter choice could even include free DNS hosting.

Update domain DNS, with the current registrar, to only point to your Blogger blog.

If you need or prefer - and if the current registrar will provide the necessary DNS addresses - you may leave the domain hosted with the current registrar. You can then remove existing host addresses, and add DNS addresses to publish the Blogger blog using a symmetrical address complement - or using an asymmetrical address complement.

Update domain DNS, with the current registrar, to also point to your Blogger blog.

If you need, because you wish to continue publishing a non Google website, and if the current registrar can provide the necessary DNS address for your Blogger blog, you may be able to leave the domain hosted with the current registrar. You can add an additional virtual host, to publish the Blogger blog.

Whatever your decision, consider the needs of custom domain publishing.

As I've repeatedly stated, publishing a Blogger blog to a custom domain is very simple - as long as you adhere to the requirements. This specific project, though may not be so simple. Be aware of the details - and start this project only when you are able to deal with the details.

With the domain operational, setup a Blogger blog - then maybe import content.

When you get the domain working, it's time for the creative work. Setup a Blogger blog - and import from any suitable blog extract - or maybe from a converted WordPress Export file.

Prepare to see a lot of 404s, if your readers have bookmarked the blog.

However you import the posts, you can import the content as carefully as possible. You can have the same post titles - but every different blogging service has different ways of mapping a post title, into a URL.

If your readers have bookmarked your posts (as any blog publisher would appreciate), when you import the blog content, you're going to have post URLs that will differ. Any bookmarks will go straight to 404 status.

Your readers will be getting a lot of "404 Not Found" from their bookmarks. You should consider making a custom "404" display for the blog, as a start. Alternately / complementarily, you may consider using custom redirects.

Subtle Referer Spam Attacks Can Last For Years

We see signs of confusion, in Blogger Help Forum: Get Help with an Issue, about Stats count adjustments.

The number of page views for individual posts and total page views have dropped precipitously. It appears that Google is under reporting these page views, which of course results in less earnings for our website.

This blog owner does not understand the effect of referer spam upon Stats - nor the separation of AdSense and Stats.

Some blog owners think that they know what pageview counts are appropriate, for their blog - and are unhappy when Stats does not display counts that agree with their expectations.

Not all blog owners understand that Stats displays pageview counts in their own context.

Every different visitor counter produces different statistics.
There are not any two visitor counters that will ever show the same figures - and Stats, by its unique way of identifying visitor activity, will differ even more from any third party visitor counter. Also, referer spam, and retroactive corrections, will cause Stats counts to fluctuate significantly, with some blogs.

Some referer spam may even be crafted to target specific blogs. Blogs which publish complete posts on the main page will receive a maximum amount of main page traffic with a minimum amount of individual posts traffic.

Referer spam, targeting the right blog, can have good results from slight effort.
An imaginative referer spam publisher can attack such a blog, using a minimum amount of bogus individual post page activity, and still be noticed by the blog owner - and have a good chance of receiving investigative clicks ("What is this link in the log?") - because most organic traffic will reference the main page.

Given a minimum amount of traffic involved in such a spam attack, Google could take months or years to detect the attack. The blog owner will become used to seeing the bogus counts, and may equate the referer spam to normal visitor activity.

Subtle spam attacks, when removed by Google, will produce maximum visibility.
When Google does detect the spam attack, they will remove all similar visitor activity, retroactively. The blog owner may see pageview counts for previous months and years drop precipitously.

Blogs with minimal organic visitor activity - such as blogs with large main pages, containing few posts - will be especially susceptible to this confusion. Seeing pageview counts drop rapidly, some owners will not take the change well.

Stats does not lie. Owners must accept the truth.
Unfortunately, Stats displays do not lie. If Google removes referer spam pageview counts retroactively, blog owners who have been seeing referer spam, and confusing it with genuine visitor activity, will have to accept the truth.

Content / Spam Classification Has Two Sides

Spend some time surfing Blogger Help Forum: Get Help with an Issue - both in detail, for recent periods - and random sampling, over long periods.

Read the comments, and questions. You'll see both complaints about spammy (aka "abusive") content - and objectionable (aka "adult") content. And, you'll see review requests, referencing previous abusive and adult content penalties.

Given enough surfing, you'll discover that each is simply the other side of the same coin.

As you examine issues discussed in the forum, about abusive and objectionable content, be objective - and be thorough.

Consider both sides of the classification issue.

Try to look at both sides of each story.

• Look at the complaint reports.
  • Blog "xxxxxxx" is nasty. How do I get it blocked?
  • Blog "yyyyyyy" is spammy. How do I get it removed?
• Then, look at the review requests.
  • I publish blog "xxxxxxx". Why do my readers get an "adult" content warning?
  • I publish blog "yyyyyyy". Why was my blog removed?

Each of these issues represents previous action by the Blogger Policy Review team or automated content / spam review process - and each of these issues represents more work to be done, by the Blogger Policy Review team or automated review process.

With more relevant reader opinion, Blogger has to be more responsive.

As the content / spam classification process becomes more responsive to opinion, and the needs of the reader population, the Blogger Policy Review team has to become more responsive to the review requests. Both the people who maintain the automated classification filters - and the people who conduct manual reviews - know the dichotomy involved.

As the initial classification becomes more responsive to the needs of people who don't like something in a Blogger blog, the review process is going to later get more demands for review, because of unfair classification. And, more filter tweaks will follow.

Both initial classification, and subsequent review, become more deliberate.

Both classification, and review will require more deliberation - because both teams know that the more responsive they become in one side, the more demands they will see, on the other.

And all of this continues, as cultural expansion / internationalisation, by Blogger / Google, produces a more diverse and larger blog content and reader population. And, it also produces a more easily offended population.

And all of this requires that the blog owners be willing to compromise.

Windows LiveWriter, And A Less Secure Login Option

Some blog owners, who use Windows LiveWriter, may still be seeing the signs of the recent security update by Blogger.

I get an error saying that it cannot log into remote server, and that my password/username are incorrect - although I have re-entered and they are correct.

It appears that Blogger may have created a backdoor, to allow LiveWriter client access - which requires a new Google setting.

One forum post suggests a backdoor setting, in Google Security, which appears to enable LiveWriter to login to Blogger.

IT'S WORKING AGAIN!!! With a caveat - you'll get an error message about not being able to log in. After you do, check the Gmail account associated with your Blogger. Open the link to control your access security settings (https://www.google.com/settings/security/lesssecureapps) and allow "Access for less secure apps." Then click the back arrow. Quit LW, then open & try again.

Click here for the "LessSecureApps" wizard, in Google Security.

The setting provided appears to be global. If you have other apps which use ClientLogin, this may or may not provide a complete and safe solution.

Some apps and devices use less secure sign-in technology, which makes your account more vulnerable. You can turn off access for these apps, which we recommend, or turn on access if you want to use them despite the risks. Learn more

It's your option, to allow all applications which use Google to authenticate, to use the less secure "ClientLogin" process.


If you are using Google 2-Step Verification, you can't use this new option.

Some third party offline editors may still need to be upgraded - as it does not appear that the "Less Secure Apps" option is a built in feature in OAuth 1.0. Your experience, and feedback, is welcome.

---

(Update 2015/12/16): Windows Live Writer has been replaced by Open Live Writer, an Open Source project. OLW will only work with OAuth 2.0, and is available for download.

---

Blogger Custom Domains, And Mapped Services

I've been observing custom domain publishing, and how it's affected by applications mapped through various Google services, for a few years.

The well known "Another blog", and it's successor "Key already exists", have three possible causes.

• Actual content, published to the URL.
• Bogus DNS addresses.
• Database corruption.

If you map a Google service to a URL in your domain, even temporarily, then simply disable the service, you can end up with a domain URL that remains mapped to the service. When you try to publish your blog to that URL, you're going to see "Another blog ..." or "Key already exists ...".

When there is an service mapped to a URL, that you need to use, reset the service.

Resetting a service is not difficult - as long as you have access to the dashboard, for the service that's mapped to your domain URL.

1. Create a new DNS address in the domain.
2. Enable the service.
3. Change the service mapping, to the new address.
4. Publish some content, using the service.
5. Delete the published content.
6. Disable the service.
7. Re publish the blog, to the domain.
8. You're done.

Create a new DNS address in the domain.
In this example, with the service being a Google Apps Engine project, we'll remap to "project.mydomain.com". Create a new "CNAME".

project.mydomain.com. 3600 IN CNAME ghs.google.com.

Enable the service.
The service has to be enabled, for the settings to be changed.

Change the service mapping, to the new address.
Change the app to publish to "project.mydomain.com". This will free up the current URL, "mydomain.com" or "www.mydomain.com", so you can publish the blog.

Publish some content, using the service.
This ensures that the service remapping becomes active.

Delete the published content.
Be tidy, and remove residual content, before disabling the service.

Disable the service.
You are now done with the service - until you wish to continue working on it later.

Re publish the blog, to the domain.
Publish the blog back to the BlogSpot URL (if necessary), then again publish to the domain URL. And don't forget to redirect the domain root, if you just published to the primary domain URL (generally, the "www" alias).

You're done.
And finally, complete the migration.

Blogger, And Third Party Offline Editors

Ever since Blogger Engineering completed the emergency upgrade to support Windows Live Writer, we've seen demands from people who use similar offline editors, and other third party products.

The "ClientLogin" protocol (aka OpenID 2.0) was replaced by OAuth 2.0 (aka OpenID Connect), last month. As the problem with Live Writer was diagnosed, in a joint effort by Blogger and Microsoft, we saw evidence that Live Writer was not the only offline editor, that needed attention.

The problem is not with Microsoft is with ALL external soft. Do not work with Zoundry Raven, BlogJet, Post2Blog, PowerBlog Personal Client, W.Bloggar, Windows Live Writer, etc.

Blogger is about personal choice, however - and some Blogger blog owners use offline editors that are not produced by Microsoft.

Now that Live Writer is once again operational, Blogger may need to consider other third party "Client" products - and reach out to their publishers.

I'll start with 5 products, where I can find specific mention in the forums.

• Artisteer
• Blog2Print
• BlogJet
• WordPress
• Zoundry Raven

Artisteer Support has been contacted by one blog owner.

Artisteer Software Engineers wrote me and said: it's an issue known and it's due by a Google change.

It's possible that this may be a good candidate for reaching out.

Blog2Print is not an offline editor - but it apparently uses ClientLogin, when slurping private blogs. Right now, blog owners are told to make their blogs public, just while the blog is being slurped. This can be done, with little inconvenience - given some planning. Blog2Print was, at one time, a Blogger Partner - so hopefully, Blogger Engineering has or will reached out to them.

Blog2Print Support is aware of the problem.

Blog2Print is aware of this issue and we are working hard to fix it. If you run into this issue, please contact our customer service team at support@sharedbook.com
As a temporary work around, you can make your blog public, generate and save your book. Once the book is saved you will be able to restore the privacy settings on your blog.

BlogJet was reported as a problem, by one blog owner.

I downloaded Blogjet but it won't recognize my blog. I've turned off my firewall and tried it several different ways. Is it a Blogger setting that I can't find, a Blogjet issue or some setting on my computer?

Looking at the BlogJet website, we see that the current version BlogJet 3, was released in March 2013.

WordPress is reported to be demanding use of "OAuth 2.0", as advised by Google, when importing posts from Blogger.

Google no longer supports OAuth 1.0

Zoundry Raven was mentioned by several blog owners. However, it may be an unfortunate victim of the ClientLogin deprecation. Looking on the Zoundry Raven website, we see a reference to the future.

Zoundry Raven Goes Open Source!
Join us in making Raven the best blog editor on the market today. Read the full announcement here on our blog.

Referencing the linked blog, we see the most recent post.

The good news is that, to this end, we have decided to release Raven as an open-source project.

You'll note that the "open-source" promise is dated 2009. Barring a long hibernation, I'm not confident that the open sourcing, of Zoundry Raven, is very active.

Given feedback, I'll add and update the status of additional products - and hopefully, Blogger Engineering will provide some suggestions of improvements coming.

---

(Update 6/7): Blogger and Microsoft created a backdoor, to allow Windows Live Writer to continue to work. Whether this will let your favourite third party offline editor also work remains to be tested. Your experience and feedback is welcome.

---