"Delete permanently" Means Delete, Permanently

For a long time, blog owners have been requiring the ability to delete their blogs.

In the beginning, people would delete a blog - whether intentionally or mistakenly - then change their mind, or realise their mistake.

I did not really want to delete my blog.

And the inevitable question.

How do I get my very important blog back? Surely, it's in your computer somewhere??

But this question was not always answered, with encouragement.

Too often, Blogger Support would be forced to give the bad news.

You deleted it, and it's gone.

Blogger added the "Deleted blogs" dashboard list.

Eventually, Blogger Support tired of providing negative answers - and Blogger Engineers added the "Deleted blogs" display, to the dashboard.

A blog, deleted by the owner, and listed under "Deleted blogs", can be recovered by the owner, when desired - up to 90 days from deletion. Unfortunately, the dashboard "Deleted blogs" list was not the final solution.

Some blog owners did not want a deleted blog listed, under "Deleted blogs".

Some people would delete a blog - then sometime later, learn that the blog was not really deleted.

I deleted my blog - but now I see it listed, under "Deleted blogs". How do I delete my blog, so it does not exist?

And the answer.

Wait 90 days - and it will be removed.

But that answer did not always satisfy.

I can't wait 90 days - I want it deleted, now!

And for that requirement, there was no answer.

Blogger recently added the "Remove permanently" option.

Recently, Blogger added the "Delete permanently" option, to the dashboard "Deleted blogs" list. Now, a deleted blog can be removed immediately, at the discretion of the blog owner.

• A blog, when deleted, goes offline - and is moved to the "Deleted blogs" list.
• If the owner wants the blog restored, he can use "Restore blog".
• If the owner wants the blog gone, he can use "Delete permanently".

And, as noted in Blogger Help: Back up, import, or delete your blog

• When you delete a blog: you have a short period of time to restore it if you change your mind.
• When you permanently delete a blog: all of your blog information, posts, and pages will be deleted, and you won’t be able to restore them.

And one additional advice.

Note: After a blog is permanently deleted, the blog’s URL cannot be used again.

The "Delete permanently" option can't be reversed.

The option "Delete permanently" has final and immediate results.

• The blog is removed from "Deleted blogs".
• The blog contents cannot be restored.
• The URL can never be re used.

In the words of the philosopher,

He's dead, Jim.

End of story.

Let's examine the deletion sequence.

Here's my dashboard home page - showing my test blog, awaiting deletion. Compare this display, with my test blog, deleted.

Here's my test blog - "Delete Blog Test".

Go to the dashboard Settings - Other page, and click on "Delete blog".

There is the "Delete blog" wizard - and a chance to "Download Blog".

So, click on "Delete This Blog".

And, it's deleted. But what does that really mean?



Here's my dashboard home page - showing my test blog, deleted. Compare this display, with my test blog, awaiting deletion.

Now, we see "Deleted blogs" has 1 entry.

And there is my test blog listed, with two choices - "Permanently delete" or "Undelete".

Unfortunately, "Undelete" won't work, for me.



We do get an on screen warning, before permanent deletion.

We do get a warning, before deletion. "Deleting Nitecruzr Delete Blog Test is permanent and you won't be able to undo it"

---

A #Blogger blog, once deleted, can be restored within 90 days - if "Delete permanently" is not used. Once "Delete permanently" is used, the blog and all content is gone - and the URL can never be used, again.

Read More

Blog Security Review Is Not Instantaneous

Blog owners do not always understand the reasons behind the mysterious blog security check (following "suspicious" / "unusual" activity account lock).

We see periodic complaints about deleted blogs and locked accounts - and the inconvenience involved, in Blogger Help Forum: Get Help with an Issue.

I get the security and all - but I don't get how a blog is just deleted.

This blog owner, like so many, does not understand how Blogger is trying to keep our blogs under our control - even after detection of "suspicious" / "unusual" activity.

Blog security check, if immediate and instantaneous, would not be noticed.

Blog security check is an art - not a science - and it takes time.

If blogs could be checked for hacking interference without delay, most owners would not complain. Unfortunately, examining blogs for hacking interference requires intense study - and most security experts do not work on weekends.

One unfortunate issue, about all of this, is that not all "suspicious" / "unusual" activity is malicious. Some of it is a simple result of people unable to use account / blog recovery - being innocently told to try every account name and password that can be remembered.

Owner delay, in requesting account unlock, contributes to security check delay.

In some cases, the locked account / deleted blogs may not be immediately discovered by the owner - and this may lengthen the security check process.

Not all blog owners publish - or even read - their blogs regularly. Nor do they accept the need to intentionally keep their account and blogs under their control.

Some owners are very casual about blog security - until a blog is successfully stolen.

---

Some #Blogger blog owners are not terribly impressed by the need to keep their blogs under their control, until a blog is stolen. The measures taken by Blogger / Google Security staff are considered mere annoyances.

