<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Cursebird Leaderboard</title>
	<atom:link href="http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/</link>
	<description></description>
	<lastBuildDate>Wed, 02 Nov 2011 15:00:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: JESSE DZIEDZIC</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-60</link>
		<dc:creator><![CDATA[JESSE DZIEDZIC]]></dc:creator>
		<pubDate>Thu, 20 Oct 2011 06:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-60</guid>
		<description><![CDATA[That was interesting piece of writing!]]></description>
		<content:encoded><![CDATA[<p>That was interesting piece of writing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-34</link>
		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Sun, 20 Dec 2009 17:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-34</guid>
		<description><![CDATA[All the best of luck to you!.Thanks for the information.]]></description>
		<content:encoded><![CDATA[<p>All the best of luck to you!.Thanks for the information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I cursebird more than you do. &#171; Thinking Stiff</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-14</link>
		<dc:creator><![CDATA[I cursebird more than you do. &#171; Thinking Stiff]]></dc:creator>
		<pubDate>Wed, 11 Feb 2009 07:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-14</guid>
		<description><![CDATA[[...] this is just from seeing people come up on the live feed. Many people have asked for a Top 10 list (thoughts on a leaderboard). I wouldn&#8217;t mind seeing one either, but after staring at it for hundreds of hours, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] this is just from seeing people come up on the live feed. Many people have asked for a Top 10 list (thoughts on a leaderboard). I wouldn&#8217;t mind seeing one either, but after staring at it for hundreds of hours, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thinkingstiff</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-12</link>
		<dc:creator><![CDATA[thinkingstiff]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 21:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-12</guid>
		<description><![CDATA[I also just noticed that on a cleaned list, with my original hand-typed 700 tweets, I still would have been on the top. An example of the &quot;cussing their hearts out&quot; tweeter being able to take the top.]]></description>
		<content:encoded><![CDATA[<p>I also just noticed that on a cleaned list, with my original hand-typed 700 tweets, I still would have been on the top. An example of the &#8220;cussing their hearts out&#8221; tweeter being able to take the top.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thinkingstiff</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-10</link>
		<dc:creator><![CDATA[thinkingstiff]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 21:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-10</guid>
		<description><![CDATA[I&#039;ve also thought that maybe I&#039;m overestimating the staying power of the bots. Perhaps manual cleaning won&#039;t be that big of a deal and the bots will get tired of trying.

Two lists might work.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve also thought that maybe I&#8217;m overestimating the staying power of the bots. Perhaps manual cleaning won&#8217;t be that big of a deal and the bots will get tired of trying.</p>
<p>Two lists might work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Henry</title>
		<link>http://blog.thinkingstiff.com/2009/02/04/cursebird-leaderboard/#comment-8</link>
		<dc:creator><![CDATA[Richard Henry]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 20:52:10 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingstiff.wordpress.com/?p=91#comment-8</guid>
		<description><![CDATA[@bollocks is on the list of bugs to fix before I release the leaderboard. It&#039;s caused by the Twitter API returning swears matching a username in addition to the text body, which isn&#039;t the desired result. It was only when someone tweeted me about it that I realised things weren&#039;t happening as expected.

---

Possible Solutions:

1, 2: These are both possible solutions; and it&#039;s always better to automate rules if possible to keep a level playing field. I&#039;m thinking about a couple things myself.

3: Unfortunately this is pretty much impossible. Grabbing follower counts for each user would require far too much API interaction above and beyond that I&#039;m already doing; and I would quickly hit the rate limit.

4: It would be too easy to evade that by having an array of random dictionary words inserted into tweets to prevent duplication.

---

Conclusion:

Perhaps I could publish a filtered list alongside a raw list?

---

Good article, you&#039;ve said a lot of things I wanted to say myself in a post but never had the time.

Richard]]></description>
		<content:encoded><![CDATA[<p>@bollocks is on the list of bugs to fix before I release the leaderboard. It&#8217;s caused by the Twitter API returning swears matching a username in addition to the text body, which isn&#8217;t the desired result. It was only when someone tweeted me about it that I realised things weren&#8217;t happening as expected.</p>
<p>&#8212;</p>
<p>Possible Solutions:</p>
<p>1, 2: These are both possible solutions; and it&#8217;s always better to automate rules if possible to keep a level playing field. I&#8217;m thinking about a couple things myself.</p>
<p>3: Unfortunately this is pretty much impossible. Grabbing follower counts for each user would require far too much API interaction above and beyond that I&#8217;m already doing; and I would quickly hit the rate limit.</p>
<p>4: It would be too easy to evade that by having an array of random dictionary words inserted into tweets to prevent duplication.</p>
<p>&#8212;</p>
<p>Conclusion:</p>
<p>Perhaps I could publish a filtered list alongside a raw list?</p>
<p>&#8212;</p>
<p>Good article, you&#8217;ve said a lot of things I wanted to say myself in a post but never had the time.</p>
<p>Richard</p>
]]></content:encoded>
	</item>
</channel>
</rss>

