<?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: Cake is great, Twitter is good, short URLs can die</title>
	<atom:link href="http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html</link>
	<description>Search User Experience</description>
	<lastBuildDate>Tue, 07 Feb 2012 06:22:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Preben Liland Madsen</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-142</link>
		<dc:creator>Preben Liland Madsen</dc:creator>
		<pubDate>Thu, 16 Apr 2009 07:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-142</guid>
		<description>Yes, I&#039;m aware of the fact that long urls of course wouldn&#039;t be displayed fully in the tweet. I think the best way to do it would be an icon. However, any &quot;hidden&quot; messages would still be seeable when hovering the text aswell as looking at the url when you see the urls doesn&#039;t take you to a existing web page.

But as you do mention, the possibillity of it becoming a problem is not necessarily a big one, but I think Twitter would need to think of all possibillites where a new feature like this one could be a problem.

Anyway, there need to be some way to stop that way of abusing from happening, maybe aswell have a limit to how long a url could be. Although that of course could be a problem aswell in some rare cases. 

I&#039;m sure this discussion will prove useful, and I hope someone will write the ideas into an e-mail which can be sent to the Twitter developers, providing our ideas for it - so it can save them time, so they don&#039;t have to think about everything if they want to make it.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;m aware of the fact that long urls of course wouldn&#8217;t be displayed fully in the tweet. I think the best way to do it would be an icon. However, any &#8220;hidden&#8221; messages would still be seeable when hovering the text aswell as looking at the url when you see the urls doesn&#8217;t take you to a existing web page.</p>
<p>But as you do mention, the possibillity of it becoming a problem is not necessarily a big one, but I think Twitter would need to think of all possibillites where a new feature like this one could be a problem.</p>
<p>Anyway, there need to be some way to stop that way of abusing from happening, maybe aswell have a limit to how long a url could be. Although that of course could be a problem aswell in some rare cases. </p>
<p>I&#8217;m sure this discussion will prove useful, and I hope someone will write the ideas into an e-mail which can be sent to the Twitter developers, providing our ideas for it &#8211; so it can save them time, so they don&#8217;t have to think about everything if they want to make it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Kjelsrud</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-141</link>
		<dc:creator>Thomas Kjelsrud</dc:creator>
		<pubDate>Thu, 16 Apr 2009 07:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-141</guid>
		<description>Thank you for your comment Preben. Although you highlight a possible problem of people &quot;abusing&quot; the URL field, I don&#039;t think this would be a major hurdle.

Long URLs can be a nuisance, but they wouldn&#039;t have to displayed in clear text, the actual URL path could be visible when you pointed at the link, similar to what browsers do. The link itself could be a small picture or maybe just text saying &quot;link&quot;.

