Spam Blog False Positive Classifications Do Exist

No matter what Blogger does with improving the spam classification process, they will always generate some false positive classifications.

The more that they improve the classification process overall, the more obscure the false positive classifications will be. Some false positives will require intense investigation of the blogs, to identify the relationships between the blogs involved - and to prove, to Blogger Policy Review staff, that a false positive classification is present.

Some time ago, in Blogger Help Forum: Get Help with an Issue, I had occasion to deal with a blog owner who was a currency trader, by profession. This person had published a cluster of blogs, where he discussed legitimate issues involved in currency trading.

Currency trading is an essential part of exchange of merchandise, between different countries (the export / import business) - and the Blogger spam classification process had deleted his blogs, as suspected spam hosts.

For you to understand the situation that I'm recounting, you need to understand one principle of currency trading.

When someone sells US Dollars ("usd") and buys Great Britain Pounds ("gbp"), to help a client in the USA import merchandise from the UK, there has to be a second trader, buying US Dollars and selling Great Britain Pounds. The first trader is doing a "usdgbp" trade, and the second, a "gbpusd" trade.

The blog cluster, that was setup by the trader, discussed issues about trades between Great Britain Pounds, Japanese Yen ("jpy"), and US Dollars. The trade combinations possible, with just 3 currencies, would be

1. GBPJPY
2. GBPUSD
3. JPYGBP
4. JPYUSD
5. USDGBP
6. USDJPY

Most traders handle dozens of currencies, in various trades. A staff of a dozen traders would handle all of the world currencies - with some trades involving 2 traders working together, on either end of the trade.

The trader in question had published a cluster of 6 blogs - all using the same base blog name (we will call it "Currency Trading"), which gave him 6 blogs - with legitimate names.

1. Currency-Trading-GBPJPY.blogspot.com
2. Currency-Trading-GBPUSD.blogspot.com
3. Currency-Trading-JPYGBP.blogspot.com
4. Currency-Trading-JPYUSD.blogspot.com
5. Currency-Trading-USDGBP.blogspot.com
6. Currency-Trading-USDJPY.blogspot.com

Each blog discussed specific - and very trade sensitive - issues about trades between the specific currency pairs. Each blog provided relevant and unique discussions about the issues.

Thanks to splog detection, a false positive detection - based on legitimate splog classification technique - had, nonetheless, left this blog owner with 6 deleted blogs.

Thanks to one of my previous IT responsibilities, as tech support for a bank currency trading desk network, I recognised the naming convention used by the 6 blogs, and the reason for the 6 blogs - and was able to convince Blogger Policy Review staff about the problem.

Some blogs are part of legitimate blog clusters, which use well defined naming conventions. Others have names that are coincidentally similar to other blogs, owned by different people.

In either case, the reasons for the naming similarities are where we start, in identifying any spuriously deleted blogs - and in describing the reasons for the spurious deletions. Blogger Policy Review staff have to be made aware of the legitimate reason for a naming similarity, and any other details, so they can make an informed decision.

Knowledge about obscure relationships, such as the naming convention for currency trading blogs, are not part of every Blogger helper or staff persons background. Sometimes, the blog owner has to provide details, objectively and patiently, to help convince Blogger Policy Review to restore the blogs involved.

Unfortunately, not all blog owners are patient enough, to be interviewed, to some degree of success. Also unfortunately, some self stated blog owners are actually hackers or spammers, misusing Blogger Help Forums resources.

Some owners of legitimate blogs claim that their being subjected to an interview shows suspicion placed on them, rather than an attempt to identify the problem - and successfully prove, to Blogger Policy Review staff, that a false positive spam classification is present.

The complicated and devious relationships, involved in some spam review request investigations, make a Tom Clancy novel seem like a 5 minute segment of the 6:00 news.

>> Top

Ambiguity In Spam Detection

Occasionally, some bloggers report confusion over whether their blogs have been tagged as splogs, after receiving some odd email.

Your blog at http://myblog.blogspot.com/ has been reviewed and confirmed as in violation of our Terms of Service for: NONE. In accordance to these terms, we've removed the blog and the URL is no longer accessible.

The blog does not appear to be locked, nor does it's online status change. All that's seen is the ominous email notice.

The response from Blogger Support is slightly encouraging.

we have a bug in our system that has been sending those email inadvertently

