<?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"
	>
<channel>
	<title>Comments on: Twitter Adopts TinyURL</title>
	<atom:link href="http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/</link>
	<description>The Social Times covers news, analysis and insight pertaining to the social web.  Learn how to brand yourself and your company via the social web.</description>
	<pubDate>Thu, 04 Dec 2008 22:53:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Jesse Stay</title>
		<link>http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-304</link>
		<dc:creator>Jesse Stay</dc:creator>
		<pubDate>Wed, 16 Jan 2008 18:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-304</guid>
		<description>The TinyURL integration has been around for at least several months now.  It only shortens urls above a certain character limit, but my urls have been shortened by Twitter for quite awhile now.  Also, if you use Snitter, there's a feature in it that will use snurl.com, an even shorter url, to shorten your links.</description>
		<content:encoded><![CDATA[<p>The TinyURL integration has been around for at least several months now.  It only shortens urls above a certain character limit, but my urls have been shortened by Twitter for quite awhile now.  Also, if you use Snitter, there&#8217;s a feature in it that will use snurl.com, an even shorter url, to shorten your links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Stay</title>
		<link>http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-5186</link>
		<dc:creator>Jesse Stay</dc:creator>
		<pubDate>Wed, 16 Jan 2008 17:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-5186</guid>
		<description>The TinyURL integration has been around for at least several months now.  It only shortens urls above a certain character limit, but my urls have been shortened by Twitter for quite awhile now.  Also, if you use Snitter, there&#39;s a feature in it that will use &lt;a href="http://snurl.com"&gt;snurl.com&lt;/a&gt;, an even shorter url, to shorten your links.</description>
		<content:encoded><![CDATA[<p>The TinyURL integration has been around for at least several months now.  It only shortens urls above a certain character limit, but my urls have been shortened by Twitter for quite awhile now.  Also, if you use Snitter, there&#39;s a feature in it that will use <a href="http://snurl.com">snurl.com</a>, an even shorter url, to shorten your links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Lester</title>
		<link>http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-302</link>
		<dc:creator>Dan Lester</dc:creator>
		<pubDate>Wed, 16 Jan 2008 15:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-302</guid>
		<description>I've read a couple of blog posts over the last few days indicating that Twitter is using TinyURL's API - and discussing whether Twitter should just make their own URL-shortener rather than relying on an outside service.

But I don't see why they need a URL-shortener at all (one that acts as a forwarder, anyway). Why can't the API just accept links directly without it counting towards the 140-character limit? Or they can charge us 20 characters per link if they insist; and display URLs as "http://www.socialtimes.com/2008..." or just as hyperlinks around words if possible.

I 'get' the 140-char limit, but having us worry about how to enter URLs, and whether or not the forwarding will work - not to mention our recipients having no idea where the link is going... Well, I think the whole thing is an unecessary limitation!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve read a couple of blog posts over the last few days indicating that Twitter is using TinyURL&#8217;s API - and discussing whether Twitter should just make their own URL-shortener rather than relying on an outside service.</p>
<p>But I don&#8217;t see why they need a URL-shortener at all (one that acts as a forwarder, anyway). Why can&#8217;t the API just accept links directly without it counting towards the 140-character limit? Or they can charge us 20 characters per link if they insist; and display URLs as &#8220;http://www.socialtimes.com/2008&#8230;&#8221; or just as hyperlinks around words if possible.</p>
<p>I &#8216;get&#8217; the 140-char limit, but having us worry about how to enter URLs, and whether or not the forwarding will work - not to mention our recipients having no idea where the link is going&#8230; Well, I think the whole thing is an unecessary limitation!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Lester</title>
		<link>http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-5185</link>
		<dc:creator>Dan Lester</dc:creator>
		<pubDate>Wed, 16 Jan 2008 14:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialtimes.com/2008/01/twitter-adopts-tinyurl/#comment-5185</guid>
		<description>I&#39;ve read a couple of blog posts over the last few days indicating that Twitter is using TinyURL&#39;s API - and discussing whether Twitter should just make their own URL-shortener rather than relying on an outside service.&lt;br&gt;&lt;br&gt;But I don&#39;t see why they need a URL-shortener at all (one that acts as a forwarder, anyway). Why can&#39;t the API just accept links directly without it counting towards the 140-character limit? Or they can charge us 20 characters per link if they insist; and display URLs as "http://www.socialtimes.com/2008..." or just as hyperlinks around words if possible.&lt;br&gt;&lt;br&gt;I &#39;get&#39; the 140-char limit, but having us worry about how to enter URLs, and whether or not the forwarding will work - not to mention our recipients having no idea where the link is going... Well, I think the whole thing is an unecessary limitation!</description>
		<content:encoded><![CDATA[<p>I&#39;ve read a couple of blog posts over the last few days indicating that Twitter is using TinyURL&#39;s API - and discussing whether Twitter should just make their own URL-shortener rather than relying on an outside service.</p>
<p>But I don&#39;t see why they need a URL-shortener at all (one that acts as a forwarder, anyway). Why can&#39;t the API just accept links directly without it counting towards the 140-character limit? Or they can charge us 20 characters per link if they insist; and display URLs as &#8220;http://www.socialtimes.com/2008&#8230;&#8221; or just as hyperlinks around words if possible.</p>
<p>I &#39;get&#39; the 140-char limit, but having us worry about how to enter URLs, and whether or not the forwarding will work - not to mention our recipients having no idea where the link is going&#8230; Well, I think the whole thing is an unecessary limitation!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