Keep pondering on good ideas! Cheers</description>
		<content:encoded><![CDATA[<p>Thank you for your comment Preben. Although you highlight a possible problem of people &#8220;abusing&#8221; the URL field, I don&#8217;t think this would be a major hurdle.</p>
<p>Long URLs can be a nuisance, but they wouldn&#8217;t have to displayed in clear text, the actual URL path could be visible when you pointed at the link, similar to what browsers do. The link itself could be a small picture or maybe just text saying &#8220;link&#8221;.</p>
<p>Keep pondering on good ideas! Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preben Liland Madsen</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-140</link>
		<dc:creator>Preben Liland Madsen</dc:creator>
		<pubDate>Thu, 16 Apr 2009 06:16:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-140</guid>
		<description>The idea is very good, and I&#039;ve thought about it myself. But the links would still need to be counted towards the 140 character limit to avoid flooding or spamming or simply avoid people going around the 140 char limit by creating &quot;fake&quot; urls like; http://andbtwIwantedToSayThisButCouldntGetItInsideMyTweetILoveCake.com/ILoveCookiesaswell 

I think there would be necessary to create both a limit to how many urls there could be in a tweet (for example 3 urls) aswell as having all the urls (no matter how long or short they were) count as 10 chars.

It may aswell (if possible) be a smart idea for Twitter to check whether the main domain in the post actually exists or not. With &quot;main domain&quot;; I think about youtube.com, tinyurl.com, google.com and &quot;andbtwIwantedToSayThisButCouldntGetItInsideMyTweetILoveCake.com&quot;. If Twitter could check if the main domain actually were used or owned by somone it could then determine whether or not the link provided should be provided with the advantages of posting a url (all urls just take up 10 chars) to the tweet or not.</description>
		<content:encoded><![CDATA[<p>The idea is very good, and I&#8217;ve thought about it myself. But the links would still need to be counted towards the 140 character limit to avoid flooding or spamming or simply avoid people going around the 140 char limit by creating &#8220;fake&#8221; urls like; <a href="http://andbtwIwantedToSayThisButCouldntGetItInsideMyTweetILoveCake.com/ILoveCookiesaswell" rel="nofollow">http://andbtwIwantedToSayThisButCouldntGetItInsideMyTweetILoveCake.com/ILoveCookiesaswell</a> </p>
<p>I think there would be necessary to create both a limit to how many urls there could be in a tweet (for example 3 urls) aswell as having all the urls (no matter how long or short they were) count as 10 chars.</p>
<p>It may aswell (if possible) be a smart idea for Twitter to check whether the main domain in the post actually exists or not. With &#8220;main domain&#8221;; I think about youtube.com, tinyurl.com, google.com and &#8220;andbtwIwantedToSayThisButCouldntGetItInsideMyTweetILoveCake.com&#8221;. If Twitter could check if the main domain actually were used or owned by somone it could then determine whether or not the link provided should be provided with the advantages of posting a url (all urls just take up 10 chars) to the tweet or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Kjelsrud</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-72</link>
		<dc:creator>Thomas Kjelsrud</dc:creator>
		<pubDate>Fri, 20 Mar 2009 11:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-72</guid>
		<description>I&#039;m uncertain about the volume of SMS use on twitter, and especially as to how many of these cell phone users would go to the trouble of shorting an URL through another site and then paste it into a SMS. I think these people would probably be on a computer with a Twitter client anyhow. That aside, I still think people could add short URLs to the messages if they please, but the protocol could also allow for longer ULRs to be meta-data in richer Twitter clients.</description>
		<content:encoded><![CDATA[<p>I&#8217;m uncertain about the volume of SMS use on twitter, and especially as to how many of these cell phone users would go to the trouble of shorting an URL through another site and then paste it into a SMS. I think these people would probably be on a computer with a Twitter client anyhow. That aside, I still think people could add short URLs to the messages if they please, but the protocol could also allow for longer ULRs to be meta-data in richer Twitter clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Rosenthal</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-70</link>
		<dc:creator>Ben Rosenthal</dc:creator>
		<pubDate>Fri, 13 Mar 2009 17:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-70</guid>
		<description>If URLs are separated out from the 140 characters of the tweet itself, how will people post them from a cell phone?  The 140 character limit is based on the limitations of SMS, isn&#039;t it?  Should a second text be sent containing a URL that is then &quot;reattached&quot; to the original tweet?

I don&#039;t know how popular it is to tweet by SMS, but that is still part of the Twitter userbase.</description>
		<content:encoded><![CDATA[<p>If URLs are separated out from the 140 characters of the tweet itself, how will people post them from a cell phone?  The 140 character limit is based on the limitations of SMS, isn&#8217;t it?  Should a second text be sent containing a URL that is then &#8220;reattached&#8221; to the original tweet?</p>
<p>I don&#8217;t know how popular it is to tweet by SMS, but that is still part of the Twitter userbase.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Kjelsrud</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-51</link>
		<dc:creator>Thomas Kjelsrud</dc:creator>
		<pubDate>Tue, 03 Mar 2009 14:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-51</guid>
		<description>Both good suggestions, a combination with anchor text would indeed improve link quality, but might be difficult for some users to grasp. I guess it depends on how the clients implement this bit, which would also explain why this is an issue in the first place - Twitter as a service might not have focused on extending it for &quot;richer&quot; client functionality.</description>
		<content:encoded><![CDATA[<p>Both good suggestions, a combination with anchor text would indeed improve link quality, but might be difficult for some users to grasp. I guess it depends on how the clients implement this bit, which would also explain why this is an issue in the first place &#8211; Twitter as a service might not have focused on extending it for &#8220;richer&#8221; client functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo Ring Giske</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-45</link>
		<dc:creator>Jo Ring Giske</dc:creator>
		<pubDate>Mon, 02 Mar 2009 12:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-45</guid>
		<description>Another advantage is that you could have an anchortext as well. This would make it easy to make a meaningful Tweet with many links. Today it just looks garbled.</description>
		<content:encoded><![CDATA[<p>Another advantage is that you could have an anchortext as well. This would make it easy to make a meaningful Tweet with many links. Today it just looks garbled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vegard Sandvold</title>
		<link>http://www.thingsontop.com/cake-great-twitter-good-short-urls-die-490.html/comment-page-1/#comment-44</link>
		<dc:creator>Vegard Sandvold</dc:creator>
		<pubDate>Mon, 02 Mar 2009 12:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thingsontop.com/?p=490#comment-44</guid>
		<description>I like the idea of counting URLs outside the 140 character limit on Twitter messages. Short URLs are neither user-friendly nor SEO-friendly. It&#039;s a need born out of technological limitations (and in this case artificial limitations). And they make us very vulnerable to phishing and spam.

Like you&#039;re suggesting; let&#039;s attach URLs as metadata on each tweet, freeing up some space for more meaningful words, without obfuscating the original, possibly keyword-rich URLs.</description>
		<content:encoded><![CDATA[<p>I like the idea of counting URLs outside the 140 character limit on Twitter messages. Short URLs are neither user-friendly nor SEO-friendly. It&#8217;s a need born out of technological limitations (and in this case artificial limitations). And they make us very vulnerable to phishing and spam.</p>
<p>Like you&#8217;re suggesting; let&#8217;s attach URLs as metadata on each tweet, freeing up some space for more meaningful words, without obfuscating the original, possibly keyword-rich URLs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

