<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Semantic urls, not domain: ThnLnk.com</title>
	<link>http://www.makeyougohmm.com/20060226/2991/</link>
	<description>Technology, music, video, art, news, reviews and muse on the web</description>
	<pubDate>Thu, 08 Jan 2009 22:15:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Sterling Camden</title>
		<link>http://www.makeyougohmm.com/20060226/2991/#comment-54099</link>
		<author>Sterling Camden</author>
		<pubDate>Mon, 27 Feb 2006 18:47:39 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060226/2991/#comment-54099</guid>
		<description>The realm of making domain names easier for users to manage is definitely fertile ground for further development.  I've always thought that the whole "http://www" thing is far too much technical information for the average web surfer, not to mention the rest of a heavily crufted URL.  However, I think that maybe tags and search engines will evolve to cover this ground by covering the URL's entirely.  Browsers and web content management tools could evolve to copy links without the user ever having to see the URL.  URL's could become as esoteric as IP addresses are today.  On the other hand, it's always nice to be able to publish a direct link on TV or in print -- that calls for some type of URL equivalent.  On the third hand, though, one day TV will have direct links and print may be no more!</description>
		<content:encoded><![CDATA[<p>The realm of making domain names easier for users to manage is definitely fertile ground for further development.  I&#8217;ve always thought that the whole &#8220;http://www&#8221; thing is far too much technical information for the average web surfer, not to mention the rest of a heavily crufted URL.  However, I think that maybe tags and search engines will evolve to cover this ground by covering the URL&#8217;s entirely.  Browsers and web content management tools could evolve to copy links without the user ever having to see the URL.  URL&#8217;s could become as esoteric as IP addresses are today.  On the other hand, it&#8217;s always nice to be able to publish a direct link on TV or in print &#8212; that calls for some type of URL equivalent.  On the third hand, though, one day TV will have direct links and print may be no more!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul</title>
		<link>http://www.makeyougohmm.com/20060226/2991/#comment-54088</link>
		<author>paul</author>
		<pubDate>Mon, 27 Feb 2006 06:53:34 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060226/2991/#comment-54088</guid>
		<description>I agree that the domain name can be a bit confusing, but sometimes "vision" (of thin links!) poorly preempts implementation (semantic URLs aren't always short!). I think, though, that there is a real subtle difference between author-generated or community-generated tags and third-party-oriented tags, i.e., telling "me" how content should be defined, and readers telling other readers how content should be defined. 

And I agree with you that non-cruft-laden URLs are becoming more common which is definitely a Good Thing. 

But thanks for running across my humble idea and taking the time to write about it!</description>
		<content:encoded><![CDATA[<p>I agree that the domain name can be a bit confusing, but sometimes &#8220;vision&#8221; (of thin links!) poorly preempts implementation (semantic URLs aren&#8217;t always short!). I think, though, that there is a real subtle difference between author-generated or community-generated tags and third-party-oriented tags, i.e., telling &#8220;me&#8221; how content should be defined, and readers telling other readers how content should be defined. </p>
<p>And I agree with you that non-cruft-laden URLs are becoming more common which is definitely a Good Thing. </p>
<p>But thanks for running across my humble idea and taking the time to write about it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TDavid</title>
		<link>http://www.makeyougohmm.com/20060226/2991/#comment-54086</link>
		<author>TDavid</author>
		<pubDate>Mon, 27 Feb 2006 04:48:54 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060226/2991/#comment-54086</guid>
		<description>Thanks for sharing, Andrew. I'm thinking one could also spider the page content for contextual keywords and automatically assign. I have had http://tdurl.com/ for quite some time as well, but it's just a URL shortening service, not keyword stuff. Some of these generated URLs sort of escape the whole point of shortening them.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing, Andrew. I&#8217;m thinking one could also spider the page content for contextual keywords and automatically assign. I have had <a href="http://tdurl.com/">http://tdurl.com/</a> for quite some time as well, but it&#8217;s just a URL shortening service, not keyword stuff. Some of these generated URLs sort of escape the whole point of shortening them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Ferguson</title>
		<link>http://www.makeyougohmm.com/20060226/2991/#comment-54085</link>
		<author>Andrew Ferguson</author>
		<pubDate>Mon, 27 Feb 2006 04:25:02 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060226/2991/#comment-54085</guid>
		<description>I created a similar URL shortening service(Better URL, http://burl.fergcorp.com/) a few months back as a proof-of-concept for a Lifehacker article I read (http://burl.fergcorp.com/lifehacker/6f627). For the most part BURL and ThnLnk do the same thing, except BURL doesn't let you add a title.</description>
		<content:encoded><![CDATA[<p>I created a similar URL shortening service(Better URL, <a href="http://burl.fergcorp.com/">http://burl.fergcorp.com/</a>) a few months back as a proof-of-concept for a Lifehacker article I read (http://burl.fergcorp.com/lifehacker/6f627). For the most part BURL and ThnLnk do the same thing, except BURL doesn&#8217;t let you add a title.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
