<?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: Most Used URLs Shortener on Twitter, January 2010</title>
	<atom:link href="http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/</link>
	<description>Cool things I believe the world should know about...</description>
	<lastBuildDate>Wed, 25 Aug 2010 23:44:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Want your URL Shortener? Buy a Domain and Use Bit.ly, like Techcrunch and New York Times</title>
		<link>http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/comment-page-1/#comment-82</link>
		<dc:creator>Want your URL Shortener? Buy a Domain and Use Bit.ly, like Techcrunch and New York Times</dc:creator>
		<pubDate>Tue, 02 Mar 2010 16:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alessiosignorini.com/?p=167#comment-82</guid>
		<description>[...] the diffusion of Twitter and other social sharing communities there is a lot of buzz over URLs shortening. Every major company wants to have its own URLs shortening domain: Google (goo.gl), TechCrunch [...]</description>
		<content:encoded><![CDATA[<p>[...] the diffusion of Twitter and other social sharing communities there is a lot of buzz over URLs shortening. Every major company wants to have its own URLs shortening domain: Google (goo.gl), TechCrunch [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why Twitter Clients still lack Classification, Clustering and Ranking? &#171; Tech, Research and Life</title>
		<link>http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/comment-page-1/#comment-36</link>
		<dc:creator>Why Twitter Clients still lack Classification, Clustering and Ranking? &#171; Tech, Research and Life</dc:creator>
		<pubDate>Mon, 08 Feb 2010 08:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alessiosignorini.com/?p=167#comment-36</guid>
		<description>[...] 41 Million tweets per day (39% containing link, for the majority spam) we could already take advantage of smarter Twitter [...]</description>
		<content:encoded><![CDATA[<p>[...] 41 Million tweets per day (39% containing link, for the majority spam) we could already take advantage of smarter Twitter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why Twitter Clients still lack Classification, Clustering and Ranking?</title>
		<link>http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/comment-page-1/#comment-35</link>
		<dc:creator>Why Twitter Clients still lack Classification, Clustering and Ranking?</dc:creator>
		<pubDate>Mon, 08 Feb 2010 08:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alessiosignorini.com/?p=167#comment-35</guid>
		<description>[...] 41 Million tweets per day (39% containing link, for the majority spam) we could already take advantage of smarter Twitter [...]</description>
		<content:encoded><![CDATA[<p>[...] 41 Million tweets per day (39% containing link, for the majority spam) we could already take advantage of smarter Twitter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: URLs shorteners are definitively a hot b&#8230; &#171; Tech, Research and Life</title>
		<link>http://blog.alessiosignorini.com/2010/02/most-used-urls-shortener-on-twitter/comment-page-1/#comment-24</link>
		<dc:creator>URLs shorteners are definitively a hot b&#8230; &#171; Tech, Research and Life</dc:creator>
		<pubDate>Fri, 05 Feb 2010 08:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alessiosignorini.com/?p=167#comment-24</guid>
		<description>[...] [Full post and table  at new URL] [...]</description>
		<content:encoded><![CDATA[<p>[...] [Full post and table  at new URL] [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
