Didn't want to file a bug on this yet. I wanted to see if anyone else
was experiencing this problem:
1. Upgraded to version 0.36
2. Open spaz, wait a few seconds, you get one or more of these
messages in a native dialog box:
ERROR: 400 error - Exceeded request limit. Response from Twitter:
{ "error" : "Rate limit exceeded. Clients may not make more than 70
requets per hour.", "request" : "\/direct_messages.json?_=XXXXXXXX"}
where XXXXX is some number. Maybe it's twitter's fault. didn't
happen before version 0.36
OS: Windows XP Pro
AIR: 1.0.6.4030
Refresh Interval: 3 minutes
I checked my network traffic with ethereal and it *does not* look like
spaz is making that many requests. in fact, on the first request for
"/statuses/friends_timeline.json?", twitter is returning that error.
> Didn't want to file a bug on this yet. I wanted to see if anyone else > was experiencing this problem:
> 1. Upgraded to version 0.36 > 2. Open spaz, wait a few seconds, you get one or more of these > messages in a native dialog box:
> ERROR: 400 error - Exceeded request limit. Response from Twitter: > { "error" : "Rate limit exceeded. Clients may not make more than 70 > requets per hour.", "request" : "\/direct_messages.json?_=XXXXXXXX"}
> where XXXXX is some number. Maybe it's twitter's fault. didn't > happen before version 0.36
> OS: Windows XP Pro > AIR: 1.0.6.4030 > Refresh Interval: 3 minutes
> I checked my network traffic with ethereal and it *does not* look like > spaz is making that many requests. in fact, on the first request for > "/statuses/friends_timeline.json?", twitter is returning that error.
> Everyone using apps that go through the API are having the same
> problem. Check the spaz-users group or what I've posted on the spaz
> twitter feed.
> On Jan 16, 2008 11:00 AM, Robert Cadena <robert.cad...@gmail.com> wrote:
> > Didn't want to file a bug on this yet. I wanted to see if anyone else
> > was experiencing this problem:
> > 1. Upgraded to version 0.36
> > 2. Open spaz, wait a few seconds, you get one or more of these
> > messages in a native dialog box:
> > ERROR: 400 error - Exceeded request limit. Response from Twitter:
> > { "error" : "Rate limit exceeded. Clients may not make more than 70
> > requets per hour.", "request" : "\/direct_messages.json?_=XXXXXXXX"}
> > where XXXXX is some number. Maybe it's twitter's fault. didn't
> > happen before version 0.36
> > OS: Windows XP Pro
> > AIR: 1.0.6.4030
> > Refresh Interval: 3 minutes
> > I checked my network traffic with ethereal and it *does not* look like
> > spaz is making that many requests. in fact, on the first request for
> > "/statuses/friends_timeline.json?", twitter is returning that error.
the last i heard is that the "refresh rate" has been lowered to 9 per
hour. which is rediculious. and i have no idea why twitter would do
this.. it seems as a whole lot of twitter users are very disappointed/
angry/upset/confused/etc about this.. myself included
On Jan 16, 10:00 am, Robert Cadena <robert.cad...@gmail.com> wrote:
> Didn't want to file a bug on this yet. I wanted to see if anyone else
> was experiencing this problem:
> 1. Upgraded to version 0.36
> 2. Open spaz, wait a few seconds, you get one or more of these
> messages in a native dialog box:
> ERROR: 400 error - Exceeded request limit. Response from Twitter:
> { "error" : "Rate limit exceeded. Clients may not make more than 70
> requets per hour.", "request" : "\/direct_messages.json?_=XXXXXXXX"}
> where XXXXX is some number. Maybe it's twitter's fault. didn't
> happen before version 0.36
> OS: Windows XP Pro
> AIR: 1.0.6.4030
> Refresh Interval: 3 minutes
> I checked my network traffic with ethereal and it *does not* look like
> spaz is making that many requests. in fact, on the first request for
> "/statuses/friends_timeline.json?", twitter is returning that error.
> the last i heard is that the "refresh rate" has been lowered to 9 per > hour. which is rediculious. and i have no idea why twitter would do > this.. it seems as a whole lot of twitter users are very disappointed/ > angry/upset/confused/etc about this.. myself included
It's *not* permanent. It was a reaction to apparently overwhelming traffic surrounding the Macworld keynote, and last alex posted on the dev list, it was still pretty bad. Sucks, I know.
"I'm deploying right now, and the API rate limit should soon be back to normal. My sincere apologies for the delay, but I needed the go-ahead from our operations team before inundating our servers further. I'm hoping that we'll have some announcements later this week in regards to increased capacity, so events like this don't happen again."
Yeah, 3 is the minimum, and it's right up to the edge: 60/3 = 20 refreshes, and you have 3 requests per refresh on the main timeline, which gives you 60 reqs per hour. 70 is the max.
On Jan 17, 2008 10:15 AM, hchorey <hcho...@gmail.com> wrote:
Hopefully this will end up being a feature request, but how feasible is it to add an ability to turn off the updating of the other timelines? I honestly never use the global timeline so that's 1/3 of my allowed refreshes that are pretty much going completely to waste.
Even if it couldn't be made into a toggle, wouldn't it make sense to only update the currently selected timeline anyway?
On Jan 17, 2008 9:53 AM, Ed Finkler <funkat...@gmail.com> wrote:
> Yeah, 3 is the minimum, and it's right up to the edge: 60/3 = 20 > refreshes, and you have 3 requests per refresh on the main timeline, > which gives you 60 reqs per hour. 70 is the max.
> On Jan 17, 2008 10:15 AM, hchorey <hcho...@gmail.com> wrote:
> > I had a few last night, but my update interval was set to 3 minutes. > > Just changed it to five, so that should take care of it, I think.
> > - hunter
> > On Jan 16, 6:01pm, Graeme <dunl...@gmail.com> wrote: > > > I'm not; I have my refresh interval set to 5 mins
> > > On Jan 17, 2008 9:46AM, Mighty_Squid <kate.fala...@gmail.com> wrote:
> > > > I totally lied. Still getting them. Just not as many.
On Jan 17, 2008 12:26 PM, Nathan Stohlmann <nathan.stohlm...@gmail.com> wrote:
> Hopefully this will end up being a feature request, but how feasible > is it to add an ability to turn off the updating of the other > timelines? I honestly never use the global timeline so that's 1/3 of > my allowed refreshes that are pretty much going completely to waste.
> Even if it couldn't be made into a toggle, wouldn't it make sense to > only update the currently selected timeline anyway?
It only updates the selected timeline, but a request is made to three API methods on the main timeline:
- People you're following - Replies - Direct messages
The data from each is combined, and duplicates are discarded.
> On Jan 17, 2008 12:26 PM, Nathan Stohlmann <nathan.stohlm...@gmail.com> wrote:
> > Hopefully this will end up being a feature request, but how feasible > > is it to add an ability to turn off the updating of the other > > timelines? I honestly never use the global timeline so that's 1/3 of > > my allowed refreshes that are pretty much going completely to waste.
> > Even if it couldn't be made into a toggle, wouldn't it make sense to > > only update the currently selected timeline anyway?
> It only updates the selected timeline, but a request is made to three > API methods on the main timeline:
> - People you're following > - Replies > - Direct messages
> The data from each is combined, and duplicates are discarded.
For the last couple of days I have been getting this 400 error at the
time that Spaz launches and makes it's first request. Per the
suggestions made here I have upped the rate from the default 3 to 5,
but still get the 400 error dialog. Were things downgraded for
MacWorld, and they just havn't gotten around to restoring the default
settings? I'm not having any problem with the web interface.
Mac OSX 10.4.11
Thanks.
On Jan 17, 3:32 pm, "Ed Finkler" <funkat...@gmail.com> wrote:
On Jan 21, 2008 9:24 AM, tip...@gmail.com <tip...@gmail.com> wrote:
> For the last couple of days I have been getting this 400 error at the > time that Spaz launches and makes it's first request. Per the > suggestions made here I have upped the rate from the default 3 to 5, > but still get the 400 error dialog. Were things downgraded for > MacWorld, and they just havn't gotten around to restoring the default > settings? I'm not having any problem with the web interface.
The "normal" rate limits have been restored. The web site doesn't use the API, so you'll never see rate limit issues there.
If you are not running any other apps that use the API, and you are able to connect *at all*, I'd have to assume there's something mucked up with Twitter and your account specifically. If you're certain of the first two points, I can help you try to sort it out off-list, but I'd need to get your username and password, which you may not want to share. Otherwise, you can contact Twitter's support and see if they can help.
On Jan 26, 2008 9:29 PM, Sofia Kallin <sofiakal...@googlemail.com> wrote:
> I am still getting the 400 error message when I start Spaz.
All the time? After waiting an hour? Are you using any other programs to access Twitter (other than the web site)? Does it happen on more than one machine, and at more than one location? Can another client (say, Snitter) log-in fine?
> On Jan 26, 2008 9:29 PM, Sofia Kallin <sofiakal...@googlemail.com> wrote: > > I am still getting the 400 error message when I start Spaz.
> All the time? After waiting an hour? Are you using any other programs > to access Twitter (other than the web site)? Does it happen on more > than one machine, and at more than one location? Can another client > (say, Snitter) log-in fine?
On Jan 26, 2008 8:54 PM, Ed Finkler <funkat...@gmail.com> wrote:
> On Jan 26, 2008 9:45 PM, Sofia Kallin <sofiakal...@googlemail.com> wrote: > > Yes, the error msg comes when I am using Spaz for the first time of the > day.
> > I do have an alter-ego & twitter account that I use Snitter for and that > > works fine.
> Try using the *same* account on Snitter. Do you get a rate limit error?
No error message ... however the tweets showing are a mix from both of my accounts, v weird but that is of course a Snitter probs :)
> > Maybe I should unistall Spaz and install it again to see if that works?
> I want to see if this is something specific to Spaz, or an issue with > Twitter. Trying the same account in another application would help.
> Also, if it *does* start working in the other app, switch back to Spaz > to see if it continues to throw errors.
Ok back Spaz and with my Sofia account and no error message :). I will have it in - of course - and let you know if the error message appears.
> On Jan 26, 2008 8:54 PM, Ed Finkler <funkat...@gmail.com> wrote:
> > On Jan 26, 2008 9:45 PM, Sofia Kallin <sofiakal...@googlemail.com> > > wrote: > > > Yes, the error msg comes when I am using Spaz for the first time of > > the day.
> > > I do have an alter-ego & twitter account that I use Snitter for and > > that > > > works fine.
> > Try using the *same* account on Snitter. Do you get a rate limit error?
> No error message ... however the tweets showing are a mix from both of my > accounts, v weird but that is of course a Snitter probs :)
> > > Maybe I should unistall Spaz and install it again to see if that > > works?
> > I want to see if this is something specific to Spaz, or an issue with > > Twitter. Trying the same account in another application would help.
> > Also, if it *does* start working in the other app, switch back to Spaz > > to see if it continues to throw errors.
> Ok back Spaz and with my Sofia account and no error message :). I will > have it in - of course - and let you know if the error message appears.
|
