<?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: Top 10 Twitter Feature Requests</title>
	<atom:link href="http://developingux.com/2008/06/24/top-10-twitter-feature-requests/feed/" rel="self" type="application/rss+xml" />
	<link>http://developingux.com/2008/06/24/top-10-twitter-feature-requests/</link>
	<description>Caleb Jenkins on Silverlight &#124; .NET &#124; Design &#124; Development &#124; Architecture &#124; Community</description>
	<lastBuildDate>Thu, 11 Mar 2010 00:45:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Caleb Jenkins</title>
		<link>http://developingux.com/2008/06/24/top-10-twitter-feature-requests/comment-page-1/#comment-352</link>
		<dc:creator>Caleb Jenkins</dc:creator>
		<pubDate>Wed, 25 Jun 2008 04:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-352</guid>
		<description>@Alan - That&#039;s true, but some things (like Jabber support, multi-feeds) would help relieve the stress on the system while other features (tracking specifically) will add to it... most of these, I think, would be pretty neutral or at least minimal to the system.

Either way, I think that twitter (more than anything else) has proven the point that the whole application is the user experience (not just the UI). The &quot;ilities&quot; count in UX (Scalability, Reliability, Flexibility, Maintainability)</description>
		<content:encoded><![CDATA[<p>@Alan &#8211; That&#8217;s true, but some things (like Jabber support, multi-feeds) would help relieve the stress on the system while other features (tracking specifically) will add to it&#8230; most of these, I think, would be pretty neutral or at least minimal to the system.</p>
<p>Either way, I think that twitter (more than anything else) has proven the point that the whole application is the user experience (not just the UI). The &#8220;ilities&#8221; count in UX (Scalability, Reliability, Flexibility, Maintainability)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Stevens</title>
		<link>http://developingux.com/2008/06/24/top-10-twitter-feature-requests/comment-page-1/#comment-349</link>
		<dc:creator>Alan Stevens</dc:creator>
		<pubDate>Tue, 24 Jun 2008 11:34:21 +0000</pubDate>
		<guid isPermaLink="false">http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-349</guid>
		<description>I suspect some of these convenience features will come once the uptime is fixed. We could write our own convenience features using the api if they&#039;d stop limiting requests.

++Alan</description>
		<content:encoded><![CDATA[<p>I suspect some of these convenience features will come once the uptime is fixed. We could write our own convenience features using the api if they&#8217;d stop limiting requests.</p>
<p>++Alan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.261 seconds -->
