<?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: New Twitter RT Link: Be Cautious</title>
	<atom:link href="http://flipthemedia.com/index.php/2009/11/new-twitter-rt-link-be-cautious/feed/" rel="self" type="application/rss+xml" />
	<link>http://flipthemedia.com/index.php/2009/11/new-twitter-rt-link-be-cautious/</link>
	<description>At the crossroads of Media, Culture and Technology</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:53:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Twitter&#8217;s ReTweet Beta: An Attack on 3rd Party Tools?</title>
		<link>http://flipthemedia.com/index.php/2009/11/new-twitter-rt-link-be-cautious/comment-page-1/#comment-4111</link>
		<dc:creator>Twitter&#8217;s ReTweet Beta: An Attack on 3rd Party Tools?</dc:creator>
		<pubDate>Mon, 16 Nov 2009 20:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://flipthemedia.com/?p=3905#comment-4111</guid>
		<description>[...] Twitter also has another &#8220;method&#8221; of taking down the suckerfish (aka: 3rd party apps). &#8220;Currently, retweets that are executed via the Twitter web “retweet link” are visible to your followers who are using the web interface to read your tweets but are not visible to popular third party clients. [...] In other words, third party applications may not have had a chance to integrate the new API. [...] If most of your followers read your tweets using third party desktop clients, this “bug” could have a serious impact on your personal retweet rate in the short-term.&#8221; (Flip The Media) [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter also has another &#8220;method&#8221; of taking down the suckerfish (aka: 3rd party apps). &#8220;Currently, retweets that are executed via the Twitter web “retweet link” are visible to your followers who are using the web interface to read your tweets but are not visible to popular third party clients. [...] In other words, third party applications may not have had a chance to integrate the new API. [...] If most of your followers read your tweets using third party desktop clients, this “bug” could have a serious impact on your personal retweet rate in the short-term.&#8221; (Flip The Media) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melissa</title>
		<link>http://flipthemedia.com/index.php/2009/11/new-twitter-rt-link-be-cautious/comment-page-1/#comment-4085</link>
		<dc:creator>Melissa</dc:creator>
		<pubDate>Thu, 12 Nov 2009 02:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://flipthemedia.com/?p=3905#comment-4085</guid>
		<description>wow - thank you for the FYI - I always wondered why Twitter hadn&#039;t adopted the &quot;Retweet&quot; button a la TweetDeck etc -- and then today, voila! But I did notice the small disclaimer, although not really as clear as you make it here.

I&#039;d be interested in starting a group on improving Twitter --  what else would help us pass along or aggregate info like Hashtag or Retweet? 

What I love most about Twitter is that the users are the ones who came up with the RT and the # functions -- not the initial Twitter creators.</description>
		<content:encoded><![CDATA[<p>wow &#8211; thank you for the FYI &#8211; I always wondered why Twitter hadn&#8217;t adopted the &#8220;Retweet&#8221; button a la TweetDeck etc &#8212; and then today, voila! But I did notice the small disclaimer, although not really as clear as you make it here.</p>
<p>I&#8217;d be interested in starting a group on improving Twitter &#8212;  what else would help us pass along or aggregate info like Hashtag or Retweet? </p>
<p>What I love most about Twitter is that the users are the ones who came up with the RT and the # functions &#8212; not the initial Twitter creators.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

