<?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: Searching Twitter Better</title>
	<atom:link href="http://fstutzman.com/2008/06/06/searching-twitter-better/feed/" rel="self" type="application/rss+xml" />
	<link>http://fstutzman.com/2008/06/06/searching-twitter-better/</link>
	<description>Thoughts about information, social networks, and privacy</description>
	<lastBuildDate>Fri, 06 Jan 2012 21:54:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Unit Structures &#8211; BackTweets</title>
		<link>http://fstutzman.com/2008/06/06/searching-twitter-better/comment-page-1/#comment-10656</link>
		<dc:creator>Unit Structures &#8211; BackTweets</dc:creator>
		<pubDate>Sun, 08 Mar 2009 05:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1/~fred/projects/blog/?p=606#comment-10656</guid>
		<description>[...] Something I asked for a long time ago.  Don&#8217;t know why Twitter search still doesn&#8217;t do this, perhaps now they will.  Great execution, smart defaults, instantly indispensable for anyone monitoring Twitter.  Excellent. [...]</description>
		<content:encoded><![CDATA[<p>[...] Something I asked for a long time ago.  Don&#8217;t know why Twitter search still doesn&#8217;t do this, perhaps now they will.  Great execution, smart defaults, instantly indispensable for anyone monitoring Twitter.  Excellent. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: factoryjoe</title>
		<link>http://fstutzman.com/2008/06/06/searching-twitter-better/comment-page-1/#comment-1272</link>
		<dc:creator>factoryjoe</dc:creator>
		<pubDate>Sat, 07 Jun 2008 21:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1/~fred/projects/blog/?p=606#comment-1272</guid>
		<description>Seen TwitLinks (http://www.twitlinks.com/)? Seems like it&#039;s doing something like what you&#039;re talking about...</description>
		<content:encoded><![CDATA[<p>Seen TwitLinks (<a href="http://www.twitlinks.com/" rel="nofollow">http://www.twitlinks.com/</a>)? Seems like it&#8217;s doing something like what you&#8217;re talking about&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fred</title>
		<link>http://fstutzman.com/2008/06/06/searching-twitter-better/comment-page-1/#comment-1270</link>
		<dc:creator>fred</dc:creator>
		<pubDate>Fri, 06 Jun 2008 16:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1/~fred/projects/blog/?p=606#comment-1270</guid>
		<description>@bertil -&lt;br/&gt;&lt;br/&gt;I think that&#039;s sort of what I was thinking.  The problem with it is exhaustiveness.  If you want to do a post-hoc search you need to hit 150+ url services and 150+ searches on tweetscan.  So much easier for them to build a fulltext index.  TinyUrl, which is the most common in the corpus, has an api...it could be batched.  The rest problably send over 300&#039;s so you could build the remainder of the corpus with HEAD&#039;s.</description>
		<content:encoded><![CDATA[<p>@bertil -</p>
<p>I think that&#8217;s sort of what I was thinking.  The problem with it is exhaustiveness.  If you want to do a post-hoc search you need to hit 150+ url services and 150+ searches on tweetscan.  So much easier for them to build a fulltext index.  TinyUrl, which is the most common in the corpus, has an api&#8230;it could be batched.  The rest problably send over 300&#8242;s so you could build the remainder of the corpus with HEAD&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bertil Hatt</title>
		<link>http://fstutzman.com/2008/06/06/searching-twitter-better/comment-page-1/#comment-1269</link>
		<dc:creator>Bertil Hatt</dc:creator>
		<pubDate>Fri, 06 Jun 2008 16:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1/~fred/projects/blog/?p=606#comment-1269</guid>
		<description>Not sure this matches your needs, but this Yahoo Pipe sounds like it has at least the bricks you need:&lt;br/&gt;&lt;br/&gt;&quot;Given a Tiny URL, find the original link URL, and then look up on Google web search and Google blogsearch what sites link to the URL.&quot;&lt;br/&gt;&lt;br/&gt;http://pipes.yahoo.com/pipes/pipe.info?_id=caa47cb2b123ca36cb4f21256a4eb033&lt;br/&gt;&lt;br/&gt;What I assume you can do, is use a hack of this one, in a embedded loop (Y! demands you have two &#039;pipes&#039; whenever you want to loop anything.)</description>
		<content:encoded><![CDATA[<p>Not sure this matches your needs, but this Yahoo Pipe sounds like it has at least the bricks you need:</p>
<p>&#8220;Given a Tiny URL, find the original link URL, and then look up on Google web search and Google blogsearch what sites link to the URL.&#8221;</p>
<p><a href="http://pipes.yahoo.com/pipes/pipe.info?_id=caa47cb2b123ca36cb4f21256a4eb033" rel="nofollow">http://pipes.yahoo.com/pipes/pipe.info?_id=caa47cb2b123ca36cb4f21256a4eb033</a></p>
<p>What I assume you can do, is use a hack of this one, in a embedded loop (Y! demands you have two &#8216;pipes&#8217; whenever you want to loop anything.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://fstutzman.com/2008/06/06/searching-twitter-better/comment-page-1/#comment-1268</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Fri, 06 Jun 2008 14:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1/~fred/projects/blog/?p=606#comment-1268</guid>
		<description>I&#039;ve thought about this, too.  Someone needs to dive into all those TINYURLs, URLTEAs and such and pull out the list of where they&#039;re linking to. &lt;br/&gt;&lt;br/&gt;Seems like it would be easy to do, too...   I&#039;d be curious where all the twit links go.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve thought about this, too.  Someone needs to dive into all those TINYURLs, URLTEAs and such and pull out the list of where they&#8217;re linking to. </p>
<p>Seems like it would be easy to do, too&#8230;   I&#8217;d be curious where all the twit links go.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