Read More

Please, Don't Try Guessing Your Account / Password!

We see too many problem reports, in Blogger Help Forum: Get Help with an Issue, about locked accounts and deleted blogs.

My Google account was suspended because of 'suspicious activities'. Last month, I realized that my two connected blogs, to that account, were also put offline!

Somebody else was unable to use the supplied account / blog recovery tools - and tried guessing what could not be remembered.

The first would be a blog owner, whose only mistake was having a Blogger account with a name similar to another account, owned by the second.

The second would be someone who could not remember her (his) account name / password, could not use account or password recovery, and who got well meaning advice.

Just do the best you can - try what may be your account name, and any passwords that you can remember!

One blog owner must suffer, because another cannot remember login details.

And owner #1 is suffering, because of owner #2. Owner #1 is now anxiously waiting for action by the security experts (with the blind queue of unknown length) to examine his blogs - and possibly, waiting while not knowing why.

Owner #1 may be seeing this - and not know why.



Password guessing may be necessary, in extreme cases - but it can cause misery - and owner #2 will never realise the pain caused to owner #1. Even if owner #2 recovers access to her / his blogs, innocent brute force attempts can cause account lock / blog security lock, to owner #1.

Protect yourself against the anguish, using Google 2-Step Verification.

The best way to protect against this sort of abuse is to use one or more Google Two Step Verification options. This will leave owner #2 seeing (for instance).

Insert your USB security key, and tap the lighted button.

And having no security key, owner #2 will simply have to try guessing a different account name. It may be an inconvenience (for owner #1), carrying a never used USB security key - but the one time it's needed (and available), it will make up for the inconvenience.

---

One #Blogger blog owner, unable to remember a necessary account name or password, may try guessing what cannot be remembered. Guessing an account name can leave one trying an account that somebody else owns - and can cause account lock and blog deletion for somebody who they will never know.

Read More

FeedBurner, And Blogs Unwisely Deleted Or Renamed

Some blog owners delete or rename a blog, without proper planning - and later regret their action.

Some spammers track blog name availability - particularly with blog names that contain "English" (and some non English) language words. If a spammer discovers that a given blog name has recently become available, he will publish a stub blog to that name - and later, add spammy content.

Why is a spammer interested in recently available names?

A previously unavailable name, now available, has residual value - because it previously had content, and presumably, readers.

If a valuable blog name is made available by the owner, a spammer will take it.

If a blog owner just abandoned a valuable blog name, by deleting or renaming the blog, a spammer is going to make good use of it.

The unwary blog owner will soon get complaints, from former subscribers.

Shortly, the unwary blog owner will see that his blog, recently deleted or renamed, has been re published and is now full of spam. His former readers are now asking why he is filling up their blog feeds with spam. And he has lost control of the blog, that once was his.

Unfortunately, by the time the republished blog name is discovered, the spammer has taken legal control - and is now the rightful owner. And, short of deleting the blog as a TOS violation, Blogger will recognise the spammers right to own a blog that was legally obtained, using a spammer version of "Create blog".

If the unwary blog owner is you, you may be able to correct your mistake.

If a deleted or renamed blog used FeedBurner to distribute a blog feed, it's possible that the remaining readers are subscribed to the FeedBurner feed. This is where you - the formerly unwary blog owner - can correct your mistake.

A hacker / spammer, who now (legally) has control of an abandoned blog, may not have control of the FeedBurner feed, that is feeding from the blog. If you can regain control of the FeedBurner feed, you can redirect it to a different blog.

1. Setup a stub blog, with one or more posts explaining your mistake.
2. Edit the FeedBurner feed, to point to the feed from the stub blog.
3. Publish a post or two, as an apology to your former subscribers.

Setup a stub blog, with one or more posts explaining your mistake.

You cannot do what you should have done originally - publish a stub blog to the abandoned blog name. You can, however, publish a stub blog to any other available and suitable name.

Then add a post, explaining what you did - and why the people reading the new blog (your new stub blog) are (or just previously were) seeing spam, in their bloglists and Reading List.

Edit the FeedBurner feed, to point to the feed from the stub blog.

With a new blog publishing an active feed, edit the FeedBurner feed that is currently re publishing the feed from the spammer owned blog. Change the FeedBurner feed, using "Edit Feed Details", to re publish the feed from your new stub blog.

The current FeedBurner feed, for
The Real Blogger Status, is
http://feeds.feedburner.com /Nitecruzr-Blogging



To change the feed source URL, simply edit the "Original Feed" setting - then click "Save Feed Details".

Publish a post or two, as an apology to your former subscribers.

With your FeedBurner feed now re publishing your new stub blog, publish a post or two explaining what you did. Hopefully, given a couple posts from your (reclaimed) feed that do not contain spam, your former readers may read one of your new posts, and be enlightened.

