<?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 for Tweetboard Blog</title>
	<atom:link href="http://blog.tweetboard.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tweetboard.com</link>
	<description>The official Tweetboard blog</description>
	<lastBuildDate>Mon, 01 Mar 2010 20:39:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on About this week&#8217;s downtime by juicycolors</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-567</link>
		<dc:creator>juicycolors</dc:creator>
		<pubDate>Mon, 01 Mar 2010 20:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-567</guid>
		<description>Cool, i am waiting for the confirmation !!!</description>
		<content:encoded><![CDATA[<p>Cool, i am waiting for the confirmation !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Ceri May (@CezzBB)</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-564</link>
		<dc:creator>Ceri May (@CezzBB)</dc:creator>
		<pubDate>Fri, 26 Feb 2010 03:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-564</guid>
		<description>Pulling of new tweets is unrelated, it seems the problem you are having is specific to yourself and is related to twitter auth codes... As advised via tweetboard please make sure you refresh the page and then login and authorise the tweetboard app using your main twitter username, without this we can not pull new tweets.</description>
		<content:encoded><![CDATA[<p>Pulling of new tweets is unrelated, it seems the problem you are having is specific to yourself and is related to twitter auth codes&#8230; As advised via tweetboard please make sure you refresh the page and then login and authorise the tweetboard app using your main twitter username, without this we can not pull new tweets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by sisterstalk</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-563</link>
		<dc:creator>sisterstalk</dc:creator>
		<pubDate>Wed, 24 Feb 2010 07:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-563</guid>
		<description>It appears you&#039;re still having problems. My Tweetboard hasn&#039;t updated in over 21 hours.</description>
		<content:encoded><![CDATA[<p>It appears you&#39;re still having problems. My Tweetboard hasn&#39;t updated in over 21 hours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by ramim</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-562</link>
		<dc:creator>ramim</dc:creator>
		<pubDate>Sun, 21 Feb 2010 14:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-562</guid>
		<description>No israel = NO WAR</description>
		<content:encoded><![CDATA[<p>No israel = NO WAR</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Ceri May (@CezzBB)</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-555</link>
		<dc:creator>Ceri May (@CezzBB)</dc:creator>
		<pubDate>Tue, 16 Feb 2010 22:38:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-555</guid>
		<description>Sorry for the delay in replying to you Disqus had moderated your comment for some reason. It was a *fun* ordeal but it is one we have learned from.</description>
		<content:encoded><![CDATA[<p>Sorry for the delay in replying to you Disqus had moderated your comment for some reason. It was a *fun* ordeal but it is one we have learned from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Ceri May (@CezzBB)</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-556</link>
		<dc:creator>Ceri May (@CezzBB)</dc:creator>
		<pubDate>Tue, 16 Feb 2010 22:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-556</guid>
		<description>It has been considered but we couldn&#039;t get the same speed or I/O as we do with the SSD drives.</description>
		<content:encoded><![CDATA[<p>It has been considered but we couldn&#39;t get the same speed or I/O as we do with the SSD drives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Ceri May (@CezzBB)</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-554</link>
		<dc:creator>Ceri May (@CezzBB)</dc:creator>
		<pubDate>Tue, 16 Feb 2010 22:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-554</guid>
		<description>Due to space restraints the backup was done simultaneously to the first step expecting errors latter on in the stage. Lesson learned and we will always assume the worst with every change from now on.</description>
		<content:encoded><![CDATA[<p>Due to space restraints the backup was done simultaneously to the first step expecting errors latter on in the stage. Lesson learned and we will always assume the worst with every change from now on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Corey Ward</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-553</link>
		<dc:creator>Corey Ward</dc:creator>
		<pubDate>Tue, 16 Feb 2010 20:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-553</guid>
		<description>Ouch. Note to TweetBoard: backup your database before making schema changes. I like to keep another db server ready and synced at all times, then if changes break something the application can roll over to the mirrored server without hardly any data loss while the primary database can be recovered.</description>
		<content:encoded><![CDATA[<p>Ouch. Note to TweetBoard: backup your database before making schema changes. I like to keep another db server ready and synced at all times, then if changes break something the application can roll over to the mirrored server without hardly any data loss while the primary database can be recovered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Announcing the Pre-Release Team, making a bulletproof Tweetboard by silicone bracelets</title>
		<link>http://blog.tweetboard.com/announcing-the-pre-release-team-making-a-bulletproof-tweetboard-204/comment-page-1/#comment-550</link>
		<dc:creator>silicone bracelets</dc:creator>
		<pubDate>Thu, 11 Feb 2010 00:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=204#comment-550</guid>
		<description>The word Debossed means the letters on the wristbands are sunk into the silicone surface, similar to the popular live strong yellow wristband.</description>
		<content:encoded><![CDATA[<p>The word Debossed means the letters on the wristbands are sunk into the silicone surface, similar to the popular live strong yellow wristband.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About this week&#8217;s downtime by Irwin</title>
		<link>http://blog.tweetboard.com/downtime-explained-354/comment-page-1/#comment-552</link>
		<dc:creator>Irwin</dc:creator>
		<pubDate>Sun, 31 Jan 2010 03:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tweetboard.com/?p=354#comment-552</guid>
		<description>Seriously you should move your database to a cloud service like google appengine or S3 to avoid such issues. Why do you store this in an old fashioned SQL instance ? it s just more expensive, hard to maintain and prone to errors. If more people use your service you really need to change your infrastructure.</description>
		<content:encoded><![CDATA[<p>Seriously you should move your database to a cloud service like google appengine or S3 to avoid such issues. Why do you store this in an old fashioned SQL instance ? it s just more expensive, hard to maintain and prone to errors. If more people use your service you really need to change your infrastructure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
