<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[dichotic noise]]></provider_name><provider_url><![CDATA[http://gridinoc.name/blog]]></provider_url><author_name><![CDATA[Laurian]]></author_name><author_url><![CDATA[http://gridinoc.name/blog/author/admin/]]></author_url><title><![CDATA[Twitter to employ CAPTCHA tweets to keep bots out]]></title><type><![CDATA[link]]></type><html><![CDATA[<img
class="aligncenter size-medium wp-image-112" title="twitter-captcha" src="/blog/wp-content/uploads/2009/10/twitter-captcha-300x226.png" alt="twitter-captcha" width="300" height="226" />In a near dark future we may have to go this way. Have our public tweets bot proof, and the Twitter API returning base64 encoded images of our tweets instead of text, unless you're a really good friend ... then you may have some of your friends sell your plain text tweets to advertisers, friends hacking friends' accounts to harvest more sellable tweets, etc.Well, that's a dark vision of the future, fueled by the readings I'm doing for a Cyberpunk course at the <a
href="http://p2pu.org/">Peer 2 Peer University</a>.]]></html></oembed>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached
Page Caching using memcached (request URI is rejected)
Database Caching 3/10 queries in 0.003 seconds using memcached

Served from: gridinoc.name @ 2010-09-08 06:40:59 -->