And the spammer will be none the wiser - until the people who are paying him report that his former spam channel has stopped producing traffic to their website.

---

FeedBurner Feeds, After Deletion / Renaming Of Blogs
FeedBurner Feeds, After Unwise Blog Delete / Rename
FeedBurner, After Blog Unwisely Deleted / Renamed

If you unwisely delete or rename a #Blogger blog, the name that was once yours will have some value to a spammer. If a spammer takes the abandoned blog name, publishes his own spammy content, and distributes it to you former readers, you will be powerless to do anything.

If you are using a FeedBurner feed to distribute the blog feed, however, you can edit the FeedBurner feed, and cancel the spammers channel.

Read More

Empty Or New Blogs Can Be Classified As Spam Hosts

We're seeing a few recent reports, in Blogger Help Forum: Something Is Broken, from owners of empty and / or new blogs, about spurious spam classification.

Very few owners of empty or new Blogger blogs understand why their blogs should be classified as possible spam hosts, by the Blogger anti-spam processes. Most blog owners seem to think that only blog content is considered, in spam classification.

Spam classification considers many characteristics of a Blogger blog, in classifying any blog as a possible spam host.

Blog post content is an obvious - but not the only - factor in spam classification. Given previously observed behaviour of spammers, many characteristics of blogs, besides simply the extracted and analysed content, are used in classifying possible spam blogs. Using fuzzy spam classification techniques, one might also consider

• Accessories and decorations, on the blog.
• Addresses used, in setting up multiple blogs.
• Overall behaviour in Google, by the owner.
• Past posting habits of the owner.
• Previous classification of similar blogs.

Some spammers obscure their activity, with gratuitous Google activity.

Some spammers are active in multiple Google activities and features. It's possible that some spammers even try to make their spam in Blogger harder to detect, by spreading their activity across other Google services - even when non abusive in other Google services.

Some spammers may not realise that activity in other Google areas can be tracked, and included by Blogger spam classifications processes.

Blog publishers, enjoying similar activities, may be spuriously classified.

Blog owners who use one or more techniques involved in setting up and maintaining spam blog farms may be classified as spammers - and their blogs then classified as possible spam hosts.

The term "blog owner" must itself be considered fuzzily, as some spam blog farms contain blogs owned by multiple Blogger accounts and profiles. Some Blogger accounts, similar to known spammer accounts - even with no blogs owned, or with empty blogs published - may then appear as possible spam hosts.

Empty blogs may still provide clues, which suggest spammy purpose.

Empty blogs, that appear similar to blogs in known spam farms, may themselves be classified as possible spam hosts. Various details such as blog name, blog design, and use of various blog accessories and features, can make a blog appear similar to known spam blogs - with no other content.

As long as spammers exist, some Blogger blogs will be spuriously classified.

Given the need for Google to reduce the volume of spam blogs, fuzzy spam classification might use any of the above details, in classifying any empty or new blog as a possible spam blog. This will, unfortunately, lead to spurious spam blog detection.

The possibility of spurious classification cannot prevent classification, in general.

Given the ability of spammers to publish multiple blogs in the Blogger name space, classifying empty and new blogs is necessary, in making it possible for Google to keep up with spammy activity. This technique enables publishers of genuine blogs to have their blogs viewed as righteous Internet content - not as one more blog, in a sea of spam.

Read More

The Mysterious "Deleted blogs" Dashboard Link

Occasionally, we see signs of confusion, in Blogger Help Forum: Something Is Broken.

Where is the "Deleted blogs" link?

or

How can I recover my blog, if there's no link on the dashboard??

These blog owners don't understand that "Deleted blogs" only appears, when there are deleted blogs that can be recovered.

Not all blogs, having vanishing from the dashboard, will be recoverable by the owner.

• A blog deleted / locked after hacking activity was detected won't be recoverable.
• A blog owned under another Blogger account won't be recoverable.
• A blog that does not exist won't be recoverable.

If the Blogger account owns no blogs that are recoverable, there won't be a "Deleted blogs" link on the dashboard.

If the Blogger account owns other blogs, that are not currently deleted, those blogs will be listed. If the Blogger account owns no recoverable blogs, the blog owner sees a monolithic message

You are not an author on any blogs.

In some cases, the blog owner will be advised to clear cache, cookie, and sessions - then restart the browser, and login to Blogger. In other cases, the solution will be to wait 24 to 48 hours, and check again. Just don't waste time looking for a link that may not be there - and try to understand why the link may not be there.

>> Top

Read More

Browser Cache, And Blogs Locked After Hacking

The effects of browser cache, upon our Internet life, are not always understood.

Most of us know, by now, to clear cache and restart the browser, after updating a blog, for consistent testing. Some folks know that blog security changes don't always take complete and immediate effect.

