<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: twitterapi</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/twitterapi.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-08-14T10:01:37+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Blaine Cook</title><link href="https://simonwillison.net/2008/Aug/14/oauth/#atom-tag" rel="alternate"/><published>2008-08-14T10:01:37+00:00</published><updated>2008-08-14T10:01:37+00:00</updated><id>https://simonwillison.net/2008/Aug/14/oauth/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.lukeredpath.co.uk/2008/8/12/on-iphones-and-user-credentials"&gt;&lt;p&gt;OAuth came out of my worry that if the Twitter API became popular, we'd be spreading passwords all around the web. OAuth took longer to finish than it took for the Twitter API to become popular, and as a result many Twitter users' passwords are scattered pretty carelessly around the web. This is a terrible situation, and one we as responsible web developers should work to prevent.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.lukeredpath.co.uk/2008/8/12/on-iphones-and-user-credentials"&gt;Blaine Cook&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/passwords"&gt;passwords&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/phishing"&gt;phishing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitterapi"&gt;twitterapi&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="oauth"/><category term="passwords"/><category term="phishing"/><category term="security"/><category term="twitter"/><category term="twitterapi"/></entry></feed>