<?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: Twitterloo! How to send Twitter on a hasty RT.</title>
	<atom:link href="http://www.begtodiffer.com/2009/11/twitterloo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.begtodiffer.com/2009/11/twitterloo/</link>
	<description>Branding for humans</description>
	<lastBuildDate>Sat, 20 Mar 2010 14:14:24 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: RT vs. Retweet - SxDSalon: A group blog on social interaction design</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30305</link>
		<dc:creator>RT vs. Retweet - SxDSalon: A group blog on social interaction design</dc:creator>
		<pubDate>Fri, 04 Dec 2009 06:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30305</guid>
		<description>[...] Twitterloo! How to send Twitter on a hasty RT. (Beg to Differ) [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitterloo! How to send Twitter on a hasty RT. (Beg to Differ) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Van Staalduinen</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30090</link>
		<dc:creator>Dennis Van Staalduinen</dc:creator>
		<pubDate>Wed, 18 Nov 2009 02:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30090</guid>
		<description>No argument that a) the new DUM-RTs are a nifty new feature or b) that they shouldn&#039;t have been called RT. I think if they had simply added the new feature as &quot;Like&quot; or &quot;Agree&quot;, we would all be talking about how brilliant they are and how much better the new thang is than the FriendFeed or Facebook equivalents. 

But they didn&#039;t. And really, that&#039;s the whole point for me as a branding / naming / customer experience advocate: the name matters. 

They named and positioned the new feature as a replacement for RT. It is meant to become the one and only RT. Yes of course I understand that we can go on using the old one, and I will, because I have never RTed without commentary. But now the concept of &quot;RT&quot; is being stretched in two directions.

As for &quot;it can&#039;t be modified&quot; being an advantage, that&#039;s a philosophical choice on the part of Twitter - one that I strongly disagree with. The Twitter I know / expect /promote is the realm of OPEN SOURCE ideas - where there is really no such thing as content &quot;ownership&quot;. So if I Tweet it, I also accept the possibility of alterations and even abuse, but I also know that my friends are out there to watch my back. 

I actually find this obsession with attribution very quaint (and therefore will damn it with quaint praise).</description>
		<content:encoded><![CDATA[<p>No argument that a) the new DUM-RTs are a nifty new feature or b) that they shouldn&#8217;t have been called RT. I think if they had simply added the new feature as &#8220;Like&#8221; or &#8220;Agree&#8221;, we would all be talking about how brilliant they are and how much better the new thang is than the FriendFeed or Facebook equivalents. </p>
<p>But they didn&#8217;t. And really, that&#8217;s the whole point for me as a branding / naming / customer experience advocate: the name matters. </p>
<p>They named and positioned the new feature as a replacement for RT. It is meant to become the one and only RT. Yes of course I understand that we can go on using the old one, and I will, because I have never RTed without commentary. But now the concept of &#8220;RT&#8221; is being stretched in two directions.</p>
<p>As for &#8220;it can&#8217;t be modified&#8221; being an advantage, that&#8217;s a philosophical choice on the part of Twitter &#8211; one that I strongly disagree with. The Twitter I know / expect /promote is the realm of OPEN SOURCE ideas &#8211; where there is really no such thing as content &#8220;ownership&#8221;. So if I Tweet it, I also accept the possibility of alterations and even abuse, but I also know that my friends are out there to watch my back. </p>
<p>I actually find this obsession with attribution very quaint (and therefore will damn it with quaint praise).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcwbr</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30088</link>
		<dc:creator>mcwbr</dc:creator>
		<pubDate>Tue, 17 Nov 2009 22:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30088</guid>
		<description>Twitter&#039;s new RT—which they probably should not have called &quot;retweet&quot;—is superior to good old RT in several ways. 

#1 - It can&#039;t be modified. Yes, that&#039;s a feature. Because old RTs can be modified, comments can be added, which is good. But the meaning of the original can also be changed, accidentally or maliciously, which is bad. When you look at a TitterRT, you know you are seeing the original tweet. 

#2 - It can&#039;t be modified. Often, the only reason to change an original is to shorten it. How often have you spent 10 minutes editing an RT just to make it fit? And how often have you NOT been RTd becase it was too much hassle?  Twitter&#039;s RT is a link to the original, so there&#039;s never any need to shorten. 

#3 - Look at your web sidebar. Observe the &quot;Retweet&quot; link just below &quot;Favorites.&quot; Click it. Ooh and Ahh. 

#4 - A TwitterRT also creates an old fashioned RT on the public timeline. This copy may be truncated. But it is searchable. You can see both TwitterRTs and Good Ole RTs of your (or anyone&#039;s) tweets with a search on &quot;@_____&quot;

