<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google&#8217;s New CAPTCHA: The Only Way Is Up!</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Mon, 23 Nov 2009 01:39:24 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AlexW</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925852</link>
		<dc:creator>AlexW</dc:creator>
		<pubDate>Thu, 21 May 2009 22:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925852</guid>
		<description>@mark Exactly. If I understand correctly, each image would come to acquire a margin for error *specific* to it, based on the normal distribution of results submitted for it. For instance, a profile shot of a doorway might only allow +-2 degrees of error. Other images might build in larger margins. 

But, yeah, an average of 1:36 seems reasonable to me, and once you start using more than one at a time the number of possible combinations becomes huge.</description>
		<content:encoded><![CDATA[<p>@mark Exactly. If I understand correctly, each image would come to acquire a margin for error *specific* to it, based on the normal distribution of results submitted for it. For instance, a profile shot of a doorway might only allow +-2 degrees of error. Other images might build in larger margins. </p>
<p>But, yeah, an average of 1:36 seems reasonable to me, and once you start using more than one at a time the number of possible combinations becomes huge.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925833</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 21 May 2009 10:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925833</guid>
		<description>If the margin of error is 1 in 36 (as guessed at above) then the odds of fluking all three are 1/36 * 1/36 * 1/36 = 1 in 46656. If you reduce this margin of error then it increases significantly - say 2/360 * 2/360 * 2/360 = 6 in 46656000 = 1 in 7776000.

A lot of people seem to be assuming that the same picture will always be rotated by the same amount, and therefore when you get it correct you can store that value somewhere. I would assume the picture is rotated a random amount each time it is presented, meaning you couldn&#039;t assume the same values, and also if you gave the picture a different file name how would you know which picture was being shown? You could also run filters over the images to change them maybe?

I guess image recognition might advance to the point where a machine can tell what it is (like facial recognition), but couldn&#039;t you just put the same squiggly lines over it that any current CAPTCHA has?</description>
		<content:encoded><![CDATA[<p>If the margin of error is 1 in 36 (as guessed at above) then the odds of fluking all three are 1/36 * 1/36 * 1/36 = 1 in 46656. If you reduce this margin of error then it increases significantly &#8211; say 2/360 * 2/360 * 2/360 = 6 in 46656000 = 1 in 7776000.</p>
<p>A lot of people seem to be assuming that the same picture will always be rotated by the same amount, and therefore when you get it correct you can store that value somewhere. I would assume the picture is rotated a random amount each time it is presented, meaning you couldn&#8217;t assume the same values, and also if you gave the picture a different file name how would you know which picture was being shown? You could also run filters over the images to change them maybe?</p>
<p>I guess image recognition might advance to the point where a machine can tell what it is (like facial recognition), but couldn&#8217;t you just put the same squiggly lines over it that any current CAPTCHA has?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: omnicity</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925652</link>
		<dc:creator>omnicity</dc:creator>
		<pubDate>Fri, 15 May 2009 19:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925652</guid>
		<description>&quot;You only have to look at the comparatively plodding movements of Honda’s Asimo robot or robot soccer to understand just how taxing a task this can be for a machine.&quot;

I&#039;m sorry, but a physical machine trying to imitate natural motion, as an actual method of locomotion has nothing in common with image processing. 
This task would probably not need any understanding of the image: if it is possible to detect horizontal or vertical lines in the image, then that gives a completely dumb algorithm a one in four chance of getting a single image right, and therefore 1 in 64 chance with three images, which is easily enough for a brute force approach.</description>
		<content:encoded><![CDATA[<p>&#8220;You only have to look at the comparatively plodding movements of Honda’s Asimo robot or robot soccer to understand just how taxing a task this can be for a machine.&#8221;</p>
<p>I&#8217;m sorry, but a physical machine trying to imitate natural motion, as an actual method of locomotion has nothing in common with image processing.<br />
This task would probably not need any understanding of the image: if it is possible to detect horizontal or vertical lines in the image, then that gives a completely dumb algorithm a one in four chance of getting a single image right, and therefore 1 in 64 chance with three images, which is easily enough for a brute force approach.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: FastLionDesign</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925562</link>
		<dc:creator>FastLionDesign</dc:creator>
		<pubDate>Thu, 14 May 2009 00:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925562</guid>
		<description>I think a website should present the beginning of a joke. Then the websurfer would have to provide the punchline (instead of a captcha).

Spammers are a dour, humorless bunch. They wouldn&#039;t be able to figure it out.

George
&lt;a href=&quot;http://www.fastliondesign.com&quot; rel=&quot;nofollow&quot;&gt;www.fastliondesign.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I think a website should present the beginning of a joke. Then the websurfer would have to provide the punchline (instead of a captcha).</p>
<p>Spammers are a dour, humorless bunch. They wouldn&#8217;t be able to figure it out.</p>
<p>George<br />
<a href="http://www.fastliondesign.com" rel="nofollow">http://www.fastliondesign.com</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: AlexW</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925519</link>
		<dc:creator>AlexW</dc:creator>
		<pubDate>Wed, 13 May 2009 01:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925519</guid>
		<description>@michael @smarsh  Guys, as this is a research paper, it has no current real world implementation, so you can&#039;t assume it won&#039;t have an accessible audio fallback option. 

Now, it won&#039;t be an audio equivalent of this system -- I can&#039;t imagine how that would work. But there&#039;s no reason why it should be, is there? 

So, I can&#039;t see why we&#039;d be any worse off, and in many ways we should be better off.</description>
		<content:encoded><![CDATA[<p>@michael @smarsh  Guys, as this is a research paper, it has no current real world implementation, so you can&#8217;t assume it won&#8217;t have an accessible audio fallback option. </p>
<p>Now, it won&#8217;t be an audio equivalent of this system &#8212; I can&#8217;t imagine how that would work. But there&#8217;s no reason why it should be, is there? </p>
<p>So, I can&#8217;t see why we&#8217;d be any worse off, and in many ways we should be better off.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: michael - ohio</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925502</link>
		<dc:creator>michael - ohio</dc:creator>
		<pubDate>Tue, 12 May 2009 14:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925502</guid>
		<description>Smarsh is correct: A CAPTCHA system which does not provide an audio option is not viable for any serious website as it would be inacessible to a significant number of people. Assuming that the details of the visual interaction can be worked out - what would the audio option be for the sight impaired?</description>
		<content:encoded><![CDATA[<p>Smarsh is correct: A CAPTCHA system which does not provide an audio option is not viable for any serious website as it would be inacessible to a significant number of people. Assuming that the details of the visual interaction can be worked out &#8211; what would the audio option be for the sight impaired?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: smarsh</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925471</link>
		<dc:creator>smarsh</dc:creator>
		<pubDate>Tue, 12 May 2009 02:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925471</guid>
		<description>There is soooooo much on this site about accessibility - even a forum. It&#039;s a joke to consider captcha a good thing while touting the need for accessible web sites.

One or the other people - make up your minds!</description>
		<content:encoded><![CDATA[<p>There is soooooo much on this site about accessibility &#8211; even a forum. It&#8217;s a joke to consider captcha a good thing while touting the need for accessible web sites.</p>
<p>One or the other people &#8211; make up your minds!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AlexW</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925467</link>
		<dc:creator>AlexW</dc:creator>
		<pubDate>Tue, 12 May 2009 00:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925467</guid>
		<description>If you read the detail of the white paper, the user would be presented with more than one image to re-orient (three most likely). I guess you could think of this like a combination barrel lock. A machine might well fluke one at the right angle, but acing all three would be tough.

This also provides a test bed for images. Some images are going to be less obvious than others -- for instance a close-up of table setting versus a person standing in a doorway.

As data accrues the table setting shot might allow for a +-10 degree margin for error. The door shot may only allow 2 degrees. The system would learn.

This means, like spam email filtering, the system will automatically evolve and improve as people use it.

@melissapbr I doubt you would try to produce an audio equivalent of this method. What is the audio equivalent of up? I would think this would be teamed with more traditional accessible fallback options.</description>
		<content:encoded><![CDATA[<p>If you read the detail of the white paper, the user would be presented with more than one image to re-orient (three most likely). I guess you could think of this like a combination barrel lock. A machine might well fluke one at the right angle, but acing all three would be tough.</p>
<p>This also provides a test bed for images. Some images are going to be less obvious than others &#8212; for instance a close-up of table setting versus a person standing in a doorway.</p>
<p>As data accrues the table setting shot might allow for a +-10 degree margin for error. The door shot may only allow 2 degrees. The system would learn.</p>
<p>This means, like spam email filtering, the system will automatically evolve and improve as people use it.</p>
<p>@melissapbr I doubt you would try to produce an audio equivalent of this method. What is the audio equivalent of up? I would think this would be teamed with more traditional accessible fallback options.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: melissapbr</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925455</link>
		<dc:creator>melissapbr</dc:creator>
		<pubDate>Mon, 11 May 2009 16:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925455</guid>
		<description>what would be the accessible alternative for screen reader users?</description>
		<content:encoded><![CDATA[<p>what would be the accessible alternative for screen reader users?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: peach</title>
		<link>http://www.sitepoint.com/blogs/2009/05/10/googles-new-capcha-the-only-way-is-up/comment-page-1/#comment-925432</link>
		<dc:creator>peach</dc:creator>
		<pubDate>Mon, 11 May 2009 09:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9195#comment-925432</guid>
		<description>if google would use a pool of images like flickr they&#039;re going to have a substantial miss-rate from people who cant take picutres straight. Im pretty sure my mobile phone pictures that I upload are rarely straight,</description>
		<content:encoded><![CDATA[<p>if google would use a pool of images like flickr they&#8217;re going to have a substantial miss-rate from people who cant take picutres straight. Im pretty sure my mobile phone pictures that I upload are rarely straight,</p>]]></content:encoded>
	</item>
</channel>
</rss>
