<?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: Help spread the &#8220;search://&#8221; meme!</title>
	<atom:link href="http://www.rants.org/2007/04/22/help-spread-the-search-meme/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/</link>
	<description>Thoughts, musings, and rants by Karl Fogel</description>
	<pubDate>Thu, 20 Nov 2008 22:41:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-bleeding</generator>
		<item>
		<title>By: Karl Fogel</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-599</link>
		<dc:creator>Karl Fogel</dc:creator>
		<pubDate>Sun, 29 Apr 2007 19:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-599</guid>
		<description>(Responding to Jesse.)

I often recommend to people that they do a search, and I see others recommending the same.  But I hang out on open-source user support lists, where this is common.  Often there isn't just one page you want to send someone to, rather it's a matter of giving them the search terms they need and letting &lt;em&gt;them&lt;/em&gt; filter the results.

The problem with sending a Google URL is readability -- it's URI encoded, so all the spaces and quotes look funny.  Techies are comfortable with the encoded form, but normal human beings aren't.</description>
		<content:encoded><![CDATA[<p>(Responding to Jesse.)</p>
<p>I often recommend to people that they do a search, and I see others recommending the same.  But I hang out on open-source user support lists, where this is common.  Often there isn&#8217;t just one page you want to send someone to, rather it&#8217;s a matter of giving them the search terms they need and letting <em>them</em> filter the results.</p>
<p>The problem with sending a Google URL is readability &#8212; it&#8217;s URI encoded, so all the spaces and quotes look funny.  Techies are comfortable with the encoded form, but normal human beings aren&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Hogan</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-454</link>
		<dc:creator>Jesse Hogan</dc:creator>
		<pubDate>Mon, 23 Apr 2007 18:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-454</guid>
		<description>I never find myself needing to tell someone to search for something; I guess I have different computer using habits. I usually just send the link of the page I want them to look at or, if I want them to see a Google search result I would send them the Google URL (with the search query parameters of course).  If I had a friend who worked at Yahoo I would send them a Google link. Sorry to get off topic but Yahoo is dead to me given their recent behavior.</description>
		<content:encoded><![CDATA[<p>I never find myself needing to tell someone to search for something; I guess I have different computer using habits. I usually just send the link of the page I want them to look at or, if I want them to see a Google search result I would send them the Google URL (with the search query parameters of course).  If I had a friend who worked at Yahoo I would send them a Google link. Sorry to get off topic but Yahoo is dead to me given their recent behavior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Fogel</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-446</link>
		<dc:creator>Karl Fogel</dc:creator>
		<pubDate>Sun, 22 Apr 2007 23:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-446</guid>
		<description>I think I was wrong, and that you can encode double quotes -- I misread the spec.  You just can't include a double quote literally in a URI.  It differs from those characters which can be included unencoded when used for their reserved purpose, but which must be encoded when included for any other purpose.  Double quote isn't a reserved character, it's simply a prohibited character: it can't ever be present unencoded.

Thanks for probing, David.  I've corrected the text now, so your question will probably seem odd to future readers.  But &lt;em&gt;we'll&lt;/em&gt; know what you meant :-).

The reasons I prefer "search://.../" to "search:/.../" are one, that people are used to it and know how to skip over the first pair of slashes, and two, that the two slashes makes a much better visual boundary anyway (you don't need it on the trailing end because you have a space to help you out there, plus the reader has already gone into the right "parse state" for the situation by then).</description>
		<content:encoded><![CDATA[<p>I think I was wrong, and that you can encode double quotes &#8212; I misread the spec.  You just can&#8217;t include a double quote literally in a URI.  It differs from those characters which can be included unencoded when used for their reserved purpose, but which must be encoded when included for any other purpose.  Double quote isn&#8217;t a reserved character, it&#8217;s simply a prohibited character: it can&#8217;t ever be present unencoded.</p>
<p>Thanks for probing, David.  I&#8217;ve corrected the text now, so your question will probably seem odd to future readers.  But <em>we&#8217;ll</em> know what you meant :-).</p>
<p>The reasons I prefer &#8220;search://&#8230;/&#8221; to &#8220;search:/&#8230;/&#8221; are one, that people are used to it and know how to skip over the first pair of slashes, and two, that the two slashes makes a much better visual boundary anyway (you don&#8217;t need it on the trailing end because you have a space to help you out there, plus the reader has already gone into the right &#8220;parse state&#8221; for the situation by then).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Carlton</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-445</link>
		<dc:creator>David Carlton</dc:creator>
		<pubDate>Sun, 22 Apr 2007 22:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-445</guid>
		<description>Why can't I use %22 to represent double quotes?  I haven't read the entire RFC in detail, but section 2.1 makes it seem like percent encoding can be used with arbitrary binary data.

Not clear to me whether or not search:// is better than search:/ - I'd have to think about that.</description>
		<content:encoded><![CDATA[<p>Why can&#8217;t I use %22 to represent double quotes?  I haven&#8217;t read the entire RFC in detail, but section 2.1 makes it seem like percent encoding can be used with arbitrary binary data.</p>
<p>Not clear to me whether or not search:// is better than search:/ - I&#8217;d have to think about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Fogel</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-442</link>
		<dc:creator>Karl Fogel</dc:creator>
		<pubDate>Sun, 22 Apr 2007 17:05:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-442</guid>
		<description>Yeah, I've used that in the past too.  Two problems with it: one, you still have to write text saying to do a search (so you're still typing more words, and figuring out how to phrase it each time -- do I say "Google" or "your favorite search engine", etc?), and two, it's not automatically parseable as a search, because so many other things can be surrounded by square brackets too.  Thus, software support can't evolve as easily.</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;ve used that in the past too.  Two problems with it: one, you still have to write text saying to do a search (so you&#8217;re still typing more words, and figuring out how to phrase it each time &#8212; do I say &#8220;Google&#8221; or &#8220;your favorite search engine&#8221;, etc?), and two, it&#8217;s not automatically parseable as a search, because so many other things can be surrounded by square brackets too.  Thus, software support can&#8217;t evolve as easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fitz</title>
		<link>http://www.rants.org/2007/04/22/help-spread-the-search-meme/#comment-440</link>
		<dc:creator>Fitz</dc:creator>
		<pubDate>Sun, 22 Apr 2007 12:01:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.rants.org/?p=10#comment-440</guid>
		<description>I just use [] around what you should search for.  For example:

[there will also be corn served]

or 

["there will also be corn served"]</description>
		<content:encoded><![CDATA[<p>I just use [] around what you should search for.  For example:</p>
<p>[there will also be corn served]</p>
<p>or </p>
<p>["there will also be corn served"]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