So if you get this email, apparently you can ignore it. Your blog should remain online, and accessible as before. Check your dashboard - you should have administrative access, and no need to worry.

>> Top

Moles, Spies, Spammers, And Turkeys

In 1977, the late Charles Bronson - better known for his vigilante justice "Death Wish" movies - starred in a movie that capitalised on US paranoia about American - Soviet Russia relations. Set at the height of the Cold War era, the plot of Telefon featured 51 human time bombs - all ordinary Americans. Each had been hypnotised to perform as Soviet spies, when a specially coded telephone call was received, with each tasked to sabotage some specific portion of the American infrastructure.

None of the 51 human time bombs had any conscious awareness of their intended roles. Each thought of her or him self as an ordinary American, and lived that way - until a phone call from an evil renegade Soviet agent triggered their personal hypnotic suggestion.

The woods are lovely, dark, and deep, but I have promises to keep. And miles to go before I sleep, and miles to go before I sleep. Remember. Miles to go before I sleep.

In the action adventure genre of fiction (aka "spy movie"), these spies are also called moles.

This year, we have noted many ordinary bloggers, who have no conscious awareness of their roles, tasked to sabotage the Blogger infrastructure.

My Blog mentioned above got deleted and called SPAM. But I honestly didn't do any SPAM. I went through TOS but I really don't understand my blog was deleted. Please, I have put so much of my time & effort for this blog & now its a PR2. (This blog is gone).

and

I received this msg after restore the blog, how long I must wait to get reinstated. This is totally joke, the blog is about 3 years and have hundreds of post. (This blog is gone).

and

I have been writing almost daily for more than two years and am very surprised as to why my blog would all of a sudden be classified as spam. I really can't think of any reason except that there must be a flaw in the algorithm used for automatically detecting such. (This blog is gone).

Many bloggers, just out there trying to make a buck, have been hypnotised by Affiliate partnerships, Pay To Click and Pay To Surf schemes, Syndicated Content (pay to write), and similar "make money fast and easy" techniques. And now, they are out there, begging for Blogger to just unblock their blogs, so they can get back to work. Back to work - abusing the Blogger infrastructure, and damaging the efforts of genuine bloggers.

They are not spammers (in their own minds), just as the 51 human time bombs were not Soviet agents. But just as the human time bombs (some of them) successfully destroyed key portions of America, these spammers are destroying key portions of Blogger Spam Interdiction, and of the effectiveness of Internet based advertising.

By their volume, they make it hard for us to get genuine, personal blogs, unjustly accused of being spam, back online. And they are requesting individual attention from Blogger

Please, tell me why I am considered a spammer.

This requires further resources from Blogger Support, and Google Legal, who together must decide how much - and how little - to tell these bloggers about spam interdiction, and why they were confirmed as spammers.

These are the real life moles. Moles, recruited by the genuine big time spammers. I also call them turkeys, elsewhere in my discussions.

In the meantime, the genuine spammers are out there, continually republishing their splog farms, and damaging our efforts as genuine bloggers.

>> Top

Spam Review Escalation Depends Upon Action By The Blog Owner

During the past couple of weeks, we have noted a significant increase in the volume of

Unlock my blog, it is not spam!

problem reports, with a large proportion being judged false positives after review. Unfortunately, the false positives can only be identified after the blog owners report

I submitted the review request, and the appeal, and I waited the required 2 business days. Now what?

and we have seen a few of those this week. We have also seen a few more odd reports

The 2 business days ended several days ago! I am tired of waiting for you to do something about this! Why haven't you done something about this?

and here, we have to point out that you (or the blog owner) are the key player in the next step - that is, requesting the escalation to Blogger.

If we reply to you

Since Blogger gets 2 business days to process restores requested and appealed, we'll give them until Friday to act directly from your requests. If they have not acted by then (which seems to be the case in maybe 50% of the time), please reply here, and we'll take the next step.

that means that you have to take action, to continue this process, when necessary.

We have no way to watch your blog, and see that it was or was not restored during the 2 business days. You are the one who watches the clock for 2 business days, and reports that the time is up. If we don't hear back from you, we can only consider 3 possibilities.

1. The Asker was a spammer, and has now gone elsewhere.
2. The Asker's blog was restored, and he is now busy working on his blog.
3. The Asker's blog was not restored, and he awaits further action.

We can only action the first 2 possibilities. The third is on your dime.