Recently, we're seeing a new effect, reported by owners of Blogger accounts locked, after hacking activity is detected.

I got a message mentioning suspicious account activity, when I logged in to Blogger. I provided my phone number, and I received a code on my phone, that I had to enter before I could then log in. My blog was working fine just after I logged in. A short while later, though, it was gone. Why was my blog deleted, because I unlocked my account?

This blog owner is just slightly confused, about the cause and effect here.

Google robotic processes are constantly monitoring account login activity, and watching for signs of hacking activity, such as brute force password entry.

Hacking Cannot Be Detected, Immediately.

When hacking is detected, the detection may not be immediate - so Google protects us by considering the possibility that the hacking could have been successful, and deletes or locks blogs owned by the account under attack. The blogs in question are taken offline, immediately, when hacking is detected.

When a blog is taken offline, blog content may be found in cache.

If a blog owner has just been working on a blog, as is frequently the case, the blog contents will be cached somewhere between the owner and the Blogger servers. Blogger can take the blogs offline, on their servers - but any cache containing the blogs will remain. If the blog owner is working on a blog while the Blogger account is under attack, what's in cache will remain, visible to the owner, until cache expires.

If a Blogger account is attacked, and the attack is detected, shortly after the owner has viewed a blog, what's in cache will be used, until it expires. The owner won't see the effects of the blog being deleted until the cache expires, and the browser tries to retrieve a fresh copy from the Blogger servers.

As cache expires later, the blog owner sees the blog go offline.

The blog owner sees the blog go offline shortly after he verifies account ownership, and thinks that the verification process caused the blog to go offline. In reality, the blog was taken offline before the owner even knew of "suspicious" account activity.

The blog owner has to wait, while the blogs are examined for hacker changes.

Now, the blog owner can do nothing, except wait until the account and the blogs are examined for signs of tampering. In some cases, no notification of progress will be received - and the owner will see the blog(s) returned to service, sometime later.

How much later the blogs return to service will vary widely, depending upon several details - and this variation, added to the uncertainty caused by cache latency, leads to mystery. And less attentive owners may take the delay as revenge, by Blogger, for their lack of attention to their blog(s).

---

Browser Cache, And Confusion About Blogs Locked After Suspected Account Hacking
Browser Cache, And Blogs Locked After Hacking

Read More

Deleted / Locked Blogs Have Several Causes

Many blog owners are occasionally confused, by the effects of various Blogger / Google security processes.

We see the agony, daily, in Blogger Help Forum: Something Is Broken, from those who only want to login to Blogger and work on their blogs.

The side effects of the security processes are similar - and depending upon various owner specific details, can be easily confused for each other. The possibility of confusion requires careful initial analysis, when we are faced with an angry blog owner.

My blog was deleted, by Blogger. How could they do this? I do not publish spam!

This is a typical problem report, which can reflect any one of the processes, each requiring different action in the forums.

There are multiple Blogger / Google security / TOS enforcement processes, which encourage observance of various Blogger / Google requirements.

Each process may cause a Blogger account and / or blog to be unavailable for public access, at any time.

• DMCA Violation looks for copyright and similar violations.
• Hacking detection looks for automated attacks against our Blogger accounts and blogs.
• Malware detection looks for malicious code installed in our Blogger blogs.
• Porn classification looks for blogs with adult content, and with unacceptable advertisements (aka monetised porn).
• Spam blog classification looks for Blogger blogs which contain spammy material or use spammy techniques.
• Repeated offenses can have gradually increasing severity of action taken.
• Owner deletion or rename may be confused with spam classification.
• Team blog ownership will affect blogs owned in common, by that team.

Each different process has a different effect on the Blogger account and blogs owned - and requires different attention by the blog owners, by the forum helpers, and by Blogger Support and Google Security. Not all blogs will be listed in the "Deleted blogs" dashboard inventory.

DMCA Violation

Accounts and blogs can be deleted, for progressive DMCA violations. The DMCA violation process originated with complaints made by the major entertainment industry content enforcement organisations, citing theft of "intellectual property" which they control.

In the USA, this would involve the "MPAA" (Motion Picture Association of America), and the "RIAA" (Recording Industry Association of America). I have been told that similar content enforcement organisations exist in other countries.

In more recent events, private citizens have been known to use the DMCA Violation complaint process, for miscellaneous copyright violation reporting. DMCA Violations have a formal complaint and appeal process.

Hacking detection

Blogger / Google network monitors are constantly analysing account login activity, and looking for signs of brute force password hacking.

When hacking activity is discovered, the Blogger account - and all blogs owned by the account - are deleted and locked, pending account verification by the owner, and blog integrity checking by Google Security.

The blog owner, after changing the account password, solving a CAPTCHA, and / or verifying account ownership by providing various personal details, is left waiting for the blogs owned by the account to be examined for signs of abuse by the hacker.

