<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2010:/1/tag:www.readwriteweb.com,2009://1.13800-</id>
  <updated>2010-03-12T04:20:55Z</updated>
  <title>Comments for Twitter OAuth Spotted in the Wild</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=13800" title="Twitter OAuth Spotted in the Wild" />
    <published>2009-02-12T05:00:06Z</published>
    <updated>2009-02-12T08:03:52Z</updated>
    <title>Twitter OAuth Spotted in the Wild</title>
    <summary>Twitter OAuth - oft promised but lagging in delivery - had begun to take on a mythical status, leaving many to wonder if it would ever be released. Now, that naysaying could be coming to swift end. It appears that Twitter OAuth has been released into the wild as part of a limited beta....</summary>
    <author>
      <name>Rick Turoczy</name>
      
    </author>
    
    <category term="Social Web" />
    
    <category term="Twitter" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="twitterOAuth.jpg" src="http://www.readwriteweb.com/twitterOAuth.jpg" width="150" height="216" />Twitter OAuth - <a href="http://explore.twitter.com/al3x/status/981810659">oft promised</a> but <a href="http://louisgray.com/live/2009/01/twitters-oauth-target-slipping-amid.html">lagging in delivery</a> - had begun to take on a mythical status, leaving many to wonder if it would ever be released. Now, that naysaying could be coming to swift end. It appears that <a href="http://blog.inuda.com/2009/02/12/never-share-your-twitter-password-again/">Twitter OAuth has been released into the wild</a> as part of a limited beta.<br />
</p>]]>
      <![CDATA[<p>Why is this important? It means that Twitter applications now have a way to verify user identity without asking for a username and password. Those credentials remain the private property of the user - but he or she still gets access to the tool and his or her Twitter account. (For more on the topic, listen to Chris "<a href="http://twitter.com/factoryjoe">@factoryjoe</a>" Messina talking to Twitter lead API developer Alex "<a href="http://twitter.com/al3x">@al3x</a>" Payne about <a href="http://citizengarden.com/2009/01/08/episode-10-phish-my-phail-whale/">OAuth and Twitter</a>.)</p>

<center><img alt="TwitterInudaSocialPlume.jpg" src="http://www.readwriteweb.com/TwitterInudaSocialPlume.jpg" width="600" height="282" /></center>

<p>The team at inuda - Jonathan "<a href="http://twitter.com/madmotive">@madmotive</a>" Markwell specifically - reports that 150 other developers have been <a href="http://blog.inuda.com/2009/02/12/never-share-your-twitter-password-again/">selected to participate in the OAuth private beta</a>.</p>

<p>And then there's the <a href="http://twitter.com/oauth_clients">Twitter OAuth page</a>, that allows developers with registered apps to review their applications using Twitter. Chris Messina shares the <a href="http://flickr.com/photos/factoryjoe/3273139045/in/photostream/">beta user view</a>, as well.)</p>

<center><img alt="Twitter _ Applications.jpg" src="http://www.readwriteweb.com/Twitter%20_%20Applications.jpg" width="600" height="445" /></center>

<p>How do you know if you're in the beta? According to the <a href="http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a1bc99e2e41bfac4">Twitter Development group</a>:</p>

<blockquote>"If you're one of the 150 or so people included in the closed beta your settings page (<a href="http://twitter.com/account/settings">http://twitter.com/account/settings</a>) now contains a 'Connections' tab. In the sidebar is a little information and a link to register your very own application."</blockquote> 

<p>Needless to say, the news was well received by the <a href="http://search.twitter.com/search?q=twitter+oauth">Twitter development community</a>.</p>

<p>Granted, Twitter OAuth is only in limited beta, but given Markwell's tweets and the <a href="http://blog.inuda.com/2009/02/12/never-share-your-twitter-password-again/">inuda post</a> it appears to be a straightforward implementation:</p>

<blockquote>"We managed to get a prototype up and running within a few minutes with no problems so we think it's fair to say that you should never give your Twitter password to anyone ever again. In a few weeks all developers of Twitter applications will have access to OAuth and they'll have no excuse other than laziness for not using it."</blockquote>

<p>Could we be seeing the <a href="http://www.readwriteweb.com/archives/why_twitters_new_oauth_matters.php">end of apps that ask for your Twitter password</a>? Will OAuth make an appearance in <a href="http://www.readwriteweb.com/archives/new_tweetdeck_out_tomorrow.php">tomorrow's release of Tweetdeck</a>? We can only hope.</p>

<p><em>If you'd like to befriend the ReadWriteWeb staff on Twitter <a href="http://www.agglom.com/webslideshow/52158/RWW_on_Twitter">here are our accounts</a> - we'd love to meet you too!</em></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126319</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126319" />
    <title>Comment from COP on 2009-02-11</title>
    <author>
        <name>COP</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>An offtopic comment on the RWW Ad on right. </p>

<p>In the ad "Discover  the Semantic Web - A Dow Jones Webinar"  - Is that woman drawing OWL/RDF diagram??  u must be joking.. how can such a hottie do RDF? its 1:55AM EST.. may be i m hallucinating.. </p>

<p>( owl:unionOf ROTFL, WTF )</p>]]>
    </content>
    <published>2009-02-12T06:56:20Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126321</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126321" />
    <title>Comment from marksilva on 2009-02-11</title>
    <author>
        <name>marksilva</name>
        <uri>http://twitter.com/marksilva</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://twitter.com/marksilva">
        <![CDATA[<p>This is killer. We think there are huge opportunites & implications for brands and apps dev using OAuth for Twitter. Here are some:</p>

<p>1) Multiple account management tools. Add all your accounts via oauth and use a single account to manage multiple accounts in one place. Who needs multiple accounts? All brands because they have different consumers. For instance, Dell has 18+ twitter accounts, some in 5 languages. A CPG brand may have their wild loyalists and some into them for a specific product feature or attribute.</p>

<p>2) Twitter CRM. If a brand can offer an OAuth access, it will allow someone to follow specific tags or keywords from their streams without having to follow. It will also allow d-m without following to have a back-channel conversation.</p>

<p>3) Instant DM/Search Alerts. If you allow an app access, it can DM you when Tix are on sale, stocks move, your boss is mentioned, etc.</p>

