<?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: Twitter Features That Should Already Exist</title>
	<atom:link href="http://tomuse.com/twitter-features/feed/" rel="self" type="application/rss+xml" />
	<link>http://tomuse.com/twitter-features/</link>
	<description>helpful web tips and technology tools</description>
	<lastBuildDate>Mon, 19 Apr 2010 16:08:08 -0700</lastBuildDate>
	<generator>http://wordpress.org/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Kevin Eklund</title>
		<link>http://tomuse.com/twitter-features/#comment-929</link>
		<dc:creator>Kevin Eklund</dc:creator>
		<pubDate>Wed, 19 Aug 2009 19:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://tomuse.com/?p=5194#comment-929</guid>
		<description>Yeah, more info about a new Twitter follower would be very useful.  I&#039;m looking forward to the retweet feature but if that&#039;s created by Twitter, it&#039;s going to have drastic effects on Tweetmeme and Retweet (yet to be launched).</description>
		<content:encoded><![CDATA[<p>Yeah, more info about a new Twitter follower would be very useful.  I&#8217;m looking forward to the retweet feature but if that&#8217;s created by Twitter, it&#8217;s going to have drastic effects on Tweetmeme and Retweet (yet to be launched).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Miller</title>
		<link>http://tomuse.com/twitter-features/#comment-926</link>
		<dc:creator>Robert Miller</dc:creator>
		<pubDate>Wed, 19 Aug 2009 15:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://tomuse.com/?p=5194#comment-926</guid>
		<description>Twitter should further enhance the &quot;new follower email&quot; to include a user&#039;s full set of profile information to speed up the process of identifying spammy followers.

Techcrunch reported that a retweet feature is in the works which should meet your needs without adding bloat. The other features you desire don&#039;t ring true for me but I am not that heavy of a Twitter user.</description>
		<content:encoded><![CDATA[<p>Twitter should further enhance the &#8220;new follower email&#8221; to include a user&#8217;s full set of profile information to speed up the process of identifying spammy followers.</p>
<p>Techcrunch reported that a retweet feature is in the works which should meet your needs without adding bloat. The other features you desire don&#8217;t ring true for me but I am not that heavy of a Twitter user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joel hughes</title>
		<link>http://tomuse.com/twitter-features/#comment-903</link>
		<dc:creator>joel hughes</dc:creator>
		<pubDate>Sun, 16 Aug 2009 06:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://tomuse.com/?p=5194#comment-903</guid>
		<description>Hi, thought provoking article

I think Twitter are probably very wary of a move away from the &quot;open ended&quot; approach to more &quot;functional&quot; one. What do I mean by this?

Well &quot;open ended&quot; is, as now, where you&#039;ve got few buttons/facilities etc and you&#039;ve got to accomplish everything you need within the tweet itself. A benefit here is a simple, uncluttered interface (and a lower hurdle for third party clients to implement) but a downside is that users have to get the format of the tweet right otherwise problems occurs. If you want to put &quot;meta data&quot; in a tweet then you need hashtags - e.g &quot;ran #5K today in #45mins (#excercise-plotter)&quot; - get the tweet format right then a third party app can do all manner of things with the data.

&quot;Functional&quot; is more like Facebook where they don&#039;t expect the tweet to have any meta data in it as they would explicitly gather such data using buttons etc. Eg look at how FB capture information on your latest run etc? Buttons/duration etc - very functional - which leads to good quality data but the interface is more complex and there is a bigger learning curve.

Given that FB are trying to fight the bloat with &quot;Facebook Lite&quot; I would assume that Twitter are very wary about putting on weight - they know they have to - they just want to put it on in the right places!

Sorry for the long comment - I got carried on my away on my Blackberry whilst my daughter watched early morning tv.

:)</description>
		<content:encoded><![CDATA[<p>Hi, thought provoking article</p>
<p>I think Twitter are probably very wary of a move away from the &#8220;open ended&#8221; approach to more &#8220;functional&#8221; one. What do I mean by this?</p>
<p>Well &#8220;open ended&#8221; is, as now, where you&#8217;ve got few buttons/facilities etc and you&#8217;ve got to accomplish everything you need within the tweet itself. A benefit here is a simple, uncluttered interface (and a lower hurdle for third party clients to implement) but a downside is that users have to get the format of the tweet right otherwise problems occurs. If you want to put &#8220;meta data&#8221; in a tweet then you need hashtags &#8211; e.g &#8220;ran #5K today in #45mins (#excercise-plotter)&#8221; &#8211; get the tweet format right then a third party app can do all manner of things with the data.</p>
<p>&#8220;Functional&#8221; is more like Facebook where they don&#8217;t expect the tweet to have any meta data in it as they would explicitly gather such data using buttons etc. Eg look at how FB capture information on your latest run etc? Buttons/duration etc &#8211; very functional &#8211; which leads to good quality data but the interface is more complex and there is a bigger learning curve.</p>
<p>Given that FB are trying to fight the bloat with &#8220;Facebook Lite&#8221; I would assume that Twitter are very wary about putting on weight &#8211; they know they have to &#8211; they just want to put it on in the right places!</p>
<p>Sorry for the long comment &#8211; I got carried on my away on my Blackberry whilst my daughter watched early morning tv.</p>
<p> <img src='http://tomuse.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://tomuse.com/twitter-features/#comment-901</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Sun, 16 Aug 2009 00:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://tomuse.com/?p=5194#comment-901</guid>
		<description>While tweetmeme does a good job of voting up popular LINKS, services like dailyRT are better at showing popular TWEETS. I&#039;m pretty sure dailyRT does a good job of &quot;quantifying&quot; popular tweets.</description>
		<content:encoded><![CDATA[<p>While tweetmeme does a good job of voting up popular LINKS, services like dailyRT are better at showing popular TWEETS. I&#8217;m pretty sure dailyRT does a good job of &#8220;quantifying&#8221; popular tweets.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