>> Top

You Can't Take It With You

Recently in Blogger Help Forum: How Do I?, we've had direct contact with a few confirmed spammers.

These are people who have submitted to the noxious 4 step spam confirmation protocol, and who have been given the full benefit of the doubt.

When I come back with the unfortunate (to them) news

OK, all good things end some day.

Your blogs will, quite likely, not be unlocked. You might wish to review the Blogger and Google TOS.

http://www.blogger.com/terms.g

http://www.google.com/terms_of_service.html

the next post is frequently

OK, can Blogger unlock my blog so I can get the content, and move to another host?

or

Can I redirect my address to my new TypePad (WordPress, whateverspammyhostichose, ...) web site?

and the answer is

No, you cannot do that.

What you steal is not yours to keep, when you are caught.

Like ill gotten gains from robbing banks, you're not permitted to take your spoils of illegal act into your next life.

Content, search engine reputation, and traffic - all acquired while misusing Blogger and blogger resources - are not yours to keep, once you are confirmed as an abusive blog publisher. You stole all of those resources from genuine and honest blog owners. You are not permitted to keep any assets, illegally acquired.

If the police arrest you for fraud, and break up your game of "3 Card Monte" - and you're found guilty of whatever law prohibits your "game", you're probably going to spend a few nights in jail. When they let you go, they are not going to give you back your playing cards - or the money that you stole. If you want to get back in business, you'll need a fresh pack of cards - and probably, you need to start over, in a different city.

It's time to start over.

When the blog is deleted, the BlogSpot URL is locked, for life. If the blog was published to a custom domain, the domain URL is also locked, for life.

The BlogSpot and custom domain URLs won't be re usable, in Google. Ever.



Go away, please. You may, if you wish, start over - but the current life of yours is over. Maybe, find another source of income.

Just don't make the same mistakes, next time.

Three Strikes, And You're Out

In the American game of baseball, each player while performing in the offensive role has three chances to swing the bat and hit the ball. If he does not connect with the ball in any way, on the third chance, he is "out" and goes to the bench.

As a blogger, and when your blog is detected as hosting possible spam content, you have three strikes, too.

1. An automated spam classification process, performed by a Blogger bot, inspects your blog, possibly with a few other blogs, and locks or deletes your blog.
2. A manual review process, performed by people, inspects your blog again, and objectively asks whether or not it is actually hosting spam. This is done after you complete the sometimes hated 4 step review process.
3. A second manual review process, performed by people, inspects your blog for a third time, and carefully asks whether the first two processes were correct. This is done after the review process, and is generally referred to as "escalation". This is the final recourse which you have, when you wish to continue publishing this blog.

If any one of the three steps concludes that your blog is not hosting spam, you get on base and may have a chance to, sometime later, score a point ("run") for your team. If none of the three steps finds your blog innocent of hosting spam, you get to go sit on the bench, because you are "out".

In baseball, the difference between the pitch made with one strike against the batter, and two strikes against the batter, is significant. With one strike against him, the batter can somewhat afford to be selective, and wait for a pitch that he likes; with two strikes, the batter almost has to swing, at any decent looking pitch. The batter is at a disadvantage, with the second strike pitch - because the third strike represents his last chance to accomplish something.

In spam reviews, it's to your benefit to submit the "second strike" review request, from the dashboard link. The review submitted from the dashboard link is done sooner, and it's more permissive. The review submitted from the forum request is much more carefully done, and is more restrictive. Most blog owners want their blogs reviewed and restored, as soon as possible.

All players must abide by the decision of the umpires. If the umpires rule that you're out, then you are out. Go play in another league, if you wish, or wait for your turn to possibly bat again, later (if the game does not end before that time). While you wait, read the Blogger Content Policy, the Blogger TOS, and the Google TOS.

It's that simple. Three strikes, and you're out.

>> Top

Justice Is For The Poor And The Weak - And Small

In the modern legal system, justice is (supposedly) available to all citizens - regardless of colour, crede, or financial status - equally. In the Blogger legal system, justice (as in porn / spam classification, or URL availability) is available to all bloggers - equally.

If your blog is unjustly accused of hosting hacking, porn, and / or spam content, or if your blog is unfairly placed behind a content warning, you (the blog owner) are responsible for getting the wrong righted.

