<?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"
	>
<channel>
	<title>Comments on: Introducing Twitter support</title>
	<atom:link href="http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 29 Jul 2010 16:14:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: OAuth 1.0 to be issued as an Informational RFC &#171; Test</title>
		<link>http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/#comment-1594</link>
		<dc:creator>OAuth 1.0 to be issued as an Informational RFC &#171; Test</dc:creator>
		<pubDate>Tue, 13 Apr 2010 20:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.imified.com/?p=113#comment-1594</guid>
		<description>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</description>
		<content:encoded><![CDATA[<p>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OAuth 1.0 to be issued as an Informational RFC &#124; VXML Solutions</title>
		<link>http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/#comment-1573</link>
		<dc:creator>OAuth 1.0 to be issued as an Informational RFC &#124; VXML Solutions</dc:creator>
		<pubDate>Fri, 19 Feb 2010 17:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.imified.com/?p=113#comment-1573</guid>
		<description>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</description>
		<content:encoded><![CDATA[<p>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Speaking of Standards &#187; OAuth 1.0 to be issued as an Informational RFC</title>
		<link>http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/#comment-1572</link>
		<dc:creator>Speaking of Standards &#187; OAuth 1.0 to be issued as an Informational RFC</dc:creator>
		<pubDate>Fri, 19 Feb 2010 16:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.imified.com/?p=113#comment-1572</guid>
		<description>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</description>
		<content:encoded><![CDATA[<p>[...] For example, if you were a Twitter user in its earlier days, every time you wanted to use another application or web service with your Twitter account, you had to give that app or service your Twitter user ID and password. There&#8217;s a security issue here in that you are entrusting your credentials to some other company or application &#8211; and trusting that they won&#8217;t share those credentials. There&#8217;s also a configuration issue in that if you change your password you then have to go to all the other services and provide the updated info. Now, with OAuth support in Twitter, when you want to add a new service to interact with your Twitter account, you are prompted to login to your Twitter account and authorize or deny the access for the new service. The key point is that the new service or application never gets your Twitter credentials. (And as another example, OAuth is what our IMified service uses to allow an automated bot to interact with your Twitter account.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LostFocus &#187; Blog Archive &#187; Bookmarks for June 6th through June 24th</title>
		<link>http://blog.imified.com/index.php/2009/06/24/introducing-twitter-support/#comment-1163</link>
		<dc:creator>LostFocus &#187; Blog Archive &#187; Bookmarks for June 6th through June 24th</dc:creator>
		<pubDate>Wed, 24 Jun 2009 15:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.imified.com/?p=113#comment-1163</guid>
		<description>[...] IMified &#187; Blog Archive &#187; Introducing Twitter support &#8211; That is very cool. I should reactive my IMIfied account and play with it. [...]</description>
		<content:encoded><![CDATA[<p>[...] IMified &raquo; Blog Archive &raquo; Introducing Twitter support &#8211; That is very cool. I should reactive my IMIfied account and play with it. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
