<?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: Conversational and short URLs on Rails</title>
	<atom:link href="http://thinkvitamin.com/dev/conversational-and-short-urls-on-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/</link>
	<description>The Web Practitioner&#039;s Blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:33:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Raviv</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-41867</link>
		<dc:creator>Raviv</dc:creator>
		<pubDate>Thu, 17 Mar 2011 18:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-41867</guid>
		<description>Hi Jason,

Great post.  Very useful.  One question: how did you design your links and navigation such that people could drill-down to get to an event?  As in, on a page listing all of the Chicago events, what did the link_to code look like for getting them to the Chicago events on Design?  Would it merge the parameters each time?

thanks,
Raviv</description>
		<content:encoded><![CDATA[<p>Hi Jason,</p>
<p>Great post.  Very useful.  One question: how did you design your links and navigation such that people could drill-down to get to an event?  As in, on a page listing all of the Chicago events, what did the link_to code look like for getting them to the Chicago events on Design?  Would it merge the parameters each time?</p>
<p>thanks,<br />
Raviv</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Scott Hernandez</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-40343</link>
		<dc:creator>Christopher Scott Hernandez</dc:creator>
		<pubDate>Tue, 08 Feb 2011 16:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-40343</guid>
		<description>Yeah, go with dashes...heard it a long time ago on a forum ;)</description>
		<content:encoded><![CDATA[<p>Yeah, go with dashes&#8230;heard it a long time ago on a forum ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian M.</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-20834</link>
		<dc:creator>Adrian M.</dc:creator>
		<pubDate>Tue, 25 May 2010 01:59:58 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-20834</guid>
		<description>Jason,

Interesting post.  This problem was already noticed by Tim Berners-Lee about 15 years ago with his work on &quot;Matrix URIs&quot;.  Unfortunately his ideas didn&#039;t make it to common web browsers.

That said, I&#039;ve also worked on variants of this idea.  I&#039;m wondering how do you generate these conversational URLs.

Regards</description>
		<content:encoded><![CDATA[<p>Jason,</p>
<p>Interesting post.  This problem was already noticed by Tim Berners-Lee about 15 years ago with his work on &#8220;Matrix URIs&#8221;.  Unfortunately his ideas didn&#8217;t make it to common web browsers.</p>
<p>That said, I&#8217;ve also worked on variants of this idea.  I&#8217;m wondering how do you generate these conversational URLs.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Julian</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-19131</link>
		<dc:creator>Jonathan Julian</dc:creator>
		<pubDate>Sun, 14 Mar 2010 06:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-19131</guid>
		<description>Edmund is absolutely correct. I&#039;ve written a spec that exposes the error in decode: http://gist.github.com/331808</description>
		<content:encoded><![CDATA[<p>Edmund is absolutely correct. I&#8217;ve written a spec that exposes the error in decode: <a href="http://gist.github.com/331808" rel="nofollow">http://gist.github.com/331808</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edmund Salvacion</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18864</link>
		<dc:creator>Edmund Salvacion</dc:creator>
		<pubDate>Thu, 25 Feb 2010 02:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18864</guid>
		<description>Great article.

In base58.rb file there is a bit of an error in the decode:

decoded += multi * alphabet.index(n[i,i+1])

should be:

decoded += multi * alphabet.index(n[i,1])

The former would only work up to 2 characters.</description>
		<content:encoded><![CDATA[<p>Great article.</p>
<p>In base58.rb file there is a bit of an error in the decode:</p>
<p>decoded += multi * alphabet.index(n[i,i+1])</p>
<p>should be:</p>
<p>decoded += multi * alphabet.index(n[i,1])</p>
<p>The former would only work up to 2 characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18200</link>
		<dc:creator>Gareth</dc:creator>
		<pubDate>Thu, 28 Jan 2010 17:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18200</guid>
		<description>It would require a similar amount of code in PHP, the difference here is that Ruby&#039;s block syntax allows someone *else* to write the repetitive code which loops through the array and splits it out. It means that someone reading your code has a much better chance of seeing *what* you want to do, without having to understand the implementation detail of how you are doing it.

Now I think of it, Rails provides a similar in_groups_of(x) method, which offers better handling of cases where your array doesn&#039;t split exactly into groups of x - probably worth investigating.</description>
		<content:encoded><![CDATA[<p>It would require a similar amount of code in PHP, the difference here is that Ruby&#8217;s block syntax allows someone *else* to write the repetitive code which loops through the array and splits it out. It means that someone reading your code has a much better chance of seeing *what* you want to do, without having to understand the implementation detail of how you are doing it.</p>
<p>Now I think of it, Rails provides a similar in_groups_of(x) method, which offers better handling of cases where your array doesn&#8217;t split exactly into groups of x &#8211; probably worth investigating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Lynes</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18199</link>
		<dc:creator>Jason Lynes</dc:creator>
		<pubDate>Thu, 28 Jan 2010 17:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18199</guid>
		<description>life is good when that for syntax is nasty.  :)  how much code would that require in php?

but this is tons cleaner, and i haven&#039;t seen that technique.  i&#039;ll throw this in now...</description>
		<content:encoded><![CDATA[<p>life is good when that for syntax is nasty.  :)  how much code would that require in php?</p>
<p>but this is tons cleaner, and i haven&#8217;t seen that technique.  i&#8217;ll throw this in now&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18198</link>
		<dc:creator>Gareth</dc:creator>
		<pubDate>Thu, 28 Jan 2010 17:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18198</guid>
		<description>Instead of that nasty looking for..in syntax, you can use the much more Ruby-ish each_slice, which will yield you successive pairs from an Enumerable:

&gt;&gt; (1..10).each_slice(2) { &#124;a,b&#124; puts [a,b].inspect }
[1, 2]
[3, 4]
[5, 6]
[7, 8]
[9, 10]</description>
		<content:encoded><![CDATA[<p>Instead of that nasty looking for..in syntax, you can use the much more Ruby-ish each_slice, which will yield you successive pairs from an Enumerable:</p>
<p>&gt;&gt; (1..10).each_slice(2) { |a,b| puts [a,b].inspect }<br />
[1, 2]<br />
[3, 4]<br />
[5, 6]<br />
[7, 8]<br />
[9, 10]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Merrick Christensen</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18197</link>
		<dc:creator>Merrick Christensen</dc:creator>
		<pubDate>Thu, 28 Jan 2010 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18197</guid>
		<description>This is gold! I love these URL&#039;s thanks for the post. It&#039;s good to see some cool developers out of Salt Lake too. :)</description>
		<content:encoded><![CDATA[<p>This is gold! I love these URL&#8217;s thanks for the post. It&#8217;s good to see some cool developers out of Salt Lake too. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Lynes</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18196</link>
		<dc:creator>Jason Lynes</dc:creator>
		<pubDate>Thu, 28 Jan 2010 16:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18196</guid>
		<description>Thanks, Russel, that&#039;s looking promising..</description>
		<content:encoded><![CDATA[<p>Thanks, Russel, that&#8217;s looking promising..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert van Hoesel</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18195</link>
		<dc:creator>Robert van Hoesel</dc:creator>
		<pubDate>Thu, 28 Jan 2010 16:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18195</guid>
		<description>Next to these urls not being twitter friendly, google does not like them either.
When Google has to dig in 4 or more subdirectories it thinks the page is less important or less worthy.</description>
		<content:encoded><![CDATA[<p>Next to these urls not being twitter friendly, google does not like them either.<br />
When Google has to dig in 4 or more subdirectories it thinks the page is less important or less worthy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell Allen</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18192</link>
		<dc:creator>Russell Allen</dc:creator>
		<pubDate>Thu, 28 Jan 2010 16:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18192</guid>
		<description>This sounds like a really cool idea - on the SEO implications, it might be worth taking a look at the new canonical link meta tag, which allows multiple pages to pool their SEO ranking against a single URL.

http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html</description>
		<content:encoded><![CDATA[<p>This sounds like a really cool idea &#8211; on the SEO implications, it might be worth taking a look at the new canonical link meta tag, which allows multiple pages to pool their SEO ranking against a single URL.</p>
<p><a href="http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html" rel="nofollow">http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Lynes</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18188</link>
		<dc:creator>Jason Lynes</dc:creator>
		<pubDate>Thu, 28 Jan 2010 15:37:09 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18188</guid>
		<description>Henrik, thanks for that link!  I didn&#039;t know about that.  I&#039;ll have to grab that plugin.

And great point, Paul.  Yes, they go to the same page.  I&#039;m no SEO expert, so I&#039;m not sure about the search implications of that.  A friend also mentioned that my underscores weren&#039;t as Google-friendly as dashes.  Any SEO gurus care to chime in?</description>
		<content:encoded><![CDATA[<p>Henrik, thanks for that link!  I didn&#8217;t know about that.  I&#8217;ll have to grab that plugin.</p>
<p>And great point, Paul.  Yes, they go to the same page.  I&#8217;m no SEO expert, so I&#8217;m not sure about the search implications of that.  A friend also mentioned that my underscores weren&#8217;t as Google-friendly as dashes.  Any SEO gurus care to chime in?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Campbell</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18187</link>
		<dc:creator>Paul Campbell</dc:creator>
		<pubDate>Thu, 28 Jan 2010 15:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18187</guid>
		<description>This is absolutely brilliant.  Definitely the way forward. One question (forgive me for not being a ruby programmer...)

Does this mean you can have these two URLs pointing to the same page:

conferences/on/programming/in/new_york

conferences/in/new_york/on/programming

How do we address search engines crawling, what I guess it would see as, duplicate content?</description>
		<content:encoded><![CDATA[<p>This is absolutely brilliant.  Definitely the way forward. One question (forgive me for not being a ruby programmer&#8230;)</p>
<p>Does this mean you can have these two URLs pointing to the same page:</p>
<p>conferences/on/programming/in/new_york</p>
<p>conferences/in/new_york/on/programming</p>
<p>How do we address search engines crawling, what I guess it would see as, duplicate content?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik N</title>
		<link>http://thinkvitamin.com/code/conversational-and-short-urls-on-rails/#comment-18183</link>
		<dc:creator>Henrik N</dc:creator>
		<pubDate>Thu, 28 Jan 2010 13:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://carsonified.com/?p=4289#comment-18183</guid>
		<description>Rather than add a /h/ prefix, you could use a plugin like http://github.com/veilleperso/request_routing and add :conditions =&gt; { :domain =&gt; MY_SHORT_DOMAIN } to those routes. Saves a few characters.</description>
		<content:encoded><![CDATA[<p>Rather than add a /h/ prefix, you could use a plugin like <a href="http://github.com/veilleperso/request_routing" rel="nofollow">http://github.com/veilleperso/request_routing</a> and add :conditions =&gt; { :domain =&gt; MY_SHORT_DOMAIN } to those routes. Saves a few characters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.090 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-11 21:59:30 -->

