<?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: A simple perl script to interrogate the Technorati API</title>
	<atom:link href="http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/</link>
	<description>a blog by mat morrison</description>
	<lastBuildDate>Thu, 05 Aug 2010 09:23:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Malise</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-4261</link>
		<dc:creator>Malise</dc:creator>
		<pubDate>Sun, 01 Mar 2009 22:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-4261</guid>
		<description>i just wanted to say that I love this site</description>
		<content:encoded><![CDATA[<p>i just wanted to say that I love this site</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Technorati Authority Yahoo! Pipe &#124; Mediaczar</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-547</link>
		<dc:creator>The Technorati Authority Yahoo! Pipe &#124; Mediaczar</dc:creator>
		<pubDate>Thu, 08 Jan 2009 00:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-547</guid>
		<description>[...] Over the holidays, I started playing with a new Yahoo! pipe to pull information from Technorati into a spreadsheet. The reasons why I wanted to do this are covered in this post about the quantitative analysis of blogs, and my eventual perl-based solution to the problem is covered in this post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Over the holidays, I started playing with a new Yahoo! pipe to pull information from Technorati into a spreadsheet. The reasons why I wanted to do this are covered in this post about the quantitative analysis of blogs, and my eventual perl-based solution to the problem is covered in this post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob B.</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-528</link>
		<dc:creator>Bob B.</dc:creator>
		<pubDate>Mon, 05 Jan 2009 18:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-528</guid>
		<description>Mat, 

Using a &lt;br&gt; worked.  Excellent!  Thanks for the tip.</description>
		<content:encoded><![CDATA[<p>Mat, </p>
<p>Using a &lt;br&gt; worked.  Excellent!  Thanks for the tip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogger typology: quantitative analysis step 1 &#124; Mediaczar</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-517</link>
		<dc:creator>Blogger typology: quantitative analysis step 1 &#124; Mediaczar</dc:creator>
		<pubDate>Sun, 04 Jan 2009 20:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-517</guid>
		<description>[...] iFAQ             &#171; A simple perl script to interrogate the Technorati API [...]</description>
		<content:encoded><![CDATA[<p>[...] iFAQ             &laquo; A simple perl script to interrogate the Technorati API [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mat Morrison</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-511</link>
		<dc:creator>Mat Morrison</dc:creator>
		<pubDate>Sun, 04 Jan 2009 11:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-511</guid>
		<description>&lt;a href=&quot;http://twitter.com/themetz&quot; rel=&quot;nofollow&quot;&gt;@themetz&lt;/a&gt; - the perl and Excel stuff I make myself in the evenings and weekends. Lackeys do the complicated stuff like Java.

Actually - my team at &lt;a href=&quot;http://porternovelli.com&quot; rel=&quot;nofollow&quot;&gt;Porter Novelli&lt;/a&gt; are getting really good at doing this stuff themselves. Part of why I&#039;m doing more of this stuff is so that I can keep just far enough ahead of them that they don&#039;t overtake me!

The web really helps, of course. In the old days, someone with limited coding abilities like myself would have to give up when faced by complicated problems (or buy a reference book, which is often the same thing, I find.) These days, Google and the forums help you solve most things; it&#039;s rare that we find that we&#039;re the first person to have discovered a problem; most times we find that someone has trodden the path before and a solution (or solutions) have been provided. Part of the purpose of &lt;em&gt;this&lt;/em&gt; blog is to share stuff back into the community that I will have patched together from other people&#039;s work!</description>
		<content:encoded><![CDATA[<p><a href="http://twitter.com/themetz" rel="nofollow">@themetz</a> &#8211; the perl and Excel stuff I make myself in the evenings and weekends. Lackeys do the complicated stuff like Java.</p>
<p>Actually &#8211; my team at <a href="http://porternovelli.com" rel="nofollow">Porter Novelli</a> are getting really good at doing this stuff themselves. Part of why I&#8217;m doing more of this stuff is so that I can keep just far enough ahead of them that they don&#8217;t overtake me!</p>
<p>The web really helps, of course. In the old days, someone with limited coding abilities like myself would have to give up when faced by complicated problems (or buy a reference book, which is often the same thing, I find.) These days, Google and the forums help you solve most things; it&#8217;s rare that we find that we&#8217;re the first person to have discovered a problem; most times we find that someone has trodden the path before and a solution (or solutions) have been provided. Part of the purpose of <em>this</em> blog is to share stuff back into the community that I will have patched together from other people&#8217;s work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mat Morrison</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-510</link>
		<dc:creator>Mat Morrison</dc:creator>
		<pubDate>Sun, 04 Jan 2009 11:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-510</guid>
		<description>@Bob B. Thank you so much - I love what you&#039;ve done with the Pipe. The string builder is a v. smart way around the problem. It looks to me like you can add &quot;&lt;/br&gt;&quot; or &quot;&lt;/p&gt;&quot; in place of the &quot;--&quot;, although I&#039;d consider commas as well. In an ideal world I&#039;ll take the data into Google Docs at the end of the process.

Interestingly I&#039;d already come across (and bookmarked) your &lt;a href=&quot;http://www.semdevel.com/2008/12/11/top-keywords-yahoo-pipes/&quot; rel=&quot;nofollow&quot;&gt;Top Keywords - Yahoo  Pipes&lt;/a&gt; post; it helped me solve one of the early problems I&#039;d faced (back when my Pipe was actually working.) 

One of the problems I stumbled into (and which I still don&#039;t understand) was the sudden and unexpected failure of Pipes to retrieve my CSV file. Every version I&#039;d used up till then had worked, then - out of nowhere - it stopped working. Cloning the pipe didn&#039;t &quot;reboot&quot;. When I started again from a fresh canvas it fetched the pipes, but couldn&#039;t build the URLs.

I know pipes is a bit beta-y sometimes, but this was just frustrating. Stuff that had worked stopped working. Gah!

Will take a clone of your pipe, if that&#039;s OK, and give you full recognition and links on the new post. Am so pleased. Pipes is a far better tool for sharing with others than the perl script.</description>
		<content:encoded><![CDATA[<p>@Bob B. Thank you so much &#8211; I love what you&#8217;ve done with the Pipe. The string builder is a v. smart way around the problem. It looks to me like you can add &#8220;&lt;/br&gt;&#8221; or &#8220;&lt;/p&gt;&#8221; in place of the &#8220;&#8211;&#8221;, although I&#8217;d consider commas as well. In an ideal world I&#8217;ll take the data into Google Docs at the end of the process.</p>
<p>Interestingly I&#8217;d already come across (and bookmarked) your <a href="http://www.semdevel.com/2008/12/11/top-keywords-yahoo-pipes/" rel="nofollow">Top Keywords &#8211; Yahoo  Pipes</a> post; it helped me solve one of the early problems I&#8217;d faced (back when my Pipe was actually working.) </p>
<p>One of the problems I stumbled into (and which I still don&#8217;t understand) was the sudden and unexpected failure of Pipes to retrieve my CSV file. Every version I&#8217;d used up till then had worked, then &#8211; out of nowhere &#8211; it stopped working. Cloning the pipe didn&#8217;t &#8220;reboot&#8221;. When I started again from a fresh canvas it fetched the pipes, but couldn&#8217;t build the URLs.</p>
<p>I know pipes is a bit beta-y sometimes, but this was just frustrating. Stuff that had worked stopped working. Gah!</p>
<p>Will take a clone of your pipe, if that&#8217;s OK, and give you full recognition and links on the new post. Am so pleased. Pipes is a far better tool for sharing with others than the perl script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Metz</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-509</link>
		<dc:creator>Adam Metz</dc:creator>
		<pubDate>Sun, 04 Jan 2009 08:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-509</guid>
		<description>Mat, did you hand-code this stuff yourself, or did your lackeys do it? Good stuff, man.</description>
		<content:encoded><![CDATA[<p>Mat, did you hand-code this stuff yourself, or did your lackeys do it? Good stuff, man.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob B.</title>
		<link>http://mediaczar.com/blog/2009/01/a-simple-perl-script-to-interrogate-the-technorati-api/comment-page-1/#comment-508</link>
		<dc:creator>Bob B.</dc:creator>
		<pubDate>Sun, 04 Jan 2009 07:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://mediaczar.com/blog/?p=220#comment-508</guid>
		<description>I&#039;ve created a small pipe that outputs what you want in the form of an RSS feed.  It&#039;s published here: http://pipes.yahoo.com/pipes/pipe.info?_id=OgntVi3a3RG6XTW_1L3fcQ.  I haven&#039;t quite figured out how to do line breaks in pipes yet so I&#039;ve separated the data with a double dash.  I&#039;ve been playing with pipes a lot lately.  I explain a few others at semdevel.com.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve created a small pipe that outputs what you want in the form of an RSS feed.  It&#8217;s published here: <a href="http://pipes.yahoo.com/pipes/pipe.info?_id=OgntVi3a3RG6XTW_1L3fcQ" rel="nofollow">http://pipes.yahoo.com/pipes/pipe.info?_id=OgntVi3a3RG6XTW_1L3fcQ</a>.  I haven&#8217;t quite figured out how to do line breaks in pipes yet so I&#8217;ve separated the data with a double dash.  I&#8217;ve been playing with pipes a lot lately.  I explain a few others at semdevel.com.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
