<?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: Adventures with my Technorati ranks &#34;toy&#34;</title>
	<atom:link href="http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/</link>
	<description></description>
	<pubDate>Thu, 04 Dec 2008 21:45:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bruno Rodrigues</title>
		<link>http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26060</link>
		<dc:creator>Bruno Rodrigues</dc:creator>
		<pubDate>Sat, 26 May 2007 10:05:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26060</guid>
		<description>PS: oops... this breaks with a '&#60;' char in the comments :P</description>
		<content:encoded><![CDATA[<p>PS: oops&#8230; this breaks with a &#8216;&lt;&#8217; char in the comments <img src='http://www.thetlog.net/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno Rodrigues</title>
		<link>http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26058</link>
		<dc:creator>Bruno Rodrigues</dc:creator>
		<pubDate>Sat, 26 May 2007 10:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26058</guid>
		<description>Why two tables?
Just use one table and always store a timestamp when you enter the data:
Timestamp, URL (key), Value (val), Primary key Timestamp, URL

This way you can even graph the evolution (or devolution) overtime of the ranking. You can rely on the timestamp to decide to query again or not (timestamp   86400 </description>
		<content:encoded><![CDATA[<p>Why two tables?<br />
Just use one table and always store a timestamp when you enter the data:<br />
Timestamp, URL (key), Value (val), Primary key Timestamp, URL</p>
<p>This way you can even graph the evolution (or devolution) overtime of the ranking. You can rely on the timestamp to decide to query again or not (timestamp   86400</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro Timóteo</title>
		<link>http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26009</link>
		<dc:creator>Pedro Timóteo</dc:creator>
		<pubDate>Thu, 24 May 2007 00:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26009</guid>
		<description>Old habits die hard. :) I'm more experienced with SQL than with XML, so that's what I used. Of course, there's a lot of room for improvement...

I don't reach the API request limit if I do it &lt;i&gt;once a day&lt;/i&gt; (as my cron does). However, since this is a new "toy", I've been doing experiments, changing things here and there, forcing an update after adding another blog, and so on. That's why I hit the limit, 2 days ago. As of now, my script updates all the blogs when called; maybe having an option to update just one (when adding a new one) would be a good idea.

The problem, however, isn't the request limit, but the other problem I described. It's probably a Technorati bug, but I've seen it happen more than once. Say I have a blog with about 400 incoming links, I update it from Technorati, and suddenly it has only 30 links or something. "What the...?!" I update it again, and it's back to 400.

Sure, since this isn't "life or death" stuff, I could have left it with an incorrect value for a day, but this way works around that problem.

But, yes, there's a lot that can be improved -- though in terms of results visible to the user, I'd say it's working perfectly.</description>
		<content:encoded><![CDATA[<p>Old habits die hard. <img src='http://www.thetlog.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> I&#8217;m more experienced with SQL than with XML, so that&#8217;s what I used. Of course, there&#8217;s a lot of room for improvement&#8230;</p>
<p>I don&#8217;t reach the API request limit if I do it <i>once a day</i> (as my cron does). However, since this is a new &#8220;toy&#8221;, I&#8217;ve been doing experiments, changing things here and there, forcing an update after adding another blog, and so on. That&#8217;s why I hit the limit, 2 days ago. As of now, my script updates all the blogs when called; maybe having an option to update just one (when adding a new one) would be a good idea.</p>
<p>The problem, however, isn&#8217;t the request limit, but the other problem I described. It&#8217;s probably a Technorati bug, but I&#8217;ve seen it happen more than once. Say I have a blog with about 400 incoming links, I update it from Technorati, and suddenly it has only 30 links or something. &#8220;What the&#8230;?!&#8221; I update it again, and it&#8217;s back to 400.</p>
<p>Sure, since this isn&#8217;t &#8220;life or death&#8221; stuff, I could have left it with an incorrect value for a day, but this way works around that problem.</p>
<p>But, yes, there&#8217;s a lot that can be improved &#8212; though in terms of results visible to the user, I&#8217;d say it&#8217;s working perfectly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Jorge Andrade</title>
		<link>http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26007</link>
		<dc:creator>Carlos Jorge Andrade</dc:creator>
		<pubDate>Wed, 23 May 2007 23:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.thetlog.net/2007/05/23/adventures-with-my-technorati-ranks-toy/#comment-26007</guid>
		<description>Jesus, could you made it more complicated ? :-)
My version uses no DB table and with caching I never reached the API request limit.

Why so many database operations ? This is my "db" http://dev.karlus.net/asteriscoRanks/rank.xml ;-)</description>
		<content:encoded><![CDATA[<p>Jesus, could you made it more complicated ? <img src='http://www.thetlog.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
My version uses no DB table and with caching I never reached the API request limit.</p>
<p>Why so many database operations ? This is my &#8220;db&#8221; <a href="http://dev.karlus.net/asteriscoRanks/rank.xml" rel="nofollow">http://dev.karlus.net/asteriscoRanks/rank.xml</a> <img src='http://www.thetlog.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
