Skip to main content

Please, Do Not Misuse "Report Abuse"!

We see odd abuse issues reported in Blogger Help Forum: Get Help with an Issue - like blog owners reporting a blog with recycling abuse status.
My blog was locked one day, unlocked the next, then locked again the following day. Help!
Generally, this will be a simple case of borderline abuse / spam content or techniques.

Sometimes, the cause of the recycling status is more subtle, than being solely the fault of the owner.

Abuse classification is fuzzy and heuristic. Sometimes, the fuzziness involves unknown third parties.

Account / blog recovery, with demographic verification, is a frustrating process.

Recovery of blogs, when the account details are forgotten or the owner travels, is a frustrating process. Some well meaning persons have been known to provide misleading advice, to someone unable to recover control of their Blogger account.
If you can't recover control, have the blog deleted, by reporting it as abusive.
This was a last ditch effort, that occasionally yielded amazing results.
The blog is gone! Yes!!
But not always were the long term results pleasant.

Occasional malicious abuse blog reporting contributes here.

Occasionally, a blog may be reported as abusive by a devious third party - and the innocent owner would have the blog reviewed, and restored. And Blogger Policy Review improved their abuse reported deletion standards.

And fuzzy, heuristic classification and review can cause side effects.

And another scenario may be seen. Since abuse classifications are fuzzy, and heuristic, any activity in the abuse classification - review process, initiated by reversed abuse reports, can still affect automated classification.





A blog being reported as abusive can affect the classification filters - and cause other blogs to be similarly classified. Similarly, a blog reviewed and restored can cause other similar blogs, deleted or locked as abusive, to be reviewed and restored. And there, we see the repeated, contradictory email from Blogger.

All of this starts so innocently, with someone who can not delete their blog because they lost control of the owner account. And that person, maybe having their unwanted blog deleted, will never know of the confusion, caused by their misuse of the abuse reporting process.

Comments

dolorah said…
Thanks for all your helpful posts over this last year nitecruzer. They have been a valued service. Happy New Year :)

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *.blogspot.com, or maybe have network configuration or infrastructure problems. You can access Blogger.com or you can access Blogspot.com, but you can't access nitecruzr.blogspot.com, or bloggerstatusforreal.blogspot.com.

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):
http://www.pkblogs.com/bloggerstatusforreal.blogspot.com/
2006/07/help-i-cant-see-my-blog.html


And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post:
ht…