<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OAuth on Nick Perkins Archive</title><link>https://archive.nickperkins.au/tags/oauth/</link><description>Recent content in OAuth on Nick Perkins Archive</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 19 Aug 2010 00:27:34 +1000</lastBuildDate><atom:link href="https://archive.nickperkins.au/tags/oauth/index.xml" rel="self" type="application/rss+xml"/><item><title>The only way is oAuth!</title><link>https://archive.nickperkins.au/nicholosophy/the-only-way-is-oauth/</link><pubDate>Thu, 19 Aug 2010 00:27:34 +1000</pubDate><guid>https://archive.nickperkins.au/nicholosophy/the-only-way-is-oauth/</guid><description>&lt;p&gt;A reminder for all those who deal with the Twitter API that the cut off has now passed for the end of Basic Auth access to Twitter. For the non-technical out there, this is where you give an application, or a website, your username and password and it logs into Twitter and does something for you.&lt;/p&gt;
&lt;p&gt;From now on, all applications will need to use &lt;a href="http://dev.twitter.com/pages/oauth_faq" title="oAuth FAQ"&gt;oAuth&lt;/a&gt;. I think this is much more secure as the application or website will direct you to Twitter, who would verify who you are and whether you give approval or not. Twitter will also tell the user who is seeking the authorisation, so as an end user I have a better idea of who gets to know what. Developers of Twitter applications have been moving towards this model for a while now and it was pretty much the de facto standard anyway.&lt;/p&gt;</description></item></channel></rss>