Skip to main content

CloudFlare's ScrapeShield spots single line of text copy/pasted from my blog

Some months ago CloudFlare launched a service called ScrapeShield that's designed to protect web page content from content scraping. It's a free service and I enabled it on this blog. The ScrapeShield report shows where my blog content has been copied around the web.

It doesn't get copied very often, but just the other day there was a great example of how ScrapeShield spots taken content: I wrote a popular blog entry about Mars Curiosity; someone saw it and wrote their own version taking a single line of text from my blog. ScrapeShield caught it.

My article was Curiosity Rover writes Morse Code of JPL everywhere it goes and a web site owner obviously read it and added this section to an article called "Five awesome things about Curiosity":

That's not the photo that I used, nor is that the text I wrote, but the caption under the photograph is a copy/paste of the title of my article. How am I sure? Because when they copy and pasted, they copy and pasted one of the beacons inserted by ScrapeShield.

ScrapeShield inserts multiple page beacons of different types to spot manual and automatic page scraping. In this case just a single line of text was enough to know that the content came from this blog. Sadly, the web site did not link back here so people could read the full blog post.


bbot said…
Yeah, but that only works if people are dumb enough to copy the 1x1 gif. Not just copy, hotlink.
Unknown said…
Nice Post!!
Unknown said…
Nice one!!

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of