Due diligence requires that the blog owner has to report any problem with any Blogger blog. Regardless of how many anxious readers your blog may serve, you the owner have to request a review, when the blog is unjustly classified, deleted or locked. And, you have to do so promptly.

Blogger must serve owners of small and unpopular blogs equally, with owners of large and popular ones. The blog readers are not part of the review process. The only question is

Does the blog host hacking, objectionable, porn, or spam content?

Please, no coyote attacks in Blogger Help Forum.

Maybe It's Time To Start Over

I've been advising folks about spam problems, and splog detection (both righteous and spurious), for several years.

Sometimes, the advice is about cleaning up the blog, and submitting it for review. Other times, it's about blogs unjustly accused of being spam. Occasionally, it's about a spam blog, that just can't be reviewed again, or maybe a old blog, that you just can't regain control.

If the Blogger region of the Blogosphere is to have any reputation, other than "spam haven", it's simply not possible to provide an infinity of chance for people to clean up their act.

this is what i got from email:

We'd like to inform you that we've received another complaint regarding your blog. Upon review of your account, we've noted that your blog has repeatedly violated Blogger's Terms of Service (http://www.blogger.com/terms.g). Given that we've provided you with several warnings of these violations and advised you of our policy towards repeat infringers, we've been forced to remove your blog.

Once forgiven, you still start over from the beginning.

We all believe in forgiveness, but having been forgiven, should you continue with the blog restored and simply cleaned up? Or maybe, isn't it better for everybody if you simply start over, with a new blog and new content?

And if you publish your blog, you want your blog to remain your blog. Just as we cannot give spammers an infinity of chances to pollute the Blogosphere with their blogs, neither can we give them the chance to steal already developed blogs, using brute force and an army of hijacked computers.

Everybody who wishes to publish a Blogger blog has to religiously maintain control of their Blogger accounts - both by not forgetting access tokens, and by not idly allowing unknown persons to seize control.

If you lose control of your Blogger account, don't demand that Blogger Support blindly tell you what you require, and possibly violate your right to anonymity.

Start a new blog - and don't repeat past mistakes.

Focus your energy on starting a new blog - and maybe connecting the new blog to the old blog. Don't waste your time (the helpers time, Blogger Support's time) trying to clean up what can't be cleaned up, or demand that Blogger help you to seize control of a blog which could be (to them) someone else's blog.

Start over, but with a clean blog - and try to avoid repeating your mistakes.

Learn to read - and heed - the warnings.

Next time, when you get the first notice about unacceptable content, heed the warning. And when you change ISPs (get a new job, graduate from school, whatever), and you get a new email address, update your Blogger account - while you can.

The Attack Of The Clones

One noticeable spam problem became visible in late 2009, thanks to yet another Blogger error.

This error left a lot of bloggers (some legitimate and others actually spammers) reporting both confusion and indignation.

The confusion was seen, in two (seemingly) separate topics of indignation.

My blog seems to be locked, but when I fill out the CAPTCHA, I get

Your blog is not locked, and does not need review.

What do I do, now?

and

My blog is not spam! Honestly, how could Blogger legitimately call my blog spam?

Both of these reports, echoed by dozens of bloggers and spammers, show two sides of the same story.

The first report was typically about blogs that were righteously locked - yet a mistake caused the message

Your blog is not locked, and does not need review.

The second report exemplifies the despair and frustration felt by thousands of honest people who simply want to publish to their blogs. And there are dozens of similar, and dissimilar reports.

Note: This isn't fiction - I'm not stealing content from the Tom Clancy "Net Force" novels. This is real.

Spammers publish new blogs, constantly, using botnets.

Spammers, in order to publish one or two active splogs (blogs containing actual hacking, porn, and / or spam content), use the power of the Internet. Each splog publisher ("splogger"), who may have at his control thousands of hijacked computers, publishes thousands of blogs each day.

A spammer starts with empty blogs, which do not appear spammy.

A splogger starts by simply publishing empty blogs, in a constant, all day activity. You may see the empty blogs some time, if you go "Next Blog" surfing. They have a title, an archives gadget in the sidebar, and maybe one or two posts with random garbage. And a Profile gadget, with a link to the "owner", each "owner" with 10 blogs.

He then adds random content, scraped from the web - maybe, from your blog.

The splogger next takes one legitimate blog - in this case, your blog. He scrapes content from your blog, takes a dozen or so of his empty blogs, adds your content to each, and republishes each blog. Now, there are a dozen clones of your blog, plus your original, in BlogSpot.

