9 files changed, 44 insertions, 0 deletions
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/calmobile.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/calmobile.jpg
new file mode 100644
index 0000000..f9201fa
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/calmobile.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/gcal.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/gcal.jpg
new file mode 100644
index 0000000..d033b4d
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/gcal.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/mobilecal.txt b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/mobilecal.txt
new file mode 100644
index 0000000..db13988
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/mobilecal.txt
@@ -0,0 +1,11 @@
+Google quietly added a new mobile version of Google calendar to the site yesterday. The new mobile-optimized version of Google Calendar can be found by pointing your phone to [calendar.google.com][1].
+
+The Google Blog reports that the mobile version of Calendar will display "your agenda of upcoming events, complete with details like date, time, location, description, and guest list."
+
+The new site is nice, but I can't help thinking that the mobile version should have been available from the beginning. Better late than never I guess.
+
+Screenshot from the official site:
+
+
+
+[1]: http://www.google.com/calendar/m "Google Calendar Mobile Edition"
+\ No newline at end of file
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osx.txt b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osx.txt
new file mode 100644
index 0000000..22d2846
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osx.txt
@@ -0,0 +1,9 @@
+Apple has released a new security update for Mac OS X, which patches a number of vulnerabilities including a fairly serious flaw in CoreGraphics. The CoreGraphics flaw could allow a malicious PDF file to crash an application and create a buffer overflow which would allow for the execution of malicious code. 
+
+A number of the other significant patches include fixes for open source programs like Bind, Fetchmail, and contab. Aside from CoreGraphics the most serious flaw in an Apple program affects iChat and could also allow remote code execution.
+
+The new update is available via the Software Update pane in OS X's System Preferences, or direct from [the Apple site][1].
+
+This marks the fifth security update from Apple this year, which, while not an official monthly occurrence like Microsoft's "patch Tuesdays," seems to be settling into a regular pattern.
+
+[1]: http://www.apple.com/support/downloads/ "Apple Support: Downloads"
+\ No newline at end of file
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osxsm.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osxsm.jpg
new file mode 100644
index 0000000..8b030d4
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/osxsm.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap1.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap1.jpg
new file mode 100644
index 0000000..16037ae
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap1.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap2.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap2.jpg
new file mode 100644
index 0000000..1e604d3
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recap2.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recapi.jpg b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recapi.jpg
new file mode 100644
index 0000000..7a59abe
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recapi.jpg
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recaptcha.txt b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recaptcha.txt
new file mode 100644
index 0000000..266b44d
--- /dev/null
+++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/05.21.07/Fri/recaptcha.txt
@@ -0,0 +1,24 @@
+Thanks to the wonderful world of spammers most websites these days rely on CAPTCHA images to force users to prove they are human before accepting comments or other user feedback. In fact humans solve roughly 60 million CAPTCHAs a day according to a the people behind [reCAPTCHA][1] a group that wants to leverage that effort to help digitizing books.
+
+ReCAPTCHA wants to improve the process of digitizing books by sending words that cannot be read by computers to the web in the form of CAPTCHAs for humans to decipher.
+
+The idea behind reCAPTCHA is that, as long as we're all solving these CAPTCHA puzzles, why not throw in some minimal additional data? By adding a second image with an unsolved word from the [Internet Archive][3] book scanning project, ReCAPTCHA allows users to channel their CAPTCHA solving skills into real world benefits.
+
+The Internet Archive and other similar initiatives are busy scanning the world's books and converting them to text via OCR technology. But of course OCR is far from perfect, often there are unreadable words in the scans that require a human to make a decision. Tedious work to be sure.
+
+The reCAPTCHA idea works by taking each word that cannot be read correctly by OCR and creating a CAPTCHA image out of it. 
+
+But, you may be thinking, if the OCR software doesn't know the word, then how does the CAPTCHA software know that the solution has been correctly entered?
+
+Here's an explanation from the reCAPTCHA site:
+
+>But if a computer can't read such a CAPTCHA, how does the system know the correct answer to the puzzle? Here's how: Each new word that cannot be read correctly by OCR is given to a user in conjunction with another word for which the answer is already known. The user is then asked to read both words. If they solve the one for which the answer is known, the system assumes their answer is correct for the new one. The system then gives the new image to a number of other people to determine, with higher confidence, whether the original answer was correct.
+
+Since we're all stuck solving CAPTCHAs anyway, the reCAPTCHA project makes perfect sense. If you'd like to use the system head over to the reCAPTCHA site and have a look at the [various options][2] for including the CAPTCHAs on your site -- there are already plugins for WordPress and PHP.
+
+[via [Hackszine][4]]
+
+[1]: http://recaptcha.net/ "reCAPTCHA"
+[2]: http://recaptcha.net/resources.html "reCAPTCHA resources"
+[3]: http://www.archive.org/index.php "Internet Archive"
+[4]: http://www.hackszine.com/blog/archive/2007/05/recaptcha_distributed_book_dig.html?CMP=OTC-7G2N43923558 "reCAPTCHA: distributed book digitization while fighting spam"
+\ No newline at end of file