Google sends C&D, then gags Facebook code leaker

Even before the code was published on a Blogger hosted blog, Facebook seemed to be suffering serious server configuration problems -- which were even reported by Rich Acosta on the Facebook developers forum. The poster took a portion of the code for "photos.

Even before the code was published on a Blogger hosted blog, Facebook seemed to be suffering serious server configuration problems -- which were even reported by Rich Acosta on the Facebook developers forum. The poster took a portion of the code for "photos.php" and made it available here.

I was browsing through a large photo gallery, and not sure exactly quite happened.. but instead of serving me the page with the next image, I was served the PHP source to the page.

Seemed to be like a one-time thing.. but something that should be looked into regardless.

On the 14th of this month, Google sent the author of a blog hosting the main page code a C&D order which was ignored. Google then took matters into their own hands and deleted the blog that hosted the code themselves with an email that said the following:

Hello,

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):

http://www.chillingeffects.org/notice.cgi?sID=3836

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.

Sincerely, The Blogger Team

I think Google did the right thing here -- the code was obviously posted with malicious, or illegal intent. They went through the proper channels by sending an official C&D before simply deleting the blog, however there is no doubt some people will be upset over the deletion. At least this guy had warning -- unlike Google's own "Custom Search Blog".