He then adds spammy content, to a few of his blogs.

Next, the splogger takes a couple of his recently created clones, adds the payload - hacking, porn, and / or spam content, or possibly, links to other blogs or websites containing the payload - and republishes his now active splogs.

Each time, he just uses a couple blogs (cloned from your blog), and keeps the others as reserve. He has dozens of other splogs with active content out there too, using content scraped from other legitimate blogs. The clones of your blog, joining the clones of other blogs, are now active members of his splog farm.

As Blogger deletes discovered spammy blogs, the spammer uses more like yours.

As the splogs with active content are detected and removed by Blogger, the splogger simply activates other reserves, placing payload into each, in turn. By the time all of the reserves, that are clones of your blog, are used up, the well designed spam blog farm will have clones of still more legitimate blogs, ready to be activated.

A spam blog has a distinctive life cycle.

Considering this process, we see the 5 Stage life cycle, of each blog in the splog farm.

1. Empty (just published).
2. Reserve (previously empty, republished with scraped content added).
3. Active (previously reserve, republished with payload added).
4. Detected (previously active, locked by the Blogger Spam Classification bot).
5. Deleted.

The plan here is that each splog will pass through each stage in the life cycle, in proper sequence. Since the splogger publishes thousands of splogs daily, if Blogger were to simply lock then delete the active splogs, the splogger simply activates the reserve splogs, as needed. This is good project management, by the sploggers.

Blogger shortens the life cycle, using fuzzy blog identification.

Blogger aims to shorten the splog life cycle. When the anti-spam bot detects an active splog, they search their database of suspected splogs, find similar blogs with no active content (the reserves), and lock the reserves too.

Unfortunately, when Blogger locks the reserve splogs, they are also going to lock your blog. Fuzzy spam detection techniques can't tell the difference between your blog, and the clones, because there is no difference.

If a spammer clones your blog, your blog will look just like a spam blog.

A successful clone is a non distinguisable replica of the original blog. Your blog looks like one of the reserve splogs. This leaves you, and bloggers like you, reporting

My blog is not spam! Honestly, how could Blogger legitimately call my blog spam?

If the spam blogs went untouched, the search engines would index your blog.

When you look at this differently, though, you see that Blogger is actually helping you. Were your blog, and the clones, to remain in BlogSpot undisturbed, the search engines would see the clones, and levy a huge duplicated content penalty on all aliases of the content - including your original blog.

If you are able to declare your blog as legitimate to Blogger, Blogger can later delete the sploggy clones - and the search engines will, hopefully, continue to index your blog, as legitimate and unique content.

In 2012, Blogger took the Next Step, and made "Next Blog" a less productive launching ground for splog farms. With blog owners carelessly deleting and renaming their blogs, however, the blog clone farm continues as a useful model for spam distribution.

The Blogger Anti-Spam Bot Bites The Big One

Since January 2008, Blogger has been working hard to keep hacking, porn, and spam out of the blogosphere. This work is not by humans, though, but by an army of unattended computers, called by many the Blogger anti-spam bot.

The anti-spam bot is not static. It has to be constantly updated, to keep up with constant activity by the producers of the many large splog farms that inhabit the blogosphere. It's going to produce false positives, as well as false negatives, and it's going to produce inconvenience to many bloggers.

This week, a recently applied update appears to have taken an excessive amount of innocent blogs with it. Major inconvenience to many. Can you say "egregious false positive rate"?

One blogger seems to have a way around the problem - at least to let your readers know what's going on.

If you still have access to your blog, you can still post a new widget at the top of your blog that contains text to tell your readers what has happened.

Using Page Elements, create a text widget with a brief message, and position the widget in a conspicuous place on the blog.

Note to Readers - Blogger's spam robot has run amok and has tagged 1000s of blogs, including this one, as "spam." Obviously, I am not a spam blog.

So, if you can't post but you can access the Layout wizard, you can at least let your readers know why you aren't posting.

As far as resolving this for your blog, I'm sure that you have done what a few other bloggers have instinctively done, and started the well known blog review request process.

In this case, and based upon the level of complaints seen so far, I suspect that's going to be a waste of time from you. Unless Blogger brings in extra staff, there's no way that they can review all of the requests generated by this experience. How long does a review requests typically take? Multiply that by 100 (minimum). Would you really want to wait that long?

