FacebookSecrets, the site that shared the code released by the Facebook servers, has been shut down with a DMCA notice. At this point, it’s popped back up as a SBlog (Spam Blog) and the original author has popped up, yet again.
This time, (s)he has published the notices Google has forwarded onto them. Check out that new blog. The blogger apparently tried to contact Google about the notice because there is a second email that is shared stating that Google had to work with a third party otherwise they themselves would be infringing on copyright.
So where does all of this end? Facebook, unintentionally, leaked their code. It was effectively published online for all to see and someone took the chance to publish that code in other places. To use the Journalist world - if you worked on the story of your life and left it sitting on a copier for 5 minutes - do you think someone would copy this great story and publish it before you? Of course they would.
If I where dumb enough to leave my code hanging out to dry, especially the way Facebook’s code looked, I wouldn’t spend time and money on take down notices. My entire dev team would be renaming functions, recoding and changing things around to make the site more secure and a little faster. Facebook needs to count their blessings that they’re include files for the database where not leaked or found. With server names, usernames, password, etc - it could have been nasty, unless it happened and no one is talking.
