<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chris Brakebill &#187; retweet</title>
	<atom:link href="http://chrisbrakebill.com/tag/retweet/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisbrakebill.com</link>
	<description>I&#039;m afraid I&#039;ll create Skynet...</description>
	<lastBuildDate>Tue, 27 Jul 2010 15:19:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>More on why the old retweet sucks</title>
		<link>http://chrisbrakebill.com/2009/12/22/more-on-why-old-retweet-sucks/</link>
		<comments>http://chrisbrakebill.com/2009/12/22/more-on-why-old-retweet-sucks/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 19:04:17 +0000</pubDate>
		<dc:creator>Chris Brakebill</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[retweet]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.brakeronenine.com/?p=463</guid>
		<description><![CDATA[I&#8217;d like to add a little further add to my previous post on the old retweet.  Frankly, I think the old retweet sucks.  And I think those that argue that the new version doesn&#8217;t allow for commentary are right, but wrong that the old solution is at all a good way to go about providing]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d like to add a little further add to my <a href="http://www.brakeronenine.com/2009/12/21/what-to-do-with-the-old-rt/" target="_blank">previous post</a> on the old retweet.  Frankly, I think the old retweet sucks.  And I think those that argue that the new version doesn&#8217;t allow for commentary are right, but wrong that the old solution is at all a good way to go about providing that commentary.</p>
<p>I&#8217;d say that in 90% of cases, a tweet is too long for someone to retweet and be able to provide any kind of additional comment that creates value.  So what do you do? You either alter the tweet to make it shorter so you can add what you want or you say something brilliant like &#8220;agree&#8221; or &#8220;wow&#8221;.</p>
<p>In the first situation you&#8217;re changing someone&#8217;s message.  You are altering what they had to say, making it hard for your followers to REALLY know what they said.  Someone could easily alter that message in a way that benefits their comment and it would be immediately apparent.  The only way to get the original message is to go to that person&#8217;s profile and find it, which is way more work than just including the link to the tweet.</p>
<p>In the second case, your commentary is not very valuable.  Your users might know how you stand on the subject, but that&#8217;s about the best you can do.  There&#8217;s very little being added to the discussion.</p>
<p>This is why I like the <a href="http://www.brakeronenine.com/2009/12/21/what-to-do-with-the-old-rt/" target="_blank">solution</a> I provided.  It gives you plenty of space for commentary, while making it pretty simple to get to the pure, unaltered, original content. </p>
]]></content:encoded>
			<wfw:commentRss>http://chrisbrakebill.com/2009/12/22/more-on-why-old-retweet-sucks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What to do with the old retweet</title>
		<link>http://chrisbrakebill.com/2009/12/21/what-to-do-with-the-old-rt/</link>
		<comments>http://chrisbrakebill.com/2009/12/21/what-to-do-with-the-old-rt/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 22:49:24 +0000</pubDate>
		<dc:creator>Chris Brakebill</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[bit.ly]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[retweet]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.brakeronenine.com/?p=460</guid>
		<description><![CDATA[There&#8217;s been a ton of backlash with Twitter&#8217;s new retweet functionality.  Most of the complaint is directed toward the fact that, when you use the new retweet, you can&#8217;t comment on what you&#8217;re sharing.  There are also complaints that seeing a tweet in your timeline from someone you aren&#8217;t following is confusing.  And some users]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been a ton of backlash with Twitter&#8217;s new retweet functionality.  Most of the complaint is directed toward the fact that, when you use the new retweet, you can&#8217;t comment on what you&#8217;re sharing.  There are also complaints that seeing a tweet in your timeline from someone you aren&#8217;t following is confusing.  And some users don&#8217;t like that they no longer have the metric of looking at their mentions and seeing how many times a tweet was retweeted (something I think will be resolved before long by Twitter).</p>
<p>Conversely, it&#8217;s clear that the new retweet has a lot of value for Twitter.  It allows them to really see how much a specific tweet was shared and has the potential to give them a way to rank tweets by their value.  There&#8217;s still a long way to go in making it happen, but, in my opinion, it&#8217;s really hard to argue that the new retweet isn&#8217;t good for Twitter and for users.</p>
<p>However there is the <strong>important</strong> issue of commentary.  Being able to comment on something you&#8217;re sharing can often be crucial.  But it&#8217;s not a simple problem to solve.  If you just add the commentary to the new retweets you could get a long unmanageable stream of comments in addition to every tweet, completely defeating the biggest value Twitter brings: simplicity.</p>
<p>So what should Twitter do?  No surprise, I have a suggestion.  First I think they should acquire some short Twitter-esque domain (like http://tw.tr or something along those lines) and make that, through a partnership with bit.ly, the official domain for links to tweets.  Then add some sort of functionality, keeping it simple I would just call it comment.</p>
<p>When a user clicked the comment button on the web, the short link to that tweet would be pasted in their box giving them plenty of room for commentary.  For third party applications, Twitter could work some magic to make it really easy to make API calls via that link so that apps could show the tweet just the way the show any other individual tweet.</p>
<p>They would then have analytics they could use to assign value to a tweet as well as the commentary that makes Twitter great.  This would also make viewing an individual tweet more interesting.  When you go to the web page for that tweet, below it you could see all of the users who have commented on it (possibly even ranked by value due to the new retweet strategy).</p>
<p>I might try to make a few mockups of the idea.  I&#8217;d love to know what you think of this strategy for improving the functionality of retweets.  Like it? Have ideas to make it better?? Thank it&#8217;s complete horse crap? Let me know. </p>
]]></content:encoded>
			<wfw:commentRss>http://chrisbrakebill.com/2009/12/21/what-to-do-with-the-old-rt/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.510 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-07-31 05:39:15 -->