> > (Update 17:00): Blogger admits to the problem, and implies that they are resolving it on their own.

>> Top

Less Traffic To Our Blogs?

I've been advising bloggers about an essential and sensitive subject - getting more traffic to their blogs - for years. Such a simple activity - post accurate, relevant, and useful articles - and advertise responsibly - the search engines will see you - and the readers will come. But there's a problem here, similar to the chicken and the egg paradox.

If more search engine visibility depends upon more readers, and more readers depends upon better search engine visibility, how do you start the process?

Where did the first chicken come from, anyway?

With Blogger, there is a way around the paradox - the "Next Blog" link, driven by the "Recently Updated Blogs" list. When you post to your blog, your blog goes onto the "Recently Updated Blogs" list. People using the "Next Blog" link access the RUB list, and there they are reading your blog. The more that you post, the more readers you get from "Next Blog".

But, there's a limitation here. Recently, Blogger started making the "Next Blog" link more "family friendly". This effort, prompted by thousands of complaints from people tired of seeing material not suitable for minors - or in some cases - for anybody - was welcomed by many bloggers. Many malicious or unsuitable blogs, detected as spam blogs - simply disappeared from visibility.

But this effort has side effects, not welcomed by all bloggers. The Google spam blog detection is fuzzy, and it's prone to both false negative detection and false positive detection. The former means that not all spam blogs will be detected, and the latter means that not all blogs detected will be spam. This is similar to known problems with automated locking and / or deletion of spam blogs, and with TOS actions against accounts used for setting up and maintaining such blogs.

In my opinion, locking out spam blogs, from "Next Blog" links or from the Recently Updated Blog list, can be tuned to produce false positives, and eliminate false negatives. Locking and / or deletion of blogs, on the other hand, must be much more carefully balanced, as too many false positive detections will lead to too many complaints from owners of blogs falsely locked or deleted. Check the normal forum activity, in GBH: Login Issues and GBH: Publishing Trouble, if you don't understand this problem.

Exclusion of a non spam blog from "Next Blog" links or from the Recently Updated Blog list will be much easier to get away with, even with egregious false positive detection, simply because many blog owners don't know or care about "Next Blog" and the Recently Updated Blog list, nor is it easy to measure "Next Blog" activity. With that in mind, Blogger will likely tune their scanning with the goal of eliminating false negatives - excluding all malicious blogs from "Next Blog" and the Recently Updated Blog list - and there will be many more false positives.

So enjoy the cleaner and more useful "Next Blog" link, but note that there may be a price.

>> Top

The Blog Content Warning May Not Be Voluntary, In All Cases

The "Content Warning" advisory page, appearing ahead of blogs with questionable content, protects the casual blog surfer from viewing content which may be objectionable to some readers. It's presence on any given blog is supposedly the result of voluntary action by a blog owner, who can set "Adult Content?" to "Yes", at his / her discretion.

The presence of the advisory page, supposedly has slight effect upon prospective readers of the blog.

• Prospective readers must read the notice, and decide whether they wish to view possibly gratuitous content, and that after they click through the notice.
• The blog, when listed in a search hit list, will show the text of the content warning, in place of the blog description and post extract.

Recent claims by some readers make it appear that this setting may be, in some cases, not set voluntarily, and that it has additional consequences. The warning page also seems to interfere with the ownership verification process, in Google Webmaster Tools.

>> Forum thread links: bX-*00079

>> Copy this tag: bX-*00079

>> Top

The Daily Coyote

Apparently the blog "The Daily Coyote" was locked as a spam blog, pending investigation. The owner then convinced its readers to conduct a DOS attack against Google Blogger Help, until it was restored to operational status, in the impression that such action would hasten Bloggers reaction.

It was restored 7th of April 2008, and the owner admitted the same, in a post on the blog. Obviously unlocked.

Yet the useless posts continue in Blogger Help Group. This prevents other people, needing help, from being helped promptly.

To the owners of the blog:

You need to again email your readers, and instruct them to knock it off. You aren't bothering Blogger, but you are interfering with other bloggers being helped.

Blogger has a very real problem with spam blogs. If your blog is blocked, or if it's removed, it's not done so trivially, nor are you the only one being so oppressed.

Right now, Daily Coyote whinings are approaching classification as a Denial Of Service Attack.

Go away.

>> Top