<?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: Death to Twitter&#8217;s &#8220;Older&#8221; Button</title>
	<atom:link href="http://www.en-dash.com/blog/2008/08/15/death-to-twitters-older-button/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.en-dash.com/blog/2008/08/15/death-to-twitters-older-button/</link>
	<description>Time Makes Fools of Us All</description>
	<lastBuildDate>Wed, 17 Mar 2010 03:30:23 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Nassi</title>
		<link>http://www.en-dash.com/blog/2008/08/15/death-to-twitters-older-button/comment-page-1/#comment-163976</link>
		<dc:creator>Jason Nassi</dc:creator>
		<pubDate>Fri, 15 Aug 2008 16:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.en-dash.com/blog/?p=551#comment-163976</guid>
		<description>Invite sent!</description>
		<content:encoded><![CDATA[<p>Invite sent!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake</title>
		<link>http://www.en-dash.com/blog/2008/08/15/death-to-twitters-older-button/comment-page-1/#comment-163975</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Fri, 15 Aug 2008 16:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.en-dash.com/blog/?p=551#comment-163975</guid>
		<description>Jason:&lt;br&gt;&lt;br&gt;Interesting. Well, as you say, plenty of Twitter&#039;s direct (and indirect) competitors have much more useful interfaces/APIs, but as long as Twitter has the lion&#039;s share of users it&#039;ll be hard to dislodge. For example, FriendFeed can do everything Twitter can, and much more, but outside of my geekiest friends nobody uses it (and if few people use *FriendFeed*, it&#039;s safe to say that almost nobody&#039;s using Plurk or any other competitors, either). And as long as all my friends are on Twitter, I will be, too.&lt;br&gt;&lt;br&gt;So I guess my point is that Twitter is in a lucky position, because of the network effect of its critical mass of users, and now that they seem to have at least muffled the uptime problem I&#039;m hoping they&#039;ll start addressing some of the more glaring interface problems. If they don&#039;t do it, and soon, I&#039;m pretty sure Facebook is going to figure out a way to make its status feature as easy to use and ubiquitous as Twitter ever was.&lt;br&gt;&lt;br&gt;I don&#039;t know anything about Socialthing, but if you can send me an invite I&#039;ll definitely check it out (calamityjake at gmail dot com). Thanks!</description>
		<content:encoded><![CDATA[<p>Jason:</p>
<p>Interesting. Well, as you say, plenty of Twitter&#39;s direct (and indirect) competitors have much more useful interfaces/APIs, but as long as Twitter has the lion&#39;s share of users it&#39;ll be hard to dislodge. For example, FriendFeed can do everything Twitter can, and much more, but outside of my geekiest friends nobody uses it (and if few people use *FriendFeed*, it&#39;s safe to say that almost nobody&#39;s using Plurk or any other competitors, either). And as long as all my friends are on Twitter, I will be, too.</p>
<p>So I guess my point is that Twitter is in a lucky position, because of the network effect of its critical mass of users, and now that they seem to have at least muffled the uptime problem I&#39;m hoping they&#39;ll start addressing some of the more glaring interface problems. If they don&#39;t do it, and soon, I&#39;m pretty sure Facebook is going to figure out a way to make its status feature as easy to use and ubiquitous as Twitter ever was.</p>
<p>I don&#39;t know anything about Socialthing, but if you can send me an invite I&#39;ll definitely check it out (calamityjake at gmail dot com). Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Nassi</title>
		<link>http://www.en-dash.com/blog/2008/08/15/death-to-twitters-older-button/comment-page-1/#comment-163974</link>
		<dc:creator>Jason Nassi</dc:creator>
		<pubDate>Fri, 15 Aug 2008 16:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.en-dash.com/blog/?p=551#comment-163974</guid>
		<description>Jake,&lt;br&gt;Some of Twitter&#039;s competitors have the timeline functionality that you describe, like Plurk.  The problem there for me is that none/very few of the people I follow are using Plurk.  Twitter is the leader in the clubhouse, as far as I&#039;m concerned.&lt;br&gt;&lt;br&gt;Something you might want to try is Socialthing!  Aside from the way that it integrates various social networking services, it also has a different way of displaying updates that might be more to your liking.  Not the timeline concept, but you&#039;ll easily be able to see what&#039;s been updated since your last login.  They&#039;re in private beta (I can send you an invite), and have just been acquired by AOL.</description>
		<content:encoded><![CDATA[<p>Jake,<br />Some of Twitter&#39;s competitors have the timeline functionality that you describe, like Plurk.  The problem there for me is that none/very few of the people I follow are using Plurk.  Twitter is the leader in the clubhouse, as far as I&#39;m concerned.</p>
<p>Something you might want to try is Socialthing!  Aside from the way that it integrates various social networking services, it also has a different way of displaying updates that might be more to your liking.  Not the timeline concept, but you&#39;ll easily be able to see what&#39;s been updated since your last login.  They&#39;re in private beta (I can send you an invite), and have just been acquired by AOL.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