<p>BTW, if you dev any of these tools, message me and we'll beta/apply. Cheers! Mark Silva, Real Branding</p>]]>
    </content>
    <published>2009-02-12T07:08:36Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126347</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126347" />
    <title>Comment from Jonathan Markwell on 2009-02-12</title>
    <author>
        <name>Jonathan Markwell</name>
        <uri>http://twitter.com/madmotive</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://twitter.com/madmotive">
        <![CDATA[<p>Rick - Thank you for the link to my blog post! Great to see so much interest in it.</p>

<p>Mark - Looks like your as excited as we are about this! :)  Our company, Inuda, is now focusing on Twitter application development.  We're also currently running a private beta of a tool that does much of what you are looking for in a Twitter app.  It's called SocialPlume (featured in the screenshot above).  We have a holding page up at <a href="http://socialplume.com" rel="nofollow">http://socialplume.com</a> Please get in touch if you'd like to be one of the first users.</p>]]>
    </content>
    <published>2009-02-12T12:05:04Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126374</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126374" />
    <title>Comment from Adam on 2009-02-12</title>
    <author>
        <name>Adam</name>
        <uri>http://www.timepoke.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.timepoke.com">
        <![CDATA[<p>Awesome - can't wait for access so we can get TimePoke using Twitter/OAuth!</p>]]>
    </content>
    <published>2009-02-12T17:14:01Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126378</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126378" />
    <title>Comment from marksilva on 2009-02-12</title>
    <author>
        <name>marksilva</name>
        <uri>http://twitter.com/marksilva</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://twitter.com/marksilva">
        <![CDATA[<p>Follow-up thought: oAuth is going to become the default and users will avoid sites asking them for their login/pw. I'm already starting to postpone using services until they implement it.</p>]]>
    </content>
    <published>2009-02-12T17:36:56Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:126716</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c126716" />
    <title>Comment from Jeroen de Miranda on 2009-02-14</title>
    <author>
        <name>Jeroen de Miranda</name>
        <uri>http://www.jeroendemiranda.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.jeroendemiranda.com">
        <![CDATA[<p>Robust and reliable implementation of OAuth at Twitter will lead to:</p>

<p>- more visible usage by prominent users: with OAuth they will trust to use Twitter in combination with the many third party add-on applications that are out there;</p>

<p>- faster and broader acceptance in the corporate world, by enabling in a more trusted way integration with corporate systems (CRM systems is just one example; another might be HRM systems).</p>]]>
    </content>
    <published>2009-02-14T16:34:36Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:127776</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c127776" />
    <title>Comment from Henrik Lied on 2009-02-25</title>
    <author>
        <name>Henrik Lied</name>
        <uri>http://bit.ly/twitter_oauth</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://bit.ly/twitter_oauth">
        <![CDATA[<p>I've created a Twitter oAuth app which is available for everyone. Check it out at my labs: <a href="http://bit.ly/twitter_oauth" rel="nofollow">http://bit.ly/twitter_oauth</a></p>]]>
    </content>
    <published>2009-02-25T12:26:43Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:128175</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c128175" />
    <title>Comment from Tyler on 2009-02-28</title>
    <author>
        <name>Tyler</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>FINALLY!</p>]]>
    </content>
    <published>2009-02-28T10:31:15Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:129068</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c129068" />
    <title>Comment from söve on 2009-03-06</title>
    <author>
        <name>söve</name>
        <uri>http://www.sove.name</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.sove.name">
        <![CDATA[<p>Our company, Inuda, is now focusing on Twitter application development. </p>]]>
    </content>
    <published>2009-03-06T22:19:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:157731</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c157731" />
    <title>Comment from KURENG | Hafiz.Z on 2009-09-14</title>
    <author>
        <name>KURENG | Hafiz.Z</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><a href="http://twitoauth.com" rel="nofollow">TwitOAuth</a> is a Twitter Apps gallery showcasing OAuth twitter login sites</p>]]>
    </content>
    <published>2009-09-15T04:04:49Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:164222</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c164222" />
    <title>Comment from Tracy Osborn on 2009-10-22</title>
    <author>
        <name>Tracy Osborn</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Tweepsect.com is a really nice lightweight and ad-free way to see who you're stalking and who's stalking you... and uses JS OAuth. :) </p>]]>
    </content>
    <published>2009-10-22T17:50:20Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13800-comment:196181</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13800" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_oauth_spotted.php#c196181" />
    <title>Comment from TvvitterBug on 2010-03-11</title>
    <author>
        <name>TvvitterBug</name>
        <uri>http://www.tvvitterbug.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.tvvitterbug.com">
        <![CDATA[<p>Great post on OAuth!</p>

<p>TvvitterBug 1.4 Just released on the App Store is fully compliant with both OAuth and xAuth (browser-less authentication) utilizing a 100% organic implementation that insures reliability, keeps code size small, and real-time performance high.  TvvitterBug is one of the "new breed" of Twitter clients for the iPhone, iPod, and iPad that bring a fresh approach to mobile Twittering that focuses more on achieving the highest quality "user experience" (UX), as opposed to simple "feature stuffing" that many of the "old dog" Twitter clients have recently gotten into.</p>

<p>You can look it up on the web at: <a href="http://www.tvvitterbug.com," rel="nofollow">http://www.tvvitterbug.com,</a> or on Twitter.com/TvvitterBug.<br />
</p>]]>
    </content>
    <published>2010-03-12T04:19:13Z</published>
  </entry>

</feed>