From: http://techcrunch.com/2010/09/12/youtube-live-streaming/<p>The widget embedded is rendering this on the page:<p>Traceback (most recent call last):<p><pre><code> File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/__init__.py", line 511, in __call__
handler.get(*groups)
File "/base/data/home/apps/yt-live/1.344714172147360500/event.py", line 69, in get
evs = get_rows()
File "/base/data/home/apps/yt-live/1.344714172147360500/event.py", line 9, in get_rows
client = gdata.spreadsheet.text_db.DatabaseClient('kieran@bynd.com', 'projectmetal')
File "/base/data/home/apps/yt-live/1.344714172147360500/gdata/spreadsheet/text_db.py", line 106, in __init__
self.SetCredentials(username, password)
File "/base/data/home/apps/yt-live/1.344714172147360500/gdata/spreadsheet/text_db.py", line 127, in SetCredentials
raise CaptchaRequired('Please visit https://www.google.com/accounts/'</code></pre>
CaptchaRequired: Please visit https://www.google.com/accounts/DisplayUnlockCaptcha to unlock your account.
One guy's password getting out, in the grand scheme of things, is perhaps not an "epic failure". I mean, it's a screwup all right, but perhaps some perspective is in order...
This reminds me of the time php.net went funny and started outputting all their PHP as text/html - they kept their DB credentials in a file included from their public_html directory and we were able to read the host details and username and password for their CMS.<p>Never ceases to amaze me that even big sites make little mistakes like that!