<?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: Rough Week for BeTwittered And Twitter</title>
	<atom:link href="http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/</link>
	<description>My journey into the software development world.</description>
	<lastBuildDate>Wed, 16 May 2012 13:36:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Twitter Search</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-70</link>
		<dc:creator>Twitter Search</dc:creator>
		<pubDate>Wed, 27 May 2009 02:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-70</guid>
		<description>thats great that you are talking about the twitter api,a good example of searching with the twitter api is on twiogle.com because you can search on twitter and google at the same time.</description>
		<content:encoded><![CDATA[<p>thats great that you are talking about the twitter api,a good example of searching with the twitter api is on twiogle.com because you can search on twitter and google at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HeyChinaski.com &#187; Blog Archive &#187; Is Michael Arrington Lying To Us?</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-69</link>
		<dc:creator>HeyChinaski.com &#187; Blog Archive &#187; Is Michael Arrington Lying To Us?</dc:creator>
		<pubDate>Sun, 22 Jun 2008 01:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-69</guid>
		<description>[...] quick Google search turned up this post on 32Hours, the blog of the creators of BeTwittered.  The first comment is from someone [...]</description>
		<content:encoded><![CDATA[<p>[...] quick Google search turned up this post on 32Hours, the blog of the creators of BeTwittered.  The first comment is from someone [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Princess Ivory</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-68</link>
		<dc:creator>Princess Ivory</dc:creator>
		<pubDate>Tue, 03 Jun 2008 17:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-68</guid>
		<description>And I no sooner post that, then content loads!

Go figure! It is sporadic access, however.

Princess Ivory</description>
		<content:encoded><![CDATA[<p>And I no sooner post that, then content loads!</p>
<p>Go figure! It is sporadic access, however.</p>
<p>Princess Ivory</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Princess Ivory</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-67</link>
		<dc:creator>Princess Ivory</dc:creator>
		<pubDate>Tue, 03 Jun 2008 17:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-67</guid>
		<description>Update: Today, Tuesday 6/3/08, my BeTwittered continues to be blank on my Google iPage. Anyone else still having this problem? I&#039;ve had to resort to using the Twitter.com page instead.

Princess Ivory</description>
		<content:encoded><![CDATA[<p>Update: Today, Tuesday 6/3/08, my BeTwittered continues to be blank on my Google iPage. Anyone else still having this problem? I&#8217;ve had to resort to using the Twitter.com page instead.</p>
<p>Princess Ivory</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-66</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sun, 01 Jun 2008 15:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-66</guid>
		<description>@Princess Ivory,

Thanks for the input.  I won&#039;t be able to make the change right away, but I can add an option to turn off auto-refreshes.  Thanks for the idea! :^) I&#039;m assuming, too, that Twitter will turn their limit back up to 70 refreshes per hour when they figure out how to handle their customer load.  That alone, should be enough fix the problem for most everyone.  Hopefully they are quick!

Thanks again!</description>
		<content:encoded><![CDATA[<p>@Princess Ivory,</p>
<p>Thanks for the input.  I won&#8217;t be able to make the change right away, but I can add an option to turn off auto-refreshes.  Thanks for the idea! :^) I&#8217;m assuming, too, that Twitter will turn their limit back up to 70 refreshes per hour when they figure out how to handle their customer load.  That alone, should be enough fix the problem for most everyone.  Hopefully they are quick!</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Princess Ivory</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-65</link>
		<dc:creator>Princess Ivory</dc:creator>
		<pubDate>Sun, 01 Jun 2008 15:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-65</guid>
		<description>&quot;or refresh/reopen the iGoogle page, that counts too.&quot;

Oh my, this will be a real problem. I use my IGooge page as my hompage desktop, and click from it to all the other things on it: reader, email, bookmarks, etc.

Any chance this can NOT be an issue? If this is truly the case, then I will not be able to use your product. I need something on my Ipage that will not cause any functions to time-out or go over preset limits.

Princess Ivory
(thanks for responding to my last post so quickly and thoroughly)</description>
		<content:encoded><![CDATA[<p>&#8220;or refresh/reopen the iGoogle page, that counts too.&#8221;</p>
<p>Oh my, this will be a real problem. I use my IGooge page as my hompage desktop, and click from it to all the other things on it: reader, email, bookmarks, etc.</p>
<p>Any chance this can NOT be an issue? If this is truly the case, then I will not be able to use your product. I need something on my Ipage that will not cause any functions to time-out or go over preset limits.</p>
<p>Princess Ivory<br />
(thanks for responding to my last post so quickly and thoroughly)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-64</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sun, 01 Jun 2008 14:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-64</guid>
		<description>@Olly Newport and @Princess Ivory
Thanks for taking the time to leave posts for us.  It helps Scott and me keep up with what&#039;s  going on with everyone, and gives everyone else a chance to share info.

It&#039;s true, the rate limit was lowered quite a bit as the Twitter crew is trying to deal with their recent problems.  I have already temporarily dropped refreshes in BeTwittered to every 4 minutes.  That alone should not hit the rate limit Twitter has in place, but if you use the refresh link, or refresh/reopen the iGoogle page, that counts too. Also, if you have any other Twitter clients, they add to your refresh count.  The count is kept by user, not by client, so this will be a problem for some people too.
Robert</description>
		<content:encoded><![CDATA[<p>@Olly Newport and @Princess Ivory<br />
Thanks for taking the time to leave posts for us.  It helps Scott and me keep up with what&#8217;s  going on with everyone, and gives everyone else a chance to share info.</p>
<p>It&#8217;s true, the rate limit was lowered quite a bit as the Twitter crew is trying to deal with their recent problems.  I have already temporarily dropped refreshes in BeTwittered to every 4 minutes.  That alone should not hit the rate limit Twitter has in place, but if you use the refresh link, or refresh/reopen the iGoogle page, that counts too. Also, if you have any other Twitter clients, they add to your refresh count.  The count is kept by user, not by client, so this will be a problem for some people too.<br />
Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olly Newport</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-63</link>
		<dc:creator>Olly Newport</dc:creator>
		<pubDate>Sun, 01 Jun 2008 12:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-63</guid>
		<description>@Princess Ivory

The new Twitter API key has been lowered from 70 updates per hour to 30, meaning that the more the BeTwittered gadget refreshes the more API timeline uses to Twitter this takes up.</description>
		<content:encoded><![CDATA[<p>@Princess Ivory</p>
<p>The new Twitter API key has been lowered from 70 updates per hour to 30, meaning that the more the BeTwittered gadget refreshes the more API timeline uses to Twitter this takes up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Princess Ivory</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-62</link>
		<dc:creator>Princess Ivory</dc:creator>
		<pubDate>Sun, 01 Jun 2008 04:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-62</guid>
		<description>Your product is trying to refresh too frequently. Here is the error message I keep getting:

OOPS! Something went wrong...
400: Invalid request. You may have exceeded your rate limit of 70 timeline refreshes per hour. Don&#039;t worry, you don&#039;t have to wait an hour to get back in. Just sit tight for 5-10 minutes. Crack your knuckles for a while. Then ease up a bit on the refreshes!

BeTwittered will check back in every few minutes.</description>
		<content:encoded><![CDATA[<p>Your product is trying to refresh too frequently. Here is the error message I keep getting:</p>
<p>OOPS! Something went wrong&#8230;<br />
400: Invalid request. You may have exceeded your rate limit of 70 timeline refreshes per hour. Don&#8217;t worry, you don&#8217;t have to wait an hour to get back in. Just sit tight for 5-10 minutes. Crack your knuckles for a while. Then ease up a bit on the refreshes!</p>
<p>BeTwittered will check back in every few minutes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://32hours.com/2008/05/24/rough-week-for-betwittered-and-twitter/comment-page-1/#comment-61</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 31 May 2008 05:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/?p=21#comment-61</guid>
		<description>Hi Joel,

That&#039;s great news!  I&#039;ll contact you with some questions I have, and some suggestions that might help us work better together.  I&#039;ve had a quick look at the toolbar (nice job!) and have had a couple of thoughts already.  I&#039;ve moved to a new server from 32hours, and would like to make sure that CrunchBar gets it&#039;s own code-base since we&#039;re planning some changes and feature adds to the location you&#039;ve pointed out.

Thanks very much for the heads-up!
Robert</description>
		<content:encoded><![CDATA[<p>Hi Joel,</p>
<p>That&#8217;s great news!  I&#8217;ll contact you with some questions I have, and some suggestions that might help us work better together.  I&#8217;ve had a quick look at the toolbar (nice job!) and have had a couple of thoughts already.  I&#8217;ve moved to a new server from 32hours, and would like to make sure that CrunchBar gets it&#8217;s own code-base since we&#8217;re planning some changes and feature adds to the location you&#8217;ve pointed out.</p>
<p>Thanks very much for the heads-up!<br />
Robert</p>
]]></content:encoded>
	</item>
</channel>
</rss>