Until the blog(s) are returned to online status, they appear in neither the "Deleted blogs" or "Locked blogs" dashboard lists. The owner, even when logged in to the right Blogger account, simply sees the dashboard advice

You are not an author on any blogs.

In this case, neither the blog owner nor the forum helpers can do anything useful, except wait, anxiously - possibly, with no notice provided. The blog being offline may not be immediately observed by the owner - and this may cause more confusion.

Malware detection

Blogger robotic processes are constantly checking the various blogs, looking for malicious blog accessories, components, and scripts. When a blog is subject to "Malware" classification, the blog will appear in one of two dashboard lists, in sequence.

1. Initially, the blog will appear in the "Deleted blogs" list. While the blog is in "Deleted" status, the blog owner will be able to do nothing, except request "Restore".
2. Once the owner has requested "Restore", the blog is undeleted, and placed into the "Locked blogs" list. While the blog is in "Locked" status, all authors can access the blog to remove malware - but the blog remains offline, to all viewers. Once all malware has been removed from the blog, the owner can "Request Unlock Review".

If the blog remains in "Locked" status for over 48 hours, the blog owner may report this in the forums, and may request a manual review. The forum helpers, and online viewers, will generally see the blog displayed as "TOS violation".

This blog is in violation of Blogger Terms of Service and is open to authors only

Adult Content / Porn Detection

Blogger will soon classify and delete blogs with "adult content", which host advertisements to commercial porn sites. Like spam classification, this will probably involve both false negatives and false positives.

Spam detection

Blogger robotic processes are constantly checking the various blogs, looking for signs of spam activity and content. When a blog is subject to "Spam" classification, the blog will be displayed in the "Deleted blogs" dashboard list.

The owner can do nothing, except request "Restore". If the blog remains in "Deleted" status for over 48 hours, the blog owner may report this in the forums, and may request a manual review. The forum helpers, and online viewers, will generally see the blog displayed as "Removed".

Blog has been removed Sorry, the blog at xxxxxxx.blogspot.com has been removed. This address is not available for new blogs.

Repeated Offenses

We have recently noted that repeated TOS Violations, involving DMCA, Malware, Porn, and Spam, are being dealt with in increasing severity.

Owner deletion or rename

Mistakes made by the owner can be confused with Spam detection. When a blog is deleted by the owner, it will appear in the dashboard "Deleted blogs" list for up to 90 days.

During the 90 days, the owner (or a team member, when applicable) may "Restore" the blog. After the 90 days expire, the blog will be removed from "Deleted blogs", and will be unrecoverable. Besides being unrecoverable, no other details have been determined.

If the blog is renamed (published under a different BlogSpot URL), the external symptom may be similar to deletion by the owner.

Blog has been removed Sorry, the blog at myblog.blogspot.com has been removed. This address is not available for new blogs.

In this case, the blog will be listed in the dashboard "My blogs" list, under the right Title. The owner needs to setup a stub blog, pointing the readers to the new URL.

Team Ownership

Any blogs owned by a deleted / locked Blogger account may simply disappear from the dashboards of other team members. If the Blogger account is not restored / unlocked, the blogs owned by that account - including any team owned blogs - may remain deleted - and inaccessible to everybody.

The Confusion Accumulates

Because of anonymous blog ownership, loss of account control, team blog ownership, and use of inactive or non existent email addresses, any account / blog which is deleted or locked for hacking (actively / as a victim), malware, and / or spam may not be easily discovered or recovered by the owner.

And, not all scenarios can be easily diagnosed. Besides the deleted blogs, there are blogs that remain online - but have still disappeared from the dashboard of the owner.

All of these issues cause further confusion and frustration.

These scenarios may appear, to the untrained eye, to be signs of fraudulent, malicious, and / or petty actions by Blogger - and are loudly claimed so by spammers with their own agenda. None of these accusations are true - the above processes simply represent Blogger and Google attempting, in the best possible way, to protect everybody against the various hacking, malware, porn, and spam attacks which are constantly in progress.

Read More

A Blog Deleted, As A Suspected Spam Host, Is Not Subject To The 90 Day Limit For Restore

We see signs of panic, periodically, in Blogger Help Forum: Something Is Broken, about blogs deleted as suspected spam hosts.

My blog was deleted for spam 2 months ago. I need my blog restored, this month, as I don't want to lose it!

This is a common misconception, about spam deletions, and the mysterious 90 day limit.

There's no deadline for either the start, or the completion, of the review process, when a blog is classified as a suspected spam host. The owner may request review a year after the blog is deleted - if he's willing to wait for a year without concern. Alternately, he may ask for review the same day that he discovers the blog is offline. When the review is requested, Blogger Support may be immediately available, and may return a blog to service that same day - or they may be busy, and require a month to respond.

