A couple more:
http://www.google.com/search?q=wisegeek.com
http://www.google.com/search?q=bizrate.com
----
My reasons for suggesting that these are blocked:
"What are Some Animals Commonly Mistaken for Dinosaurs?" (http://www.wisegeek.com/what-are-some-animals-commonly-mista...)
"How Do I Care for a Rose Breasted Cockatoo?" (http://www.wisegeek.com/how-do-i-care-for-a-rose-breasted-co...)
"Why Does Alaska Have Really Long Days During Some Times of the Year and Really Short Days During Other Times?" (http://www.wisegeek.com/why-does-alaska-have-really-long-day...)
- should be fairly self explanatory. Plus it only took be ~45 seconds to find these examples of journalistic <sarcasm>brilliance</sarcasm> (there's MANY more such examples). Plus they are - IMO - breaking AdSense guidelines since the Google link unit ads are EXACTLY the same (in color/style and :hover behaviour) as the in-content navigation links, which is a direct breach of AdSense policy. You'd think the AdSense team would be aware of such a big violation..
--
And as for BizRate, it's a 99% autogenerated site with little (if any) unique content. Plus most pages have at least one keyword stuffing area (such as http://www.bizrate.com/mens-shoes/dress-shoes/ - see the 'related searches' bit on the left, for a quick example).
Seems like you should do this when you get one of these and you wanted Stackoverflow.
That's an error message from bots that are spamming random wikis. I wrote more about it here:
There are some weird things, too. I see what might be links between mystery numbers in the spam pages and parts of their URL, and I find it odd that they're the only site listed in those error messages, and there aren't a lot of those errors. Which may indicate that they're not deliberately blocking the spambots. But I will concede that it's weak evidence so far at best.
On another note, who is using your blog as feedstock? Can you give a URL to a spun copy of your stuff?
Secondly, the first link that appears for me when you search for experts-exchange is wikipedia.
Unfortunately, i don't and can't use Chrome. If all this does though is send a URL request when a site is blocked, it should be extremely trivial (for someone who is smarter and has more free time than me, probably) to re-implement this in a Firefox-compatible form, right?
Just to be clear we're not scraping content nor SEOing to death. We've been running our mailing list archive for almost 8 years.
To quote Matt_Cutts somewhere else in this thread: 'because USENET/mailing lists don't always have a centralized/canonical location on the web, which makes dupe content more of a potential issue. It's not the usual "Website X copied my website" scenario.'
If you dislike us that's cool, but just know we're not showing in your SERPs because of scraping & SEO trickery. A lot of people, maybe not you, really are finding their answer there. There's a lot of solid answers in inboxes.
google this: site:answers.com "can you answer this question"
32,200,000 of their 103,000,000 answers pages DO NOT HAVE AN ANSWER! They are spamming google’s users to get them to build answer.com’s database of answers. (and surrounding the non-content with heavy ads!)
For the pages that do have an answer, answers.com has gone the way of answers.yahoo.com. (I guess you forgot answers.yahoo.com too)
And, BTW, ask.com is just regurgitating answers.com!!
google this: site:ask.com answers.com
or just surf around ask.com to see that they just regurgitate ALL of the content farm results, which makes ask.com a "content farm" farm
your list was a good start, but you missed the biggest (by far) offenders on the internet.
bigresource is the most annoying, one time those assholes put a fricking CAPTCHA in place so you had to prove you were human to get to the source link they STOLE the content from.
I generally find about.com has high-quality content giving an overview of a topic, much more in-depth than mahalo or eHow.
Just like how someone that weighs the same as a duck must be made of wood, and therefore is a witch.
2. Click Install, close page
3. Open each of the links below in a new tab, click block on the first result
4. Win.
http://www.google.com/search?q=Mahalo
http://www.google.com/search?q=ehow
http://www.google.com/search?q=experts-exchange
http://www.google.com/search?q=livestrong.com
http://www.google.com/search?q=answerbag
http://www.google.com/search?q=bills.com
http://www.google.com/search?q=chacha.com
http://www.google.com/search?q=associated+content
http://www.google.com/search?q=efreedom
http://www.google.com/search?q=questionhub
http://www.google.com/search?q=squidoo.com
http://www.google.com/search?q=about.com
http://www.google.com/search?q=yellowpages.com
----
Edits: fixed formatting, added suggestions
This method is fine. The actual data sent to Google when you block a domain does not contain the search query (or the referrer).
This is what gets sent when you block a domain:
and unblock: (Interestingly the CSRF token is broken when unblocking.)