Spread the Word

Site Feed



Powered by FeedBlitz

Subscribe with ...

  • Add this blog to my Technorati Favorites!
  • Subscribe in Bloglines
  • Subscribe in NewsGator Online
  • Subscribe in Rojo
  • Add Random 

Bytes (WebLens Blog) to Newsburst from CNET News.com
  • Add to Google
  • Add to My AOL
  • Subscribe in FeedLounge
  • Add to netvibes

Translate This Post

Burn a Feed

Ping the World

Showing posts with label Content Theft. Show all posts
Showing posts with label Content Theft. Show all posts

Wednesday, September 20, 2006

Blog Stolen Again!

Well, I guess imitiation is supposed to be the sincerest form of flattery. But I must confess that, this time, the main emotion I felt on seeing yet another unauthorized copy of this blog floating around the Internet was extreme irritation. At least, now I knew how to proceed.

A few months back, I posted about the shock of learning someone had cloned my blog, and the subsquent struggle to get the illicit copy taken down. This time around, I knew exactly what to do. The offending copy appeared at http://www.pkblogs.com/weblensblogs and at http://www.inblogs.net/weblensblogs. A quick WHOIS check revealed that these sites are hosted by DreamHost.com.

I fired off an email to DreamHost's abuse reporting address, citing the infraction and the name and contact information of the offender (all of which is usually available through a WHOIS query).

A big thumbs-up to DreamHost! Unlike Blogger, they were fast to respond and very co-operative, advising me that — once again — I needed to file a formal complaint under the Digital Millennium Copyright Act. But before I even got that far, I heard back from DreamHost: they had contacted their customer to warn that a complaint was coming. That was all it took. The offending copies were gone in less than 24 hours.

Thursday, May 11, 2006

Getting Blogger to Respond to Content Theft

If you were here a week ago, you'll know that I was furious about my blog being copied wholesale — title, description, posts, categories, web badges, even my profile and photograph. The person's motive for this left me bewildered, as the cloned site linked back to me all over the place.

I have since learned that such theft is becoming quite common, usually motivated by an intent to exploit your content for displaying the thief's AdSense ads. But this idiot left my original ad in the duplicate version. He even left my copyright message intact, for pete's sake!

Concerned about being penalized by Google for duplicate domain spam, I responded immediately with a post about the problem. I then began the frustrating process of communicating with Google and Blogger to let them know that the duplicate content was not mine and to request removal of the offending site.

It took a week, and numerous emails back and forth to Blogger, to get the cloned site removed. That process is worth sharing here in case you encounter similar content theft.

The initial response from Blogger was not helpful. I received a terse boilerplate reply informing me that:

Blogger is a provider of content creation tools, not a mediator of that content. We allow our users to create blogs, but we don't make any claims about the content of these pages. In cases where contact information for the author is listed on the page, we recommend working directly with this person to have this information removed or changed.

There was no contact information on the cloned blog other than my own, and no way to reach or communicate with this person. A battery of emails ensued between me and Blogger. Eventually, Blogger responded with an email containing a cryptic clue:

Based on our policies regarding content removal, we are unable to remove the content in question. However, please be aware that your blog has been reviewed, verified, and cleared for regular use so that it will not appear as potential spam.
Aha! Someone has reviewed the situation and given Random Bytes the seal of approval. But who? Blogger? Google? Both of them? Only when I asked why would Blogger not have policies around this type of illicit use and pointed out that this is a clear violation of my copyright, did Blogger respond with helpful information. That email acknowledged that Blogger does indeed have a policy of responding to notices of infringement under the Digital Millennium Copyright Act. It also outlined, in detail, the process for filing such a notice. You can find the content of that email in this text file.

I followed the steps described in that email a week ago. After one final email entreaty from me, Blogger removed the offending site yesterday. Interesting journey, and encouraging to know that these faceless companies will act when pressed hard enough by their customers.

Lorelle on WordPress has published an excellent series of articles on this topic. For more on how to protect yourself from content theft, visit these links:

Tuesday, May 02, 2006

Blog Piracy Alive and Well

My blog has been highjacked! I don't know how or why this has happened, but someone has cloned my blog index page — categories, feed, web badges, and all. Even my photo.

The cloned copy is at http://dtfka2.blogspot.com/ and it's identical to this blog in every way that I can ascertain. I saw this URL in my blog stats this morning. Imagine my shock on checking it out. (Hopefully, this link won't be live by the time you read this.)

I have no idea why someone would do this. I have contacted Blogger, Google, and this jerk's ISP, and await their response(s) with great interest.

The posts all link to this blog. My concern, of course, is that Google will consider this a duplicate domain, and penalize ME!

I'm also bewildered at how this could happen. Has anyone else had this experience? Please let me know. I would also like to know how we can protect ourselves against this kind of thing.