When the blog does get reviewed, the rules are simple.

• If the blog is judged to be righteously classified, the blog is deleted, with the URL locked to the deleted blog.
• If the blog is judged to be spuriously classified, the blog is restored, and control is returned to the owner.

In either case, the URL is not made available to the public.

This is either good news (if you are the owner), or bad news (if you wish that you were the owner).

You cannot gain control of the blog, or of the URL, by reporting the blog as a spam host - whether the blog has 1 post (one post published 10 years ago), or 3650 posts (one post published daily, for 10 years). If the blog appears to be inactive, your only option is to contact the owner, directly. If Blogger classifies an inactive blog, following your reporting the blog as a spam host, the blog will remain deleted or locked, until the owner requests review.

If the owner deletes the blog, the URL may - or may not - be made available.

Pick an available URL, and start your blog - and concentrate on the interests of your readers.

>> Top

Read More

Recovery From Locked Blogger / Google Accounts

Not all blog owners understand the reasons behind the locked Blogger / Google accounts.

Even less understand why recovery of locked accounts, and of the blogs owned by the locked accounts, is not immediate. We see the occasional report, in Blogger Help Forum: Something Is Broken.

I had to change the password on my account - and now my blogs are deleted! Why should I wait another "24 to 48 hours" to get my blogs back?

This blog owner does not understand the possible reasons for the locked account - and the work that goes on after the account is unlocked.

Brute force hacking of our Blogger / Google accounts, by hackers / spammers, who have use of the various botnets in the Internet, is a constant activity. Opposing activity, by the Security teams in Blogger / Google, to not let hackers and spammers take control of our accounts and blogs, is just as constant.

Some of the Security activity requires our patience - and blog owners, having to recover their deleted blogs, are not always patient.

The Security processes, in Blogger / Google hacking prevention, have to work from a worst case scenario, when detecting hacking activity.

Immediate detection of hacking is not always a possibility.

Account hacking cannot always be detected instantly. When hacking is detected, the hacking prevention process has to consider the possibility that the accounts under attack have already been compromised.

When Blogger / Google Security detects possible brute force hacking against an account, they lock the account - and delete the blogs owned by the account.

Alternatively, they quarantine the computers used in the hacking activity. This is where we see the notice of "suspicious account activity" - and possibly the dreaded "403 Forbidden".

Post detection security analysis looks at owner mistakes, and for hacking artifacts.

When we discover a locked account, and request its restore, the security process looks for signs of security weaknesses allowed by the account owners - or possibly added by the (temporarily) successful hacker. In some cases, the owner may be required to change the account password, and receive instruction on using a more secure ("strong") password.

Ongoing efforts by Blogger / Google, to make the account recovery easier for the blog owners to endure, may cause mystery about blogs missing from the dashboard, without obvious recovery options.

After the account is restored, all blogs must be carefully checked.

After the Blogger / Google account is restored, the integrity of the blogs owned by the account must be verified.

• The blog content must be examined for spammy content added.
• The blog Permissions list must be checked, for backdoor accounts added.
• The Mail-to-Blogger settings must be considered as a possible backdoor.

These are simply examples of what must be done, to ensure that our blogs were not compromised, even temporarily, by the hacking just detected. After you get your account back, it's not a bad idea for you to verify this, on your own. If you just got your blog back, after resetting your Blogger account password and / or verifying your phone number, check your template carefully, looking for references to unfamiliar JavaScript code, hosted outside Google address space.

Account / blog verification will take time.

The process of account and blog integrity verification will require an unpredictable time period - and needs to be done with the blogs inaccessible to anybody but the Blogger / Google security processes. The blog being offline may not be immediately observed by the owner - and this may cause more confusion.

Blogger Support is aware that nobody wants to deal with the stress of having a locked or deleted blog - especially after they have gone through the process of verifying their account. They are also well aware of the frustration that is present when someone reports

Somebody is publishing spam on my blog - and I can't access the dashboard to remove the spam!

Locking the owned blogs, after hacking activity is detected, complements the ongoing policy of not disclosing the account names, in helping to keep our blogs under our control.

---

http://blogging.nitecruzr.net/2013/01/confusion-over-recovery-from-locked.html
Confusion Over Recovery From Locked Blogger / Google Accounts

Read More

Everybody Won't Get Proper Notice About Their Blog

One problem that we're seeing in Blogger Help Forum: Something Is Broken involves blog owners, who recently discovered their blogs deleted or locked, by Blogger - and without any notice received.

The account actions may be required with the blog deleted for a suspected TOS Violation, such as hosting malware, porn, or spam - or locked because of "suspicious activity" on the Blogger account.

Why was my blog deleted? I never got proper notice!

Too many people depend upon email notification - and may not receive proper notification, in all cases.