#5 - When you want to append a comment, The old fashioned RT is still available, and will show up the old fashioned way.</description>
		<content:encoded><![CDATA[<p>Twitter&#8217;s new RT—which they probably should not have called &#8220;retweet&#8221;—is superior to good old RT in several ways. </p>
<p>#1 &#8211; It can&#8217;t be modified. Yes, that&#8217;s a feature. Because old RTs can be modified, comments can be added, which is good. But the meaning of the original can also be changed, accidentally or maliciously, which is bad. When you look at a TitterRT, you know you are seeing the original tweet. </p>
<p>#2 &#8211; It can&#8217;t be modified. Often, the only reason to change an original is to shorten it. How often have you spent 10 minutes editing an RT just to make it fit? And how often have you NOT been RTd becase it was too much hassle?  Twitter&#8217;s RT is a link to the original, so there&#8217;s never any need to shorten. </p>
<p>#3 &#8211; Look at your web sidebar. Observe the &#8220;Retweet&#8221; link just below &#8220;Favorites.&#8221; Click it. Ooh and Ahh. </p>
<p>#4 &#8211; A TwitterRT also creates an old fashioned RT on the public timeline. This copy may be truncated. But it is searchable. You can see both TwitterRTs and Good Ole RTs of your (or anyone&#8217;s) tweets with a search on &#8220;@_____&#8221;</p>
<p>#5 &#8211; When you want to append a comment, The old fashioned RT is still available, and will show up the old fashioned way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Van Staalduinen</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30032</link>
		<dc:creator>Dennis Van Staalduinen</dc:creator>
		<pubDate>Sat, 14 Nov 2009 18:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30032</guid>
		<description>That&#039;s an excellent comparison. It really doesn&#039;t do much more than the &quot;LIKE&quot; function in FaceBook does it? That too leaves the original intact but allows you to &quot;pull&quot; it into your timeline. It&#039;s also binary: you either like it or you don&#039;t. You can&#039;t even say &quot;I don&#039;t like this&quot; any of the shades of &quot;kinda, but what about...&quot;. 

That&#039;s why RT is so revolutionary. It has room for nuance, discussion, challenge, irony, whatever.</description>
		<content:encoded><![CDATA[<p>That&#8217;s an excellent comparison. It really doesn&#8217;t do much more than the &#8220;LIKE&#8221; function in FaceBook does it? That too leaves the original intact but allows you to &#8220;pull&#8221; it into your timeline. It&#8217;s also binary: you either like it or you don&#8217;t. You can&#8217;t even say &#8220;I don&#8217;t like this&#8221; any of the shades of &#8220;kinda, but what about&#8230;&#8221;. </p>
<p>That&#8217;s why RT is so revolutionary. It has room for nuance, discussion, challenge, irony, whatever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Bourne</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30031</link>
		<dc:creator>Sarah Bourne</dc:creator>
		<pubDate>Sat, 14 Nov 2009 01:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30031</guid>
		<description>Twitter has not implemented a retweet feature, they&#039;ve implemented a &quot;Like&quot; button. Because you can&#039;t add anything to it, such as the fact that you vehemently disagree, you are limited to only using it if you agree.

So, go ahead, Twitter. Implement your new feature. But fix the button: it should just be &quot;Like!&quot;</description>
		<content:encoded><![CDATA[<p>Twitter has not implemented a retweet feature, they&#8217;ve implemented a &#8220;Like&#8221; button. Because you can&#8217;t add anything to it, such as the fact that you vehemently disagree, you are limited to only using it if you agree.</p>
<p>So, go ahead, Twitter. Implement your new feature. But fix the button: it should just be &#8220;Like!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Van Staalduinen</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30029</link>
		<dc:creator>Dennis Van Staalduinen</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30029</guid>
		<description>Total agreement. To sum up:
&gt;Streamlining &amp; cleaning up the user experience: good idea - yay Twitter.
&gt;Re-inventing the Twheel: very very dumb - boo hiss.</description>
		<content:encoded><![CDATA[<p>Total agreement. To sum up:<br />
>Streamlining &#038; cleaning up the user experience: good idea &#8211; yay Twitter.<br />
>Re-inventing the Twheel: very very dumb &#8211; boo hiss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Van Staalduinen</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30028</link>
		<dc:creator>Dennis Van Staalduinen</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:12:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30028</guid>
		<description>Andrew Mueller&#039;s post on this is excellent and I owe him a huge shout-out for nudging me toward this topic, so I&#039;ve also added his link to the post.
Thanks Andrew M (that&#039;s @andrewMueller, not @andrewMozier or @andrewMilne in this case)</description>
		<content:encoded><![CDATA[<p>Andrew Mueller&#8217;s post on this is excellent and I owe him a huge shout-out for nudging me toward this topic, so I&#8217;ve also added his link to the post.<br />
Thanks Andrew M (that&#8217;s @andrewMueller, not @andrewMozier or @andrewMilne in this case)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Van Staalduinen</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30027</link>
		<dc:creator>Dennis Van Staalduinen</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30027</guid>
		<description>I think company server cost issues are definitely part of the effort to &quot;streamline&quot; the DUM-RT (as I&#039;ve just now decided to call the new feature - as opposed to TRU-RT or SMA-RT if you prefer).

But there&#039;s also Ev&#039;s &quot;attribution&quot; play that puts a disturbing new top-down angle to all of this that will favour celebrity tweeters over the rest of us that hope to bask in their light. By a) attaching their avatar to the photo (not mine), and b)not allowing us to edit or comment, this move makes an RT more of a monologue from lofty Tweeter than a conversation between equals.</description>
		<content:encoded><![CDATA[<p>I think company server cost issues are definitely part of the effort to &#8220;streamline&#8221; the DUM-RT (as I&#8217;ve just now decided to call the new feature &#8211; as opposed to TRU-RT or SMA-RT if you prefer).</p>
<p>But there&#8217;s also Ev&#8217;s &#8220;attribution&#8221; play that puts a disturbing new top-down angle to all of this that will favour celebrity tweeters over the rest of us that hope to bask in their light. By a) attaching their avatar to the photo (not mine), and b)not allowing us to edit or comment, this move makes an RT more of a monologue from lofty Tweeter than a conversation between equals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Moizer</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30026</link>
		<dc:creator>Andrew Moizer</dc:creator>
		<pubDate>Fri, 13 Nov 2009 13:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30026</guid>
		<description>Dennis,
 well put.

I&#039;m completely for RT&#039;s having a proper link back to the original, but the current strategy has the emPHAsis on the wrong sylLABle (or something like that). The commentary is critical, and can be very effectively used (as you aptly showcase on a regular basis).

I&#039;m still frustrated (being polite here) that they all but eliminated the link back with replies when the &quot;fixed&quot; them, making it all but impossible to follow a dialogue unless you happen to already follow all participants.

The profound value of Twitter is in the conversations and it puzzles me why many of the so called improvements seem to work to stifle, fragment, and largely obfuscate them.

In attempting to understand the &quot;why&quot; behind this the best that I&#039;ve come up with is that there are a goodly number of &quot;obvious&quot; ways that things &quot;should&quot; work that depend on the type and scope of the individual users. And the key decision makers have a particular bent that&#039;s at odds with many of their users.

Either that, or as I strongly suspect is the case around replies, it&#039;s driven more as an attempt to assist with company server capacity issues that it is to deliver end user features. Again that emPHAsis thing.

cheers,
 Andrew</description>
		<content:encoded><![CDATA[<p>Dennis,<br />
 well put.</p>
<p>I&#8217;m completely for RT&#8217;s having a proper link back to the original, but the current strategy has the emPHAsis on the wrong sylLABle (or something like that). The commentary is critical, and can be very effectively used (as you aptly showcase on a regular basis).</p>
<p>I&#8217;m still frustrated (being polite here) that they all but eliminated the link back with replies when the &#8220;fixed&#8221; them, making it all but impossible to follow a dialogue unless you happen to already follow all participants.</p>
<p>The profound value of Twitter is in the conversations and it puzzles me why many of the so called improvements seem to work to stifle, fragment, and largely obfuscate them.</p>
<p>In attempting to understand the &#8220;why&#8221; behind this the best that I&#8217;ve come up with is that there are a goodly number of &#8220;obvious&#8221; ways that things &#8220;should&#8221; work that depend on the type and scope of the individual users. And the key decision makers have a particular bent that&#8217;s at odds with many of their users.</p>
<p>Either that, or as I strongly suspect is the case around replies, it&#8217;s driven more as an attempt to assist with company server capacity issues that it is to deliver end user features. Again that emPHAsis thing.</p>
<p>cheers,<br />
 Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mueller &#38; Co. &#187; Blog Archive &#187; Was the Twitter Retweet Feature Designed to Bring Value to Google and Bing Search</title>
		<link>http://www.begtodiffer.com/2009/11/twitterloo/comment-page-1/#comment-30024</link>
		<dc:creator>Mueller &#38; Co. &#187; Blog Archive &#187; Was the Twitter Retweet Feature Designed to Bring Value to Google and Bing Search</dc:creator>
		<pubDate>Fri, 13 Nov 2009 00:26:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.begtodiffer.com/?p=1536#comment-30024</guid>
		<description>[...] Twitterloo! How to send Twitter on a hasty RT Dennis van Staalduinen @DenVan [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitterloo! How to send Twitter on a hasty RT Dennis van Staalduinen @DenVan [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
