Posted August 16, 2007 10:45 am by with 6 comments

Tweet about this on TwitterShare on LinkedInShare on Google+Share on FacebookBuffer this page

I guarantee that if you submit a DMCA request to Google–the one you use to request copyrighted material is removed–you won’t get the same rapid response Facebook just got.

After accidentally releasing their own copyrighted code, Facebook sent Google a DMCA take down notice and the company obliged by yanking the Blogger blog that had published the code.

The anonymous owner of the original blog has started a new one, that shows the emails sent by the Blogger team.


As mentioned in our previous email, we work with a third party to post
DMCA notices we receive. The notice we received because of the content on
your site can be found here (once the notice has been posted):

We have had to remove the content mentioned in the complaint from your
blog. If we did not do so, we would be subject to a claim of copyright infringement, regardless of its merits.

Thanks for your understanding.
The Blogger Team


Hmm, if you’re the one that released the copyrighted code to the public, does that negate a DMCA notice? I guess this guy didn’t want to hire the lawyers to find out. 😉

Hat-tip TechCrunch.

  • I like how the blogger set it up on blogspot again instead of hosting elsewhere. I bet this will be a continual game of cat and mouse for this blogger on the blogspot domain. Have fun Google & Facebook!

  • Pingback: Facebook Source Code Removed - CyberNet News()

  • Pingback: JOBMATCHBOX » Blog Archive » Facebook Security Update()

  • Well, I guess if your big enough you could get google to move quickly – or if you have the money to threaten a real lawsuit that is. If it were me, They would probably ignore me and then cliam they have to many emails and contacts [which they ignore] to move quickly to every response.

  • Jason

    Looks like it got removed from Blogger… but I guess if anyone really wanted to see it, its still in google’s cache results at the moment… amusing

  • But who owns info in the blog – creator or hosting?