Blogger provides a dashboard based malware / porn / spam classification notification / recovery process, which may not be available for everybody. Similar to malware / porn / spam classification, there will be issues with DMCA violation notification.

This is also a problem when accounts are locked for "suspicious activity", and when blogs are locked for hosting malicious third party gadgets.

There are several reasons why some blog owners won't get notification of their blogs being deleted or locked, by the various Blogger / Google security processes.

Nobody should expect advance warning of any action being taken.

Besides notification limitations, nobody should expect to get advance warning of action being taken - as this would simply encourage the intentional spammers to never request review. Intentional spammers, if permitted, would play 3 Card Monte, endlessly, with their spammy blogs.

Both the notification, and advance warning, limitations contribute to confusion about the various Blogger / Google security recovery options. All email based notifications may not be properly delivered.

The owner of any email account, which may not deliver email properly, is still responsible for reading any important email messages.

Some blogs are owned by accounts which use intentionally bogus email addresses.

Too many Blogger blogs are owned by Blogger accounts which are based on inactive or nonexistent email addresses. Owners of these blogs will never see email notification, when they - intentionally or not - make themselves anonymous.

Some email clients may misfile an incoming email message.

In other cases, some people may get the email notifying them of problems - but their email program may misfile the email, in a folder which they may not check, regularly. In some odd cases, somebody other than the owner may get the email.

Blogs owned by teams will be subject to action against any one member.

In team blog ownerships, any blog owned by the team is subject to action, against the Blogger / Google account, used by any team member. Blogs affected will simply disappear from the dashboards of all team members - with no opportunity provided for appeal or review.

Some blog owners maintain too many Blogger and email accounts.

Finally, too many blog owners maintain multiple Blogger / Google accounts, and are not completely sure which Blogger account may own a given blog. These owners may not even see the dashboard based "Deleted Blogs" button / link, because they will be logged in to the wrong Blogger account.

Each blog owner is responsible for any problems, regardless of cause.

Not all of the above scenarios are entirely the fault of the blog owners - but the blog owners are the ones who will have to deal with the resulting problems. It's possible that this may seem unfair - but it's reality.

Read More

Benefits Of The New Dashboard Based Spam Review Request Option

The improved spam review option has been available, on our dashboards, for slightly less than 2 months. For all it's usefulness, it appears that some blog owners see the new option as just another bit of red tape, which prevents them from publishing their blog. We see suggestions in Blogger Help Forum: Something Is Broken, periodically.

Can't you just submit my review request now, without making me wait another 2 days? Is my dashboard review request really necessary?

Unfortunately, the better the dashboard based spam review option works, the more this confusion should be expected.

Long ago, we had a "Deleted Blogs" link on the previous Blogger dashboard. That link, and the hidden list, were obscure - and explaining how to find the "Deleted Blogs" list was not a job for the weak or impatient. When a blog owner would post in the forums

Why was my blog deleted? I am not a spammer!!

we would typically reply, immediately, with the notorious Spam Appeal Guidelines - then later, cooperative blog owners would see

Your appeal is forwarded to Blogger Support ...

In order to speed up recovery of the less spammy blogs - and shorten the restore wait time for all deleted blogs, Blogger Engineering added the dashboard based "Restore" button. The new button serves two functions.

1. For blogs deleted by Blogger, that are marginally spammy, the blog owner can request an expedited review.
2. For blogs deleted by the owner, less than 90 days previously, the owner can easily restore his own blogs, as convenient.

The new button serves several groups of people, in various ways.

1. Owners of less spammy blogs benefit by expedited restore. When successful, they see their blogs possibly restored on that same day, without their spending any time in the forums.
2. Owners of marginally spammy blogs benefit by regular review and restore, from a shortened queue - since some blog owners will use the expedited queue.
3. Blogger Support can spend less time with the marginally spammy queue, and produce quicker turnaround - yet spend more time examining the truly spammy blogs.
4. Only the genuine spammers will not benefit from the new review queue.

This produces a Win - Win - Win - Loss (sorry, Spammie) scenario.

The blog owners who get their blogs back in a few hours probably won't post in the forums, and praise the improvement - they will be busy re publishing their newly recovered blogs. We may see more oblivious spammers, because Blogger Support will able to spend more time examining truly spammy blogs - which should encourage Blogger Engineering to tweak the automated spam classifier, into digging deeper into the Blogger Blogosphere. So we should expect to see more posts in the forums, for a while.

Why was my blog deleted? I am not a spammer!!

And, it's possible that not all deleted blogs will be listed by the "Deleted Blogs" wizard.

>> Top

Read More

Anonymity, Your BirthDate, And Your New Blogger / Google Account

Not all new Blogger blog owners understand why they are asked for their birthdate, when they setup a Blogger or Google account.

