<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: I Should Have Heeded My Own Advice About Twitter</title>
	<atom:link href="http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/</link>
	<description>My View of the Real-Time Web - Tech and Rants From Jesse Stay, The "Social" Geek</description>
	<lastBuildDate>Fri, 10 Sep 2010 14:48:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Twitter Starts the Chatter on API Guidelines &#124; Stay N' Alive</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-12562</link>
		<dc:creator>Twitter Starts the Chatter on API Guidelines &#124; Stay N' Alive</dc:creator>
		<pubDate>Fri, 11 Sep 2009 01:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-12562</guid>
		<description>[...] heels of a much broader Terms of Service launched for the general Twitter user today. I&#8217;ve long discussed the need for such guidelines, as many developers are embarking on an unknown adventure when writing [...]</description>
		<content:encoded><![CDATA[<p>[...] heels of a much broader Terms of Service launched for the general Twitter user today. I&#8217;ve long discussed the need for such guidelines, as many developers are embarking on an unknown adventure when writing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: birkin</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-12360</link>
		<dc:creator>birkin</dc:creator>
		<pubDate>Thu, 13 Aug 2009 10:54:08 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-12360</guid>
		<description>hope you will success,that way, we have more bussiness by ourselves, jessestay.</description>
		<content:encoded><![CDATA[<p>hope you will success,that way, we have more bussiness by ourselves, jessestay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taking a Stand on Twitter&#8217;s Auto-DM Policy #endautodm &#124; Stay N' Alive</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-12271</link>
		<dc:creator>Taking a Stand on Twitter&#8217;s Auto-DM Policy #endautodm &#124; Stay N' Alive</dc:creator>
		<pubDate>Sun, 02 Aug 2009 23:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-12271</guid>
		<description>[...] be very hard to require all apps to identify themselves via a developer Terms Of Service (I&#8217;ve talked about this before), either by OAuth or some other means, and then provide the tools necessary to allow users to opt [...]</description>
		<content:encoded><![CDATA[<p>[...] be very hard to require all apps to identify themselves via a developer Terms Of Service (I&#8217;ve talked about this before), either by OAuth or some other means, and then provide the tools necessary to allow users to opt [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: outdoor sinks</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-11833</link>
		<dc:creator>outdoor sinks</dc:creator>
		<pubDate>Fri, 19 Jun 2009 11:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11833</guid>
		<description>Twitter maid our life very easy...using twitter we can do anything.&lt;br&gt;&lt;br&gt;Thanks</description>
		<content:encoded><![CDATA[<p>Twitter maid our life very easy&#8230;using twitter we can do anything.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Auto-Follow Limits Rankle Some &#124; rapid-DEV.net</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-11829</link>
		<dc:creator>Twitter Auto-Follow Limits Rankle Some &#124; rapid-DEV.net</dc:creator>
		<pubDate>Mon, 15 Jun 2009 06:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11829</guid>
		<description>[...] third-party developers don&#8217;t like it, but I think for those being limited to following 365,000 new people per year, life will go [...]</description>
		<content:encoded><![CDATA[<p>[...] third-party developers don&#8217;t like it, but I think for those being limited to following 365,000 new people per year, life will go [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Proposes The Release Of API Limits, Tweet Metadata, Becoming Your Online Identity, And More &#124; Twittercism</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-11698</link>
		<dc:creator>Twitter Proposes The Release Of API Limits, Tweet Metadata, Becoming Your Online Identity, And More &#124; Twittercism</dc:creator>
		<pubDate>Wed, 27 May 2009 11:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11698</guid>
		<description>[...] Twitter themselves have done this several times to developers in the [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter themselves have done this several times to developers in the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-11456</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Thu, 07 May 2009 14:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11456</guid>
		<description>Thanks for the tip re: Dev list - just updated my membership to get email in hopes that I&#039;ll catch this next time.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip re: Dev list &#8211; just updated my membership to get email in hopes that I&#39;ll catch this next time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-2/#comment-11438</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Thu, 07 May 2009 07:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11438</guid>
		<description>Thanks Greg - I just wrote about this.  I thought about this earlier, but it&lt;br&gt;didn&#039;t register to me how many people this was affecting.  I also just&lt;br&gt;noticed the discussion going on in the Dev List.  Now I&#039;ve got to go check&lt;br&gt;out SocialToo&#039;s e-mail forwards.  I don&#039;t think many people are using them,&lt;br&gt;but they would have definitely been affected.</description>
		<content:encoded><![CDATA[<p>Thanks Greg &#8211; I just wrote about this.  I thought about this earlier, but it<br />didn&#39;t register to me how many people this was affecting.  I also just<br />noticed the discussion going on in the Dev List.  Now I&#39;ve got to go check<br />out SocialToo&#39;s e-mail forwards.  I don&#39;t think many people are using them,<br />but they would have definitely been affected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oops, Twitter Does it Again &#124; Stay N' Alive</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-1/#comment-11436</link>
		<dc:creator>Oops, Twitter Does it Again &#124; Stay N' Alive</dc:creator>
		<pubDate>Thu, 07 May 2009 06:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11436</guid>
		<description>[...] app are now broken because they were relying on the plain-text format of the new DM e-mails. In my previous post about Twitter doing this, Greg commented, stating, &#8220;When I first read this post last month I [...]</description>
		<content:encoded><![CDATA[<p>[...] app are now broken because they were relying on the plain-text format of the new DM e-mails. In my previous post about Twitter doing this, Greg commented, stating, &#8220;When I first read this post last month I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://staynalive.com/articles/i-should-have-heeded-my-own-advice-about-twitter/comment-page-1/#comment-11435</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Thu, 07 May 2009 05:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/?p=981#comment-11435</guid>
		<description>Today, without any warning, Twitter switched from text/plain emails for direct messages and new follows to a multi-part mime format with HTML and plain text. Needless to say, if you&#039;d previous coded a direct message bot to work off of email parsing, your bot was now broken.&lt;br&gt;&lt;br&gt;When I first read this post last month I though, &quot;well, if you code your application well, it should take into account potential changes from Twitter.&quot;  I also thought that Twitter would warn us about bigger changes.  Wrong on both counts. Good post, Jesse.</description>
		<content:encoded><![CDATA[<p>Today, without any warning, Twitter switched from text/plain emails for direct messages and new follows to a multi-part mime format with HTML and plain text. Needless to say, if you&#39;d previous coded a direct message bot to work off of email parsing, your bot was now broken.</p>
<p>When I first read this post last month I though, &#8220;well, if you code your application well, it should take into account potential changes from Twitter.&#8221;  I also thought that Twitter would warn us about bigger changes.  Wrong on both counts. Good post, Jesse.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
