<?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>Social Media Conversation Analyst &#187; tinyurl</title>
	<atom:link href="http://www.nickarnett.net/tag/tinyurl/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nickarnett.net</link>
	<description>Social media analytics for decision-making</description>
	<lastBuildDate>Mon, 18 Apr 2011 16:05:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>What&#8217;s really wrong with URL shorteners</title>
		<link>http://www.nickarnett.net/2009/07/17/whats-really-wrong-with-url-shorteners/</link>
		<comments>http://www.nickarnett.net/2009/07/17/whats-really-wrong-with-url-shorteners/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 15:42:18 +0000</pubDate>
		<dc:creator>Nick Arnett</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bit.ly]]></category>
		<category><![CDATA[links]]></category>
		<category><![CDATA[relevance]]></category>
		<category><![CDATA[shortening]]></category>
		<category><![CDATA[tinyurl]]></category>

		<guid isPermaLink="false">http://www.nickarnett.net/2009/07/17/whats-really-wrong-with-url-shorteners/</guid>
		<description><![CDATA[Services that shorten URLs &#8211; bit.ly, tinyurl.com, etc &#8211; have been criticized for contributing to &#8220;linkrot&#8221; (they stop working if the underlying service goes away), obscuring link destinations for nefarious purposes, violating privacy by allowing increased link tracking and using network resources due to redirection.&#160; Those are valid concerns, but none compares to the information [...]]]></description>
			<content:encoded><![CDATA[<p>Services that shorten URLs &#8211; bit.ly, tinyurl.com, etc &#8211; have been criticized for contributing to &#8220;<a href="http://en.wikipedia.org/wiki/Linkrot">linkrot</a>&#8221; (they stop working if the underlying service goes away), obscuring link destinations for nefarious purposes, violating privacy by allowing increased link tracking and using network resources due to redirection.&nbsp; Those are valid concerns, but none compares to the information opportunity lost as shortened URLs become unique.</p>
<p>URLs in real-time media &#8211; blogs, microblogs, etc. &#8211; can be the foundation of near-real-time search relevance ranking.&nbsp; This is simple in principle.&nbsp; When a lot of people (or an intelligently selected set of people) suddenly start citing links to a given page or site, there is obviously something of interest there.&nbsp; That is the kind of analysis that Google&#8217;s PageRank and similar algorithms use.&nbsp; Each cite is a signifcant &#8220;vote&#8221; for the page.&nbsp; When they occur in real-time media (v. static web pages), it provides a relevance metric that Google and its competitors aren&#8217;t touching yet.&nbsp; The big search engines are not yet doing much in this domain.&nbsp; Nobody has emerged as a leader in doing it comprehensively.&nbsp; </p>
<p>In other words, as many people have pointed out, URLs in blogs, microblogs, etc., are the foundation of something like PageRank in near realtime.&nbsp; But they become increasingly useless as they are uniquely shortened.</p>
<p>It would be interesting to figure out a motivation for the URL shorteners to offer comprehensive resolution to their APIs (given a long URL, return ALL shortened versions).&nbsp; I can&#8217;t quite see why they would do that, but perhaps developers with a vision for real-time search (which probably is more correctly called monitoring rather than search) could lobby the shorteners to add that capability&#8230; or even create a shared repository as a community project that would also solve the linkrot problem.</p>
<p>One more thought&#8230; Twitter and others who do the shortened themselves have all of this data for the URLs they shorten.&nbsp; As large customers of the shortening services, they have more influence than the individual developers, so perhaps that&#8217;s where the lobbying effort should focus.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nickarnett.net/2009/07/17/whats-really-wrong-with-url-shorteners/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

