<?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: Sign in with Twitter</title>
	<atom:link href="http://test.latko.org/?feed=rss2&#038;p=347" rel="self" type="application/rss+xml" />
	<link>http://test.latko.org/?p=347</link>
	<description>A Misanthropic Anthropoid With Something to Say</description>
	<lastBuildDate>Sun, 13 Nov 2022 02:54:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adnan</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3905</link>
		<dc:creator>Adnan</dc:creator>
		<pubDate>Tue, 09 Jun 2009 05:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3905</guid>
		<description>I already have read FAQs, but couldn&#039;t find anything specific to mobile/desktop applications. I know how to implement &quot;Sign in with Twitter&quot; for web applications but I need to know how to do this in mobile application without opening the browser. 
 
Thanks </description>
		<content:encoded><![CDATA[<p>I already have read FAQs, but couldn&#039;t find anything specific to mobile/desktop applications. I know how to implement &quot;Sign in with Twitter&quot; for web applications but I need to know how to do this in mobile application without opening the browser. </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Latko</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3904</link>
		<dc:creator>Chris Latko</dc:creator>
		<pubDate>Tue, 09 Jun 2009 05:12:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3904</guid>
		<description>You can get more info on implementation at &lt;a href=&quot;http://apiwiki.twitter.com/OAuth-FAQ.&quot; target=&quot;_blank&quot;&gt;http://apiwiki.twitter.com/OAuth-FAQ.&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>You can get more info on implementation at <a href="http://apiwiki.twitter.com/OAuth-FAQ." target="_blank"></a><a href="http://apiwiki.twitter.com/OAuth-FAQ" rel="nofollow">http://apiwiki.twitter.com/OAuth-FAQ</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adnan</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3901</link>
		<dc:creator>Adnan</dc:creator>
		<pubDate>Tue, 09 Jun 2009 04:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3901</guid>
		<description>I am interested to know how to implement this authentication process using &quot;Sign in with Twitter&quot; </description>
		<content:encoded><![CDATA[<p>I am interested to know how to implement this authentication process using &quot;Sign in with Twitter&quot;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Latko</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3788</link>
		<dc:creator>Chris Latko</dc:creator>
		<pubDate>Sat, 06 Jun 2009 16:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3788</guid>
		<description>I&#039;ve seen more and more of the &quot;Sign on with Twitter&quot; to allow for simple functionality on sites such as commenting on Disqus. I was wrong about the outcome of OAuth. But to date I&#039;ve seen it used more to authenticate apps than as a single sign-on approach. </description>
		<content:encoded><![CDATA[<p>I&#039;ve seen more and more of the &quot;Sign on with Twitter&quot; to allow for simple functionality on sites such as commenting on Disqus. I was wrong about the outcome of OAuth. But to date I&#039;ve seen it used more to authenticate apps than as a single sign-on approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adnan</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3783</link>
		<dc:creator>Adnan</dc:creator>
		<pubDate>Sat, 06 Jun 2009 08:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3783</guid>
		<description>I have seen many mobile applications which support &quot;Sign in with Twitter&quot;. 
For example: Twitter Mobile 
(http://www.twittermobile.co.uk/index.php)

If you the screenshots, it shows that they support Sign in with Twitter without opening browser.

Please have a look at it.</description>
		<content:encoded><![CDATA[<p>I have seen many mobile applications which support &#8220;Sign in with Twitter&#8221;.<br />
For example: Twitter Mobile<br />
(<a href="http://www.twittermobile.co.uk/index.php" rel="nofollow">http://www.twittermobile.co.uk/index.php</a>)</p>
<p>If you the screenshots, it shows that they support Sign in with Twitter without opening browser.</p>
<p>Please have a look at it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gc</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-1544</link>
		<dc:creator>gc</dc:creator>
		<pubDate>Mon, 20 Apr 2009 23:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-1544</guid>
		<description>Good post! 

I do agree with you on the comment regarding the reliability of some if not most third party apps and the people behind them. This is where establishing credibility and trust with your user base comes in.

IMO, I don&#039;t think twitter is aiming at SSO like openID is. Personally, I plan to use OAuth simply because I plan to only target twitter users (6 or 7 millions, or more...)! My goal is simply to not obligate users to have to register (yet again) for another service if it&#039;s related to something they already use daily, and I think OAuth is good for that.</description>
		<content:encoded><![CDATA[<p>Good post! </p>
<p>I do agree with you on the comment regarding the reliability of some if not most third party apps and the people behind them. This is where establishing credibility and trust with your user base comes in.</p>
<p>IMO, I don&#8217;t think twitter is aiming at SSO like openID is. Personally, I plan to use OAuth simply because I plan to only target twitter users (6 or 7 millions, or more&#8230;)! My goal is simply to not obligate users to have to register (yet again) for another service if it&#8217;s related to something they already use daily, and I think OAuth is good for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clatko</title>
		<link>http://test.latko.org/?p=347&#038;cpage=1#comment-3821</link>
		<dc:creator>clatko</dc:creator>
		<pubDate>Mon, 20 Apr 2009 23:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=347#comment-3821</guid>
		<description>&lt;p&gt;Published a new blog post: Sign in with Twitter @ &lt;a href=&quot;http://bit.ly/6ETlc&quot;&gt;http://bit.ly/6ETlc&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;i&gt;This comment was originally posted on &lt;a href=&quot;http://twitter.com/clatko/statuses/1569985865&quot; rel=&quot;nofollow&quot;&gt;Twitter&lt;/a&gt;&lt;/i&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Published a new blog post: Sign in with Twitter @ <a href="http://bit.ly/6ETlc">http://bit.ly/6ETlc</a></p>
<p><i>This comment was originally posted on <a href="http://twitter.com/clatko/statuses/1569985865" rel="nofollow">Twitter</a></i></p>
]]></content:encoded>
	</item>
</channel>
</rss>