Some folks see this as a violation of their right to privacy, and enter a fake birthdate. Some real serious privacy enthusiasts might enter "01/01/01", just to get through the setup process - maybe intending to correct it, later.

Nobody entering "01/01/01", for one's birthdate, suspects that claiming such a birthdate makes them - in 2013 - appear to be 12 years of age. Unfortunately, 12 years is below the minimum age for owning a Blogger blog.

Since Blogger / Google tries to protect the young people on the Internet from inadvertently exposing themselves - or their families or friends - to unknown dangers, people who may appear to be of insufficient age are subject to having their Blogger / Google accounts, and Blogger blogs, deleted or locked.

If you entered a fake birthdate some time ago, and now find your account or blog locked or deleted, you need to prove your age to Google - and you should do this promptly.

The Google Accounts document Frequently Asked Questions about Google Account and Age Requirements explains how you do this. The process of verifying your age / birthdate is not convenient - and some privacy enthusiasts may claim that it too violates their privacy rights - but it is necessary, to let you correct your birthdate - when you are legitimately of legal age.

Now, you have to hope that you did not, intentionally or mistakenly, also provide a bogus email account as your Blogger / Google account name / recovery email address. The process of identifying yourself as the owner (former, nominally underage) of a given Blogger / Google account is easier to do, when you have access to the email account stated as the account recovery email address.

>> Top

Read More

Improved Spam Review / Undelete Option In Blogger

One of the more positive changes in the "New GUI" involves an improved ability to find, and correct, deleted and locked blogs.

Finding deleted / locked blogs, under earlier versions of Blogger, was always a challenge - both for the person looking for the necessary display - and for the people trying to instruct how to find the necessary dashboard display.

In the current Blogger dashboard, one simply logs in and looks for the "Deleted Blogs" button - right beneath "New Blog", when the blog owner has any self deleted blogs, or any blogs deleted or locked by the Blogger abusive blogs classifier. Clicking on "Deleted Blogs", we see a list of blogs - with either an "Un delete" button (for self deleted blogs), or a "Restore" button (for spam classifier locked / deleted blogs).

Neither the "Restore" or "Undelete" button produce an immediate or universal result - both are still subject to previous limitations.

• The "Restore" button leads to the "Review Request" dialogue - and to the actual spam review - still subject to the opinion of Blogger / Google spam experts.
• The effect of the "Un delete" button is limited to blogs which can be un deleted.

It is simply now far easier to find the spam review / un delete mechanism, than it was under the previous GUI.

If your blog was deleted by you - or deleted by Blogger for hosting malware, you should be able to hit "Restore", and the blog will be restored while you wait. If the blog was deleted or locked by Blogger for suspected spam hosting, you will probably have to solve a CAPTCHA - then wait 24 to 48 hours, while the blog is reviewed. In the long run, you will probably find this extra effort will be worth your time.

In some cases, the owning Blogger account may be locked, following unusual account activity - generally, brute force password guessing attempts, in an effort to hijack control of the account and any owned blogs. After submitting an account restore request and / or changing the account password, the blogs owned by the account will be restored - generally 24 to 48 hours after the account is restored. This is a normal, and unavoidable, result of Google, protecting your account and blogs from hacking activity.

Just be aware that not all blogs will be listed by the "Deleted Blogs" wizard.

Please be aware of the limitations of the restore process. This process serves blog owners who have been spuriously classified. If you request restore - and Blogger confirms that you are a spammer - you will be best advised to start over, or to find a different platform for publishing.

If you do start over, you should be very careful, and avoid making the same mistakes - lest you be subject to more strict punishment. Spammers simply are not welcome, in Blogger / Google - sorry.

>> Top

Read More

Blog Owners Seeing bX-afpmyd When Trying To Un Delete Custom Domain Published Blogs

We're seeing a few reports this week, from blog owners who recently deleted their custom domain published blogs - who now lament their decision - and who are unable to un delete the blogs.

I can't "undelete" my blog, that used to be published as a custom domain URL. I received the following error code: bX-afpmyd.

This problem, like others, appears to have started when custom domain publishing was restored, last week.

Blogs deleted when a custom domain URL is in use have always been a challenge. Similar to the abandoned custom domains problem, they have resulted in yet another cause for the well known custom domain problem

Another blog ....

Now that Blogger is requiring verification of domain ownership, by adding ownership certification using a new "CNAME", it's likely that either lack of the new "CNAME", or broken blog / domain pointers, are going to be a problem when un deleting blogs formerly published to custom domains.

If you are unable to un delete your previously deleted custom domain published blog - and you are otherwise able to restore the blog in question - you, like other blog owners trying to make changes to their custom domain published blog, will need to use the Publishing wizard, and the "settings instructions", and add a unique domain ownership certificate to your non BlogSpot domain. Then, if able to un delete the blog, you'll need to re publish the blog to the domain.

>> Top

Read More