Chris Salmon Technologies

Valleywag over on Gawker (one of my favorite Silicon Valley & Tech gossip sites) revealed, apparently in near real-time, that Facebook pushed out a code bug that revealed private, personal email addresses to the open web last night for about 30 minutes.  This follows last months' flub when they sent personal messages to the wrong people ( chuckle, hehe :-D ).  Mashable quotes a "Facebook Spokesperson" (?) as follows:

“Last night during Facebook’s regular code push, a bug caused hidden e-mail addresses to be visible briefly. The bug was detected within minutes and corrected.”

Hmm... it appears to me, not to give anyone ideas, but I'm sure you could set up some network scripts running continuously to probe some various Facebook data you wanted to retrieve, sort of examine their "nooks & crannies" then just wait for them to screw up and accidentally leave the door open for a bit during one of their regular code pushes.  But you know, it's just thinking out loud on my part.  You'd have to move the IP source of the probe around or they'd see it and block you, too, of course.

Facebook has a tough job.  But they should be well-funded enough, patient and skilled enough, to perhaps do more testing on the code they so frequently update.  It seems they are in a constant rush to "improve" "upgrade" "update" "close holes" and etc., etc.,  As I used to tell some of my over-enthusiastic staff members, when they would again do an "upgrade" or a "patch" that broke something on one of our many services, "We don't need to worry about hackers finding a hole - hell, you've just hacked us yourself."