to
add to the bug report!
/Martin
On Dec 6, 2:47 pm, Damon Clinkscales sca...@pobox.com wrote:
On Sun, Dec 6, 2009 at 3:24 PM, Martin Omander moman...@google.com wrote:
I noticed the same behavior in my app: when I include since_id in the
search API call, I often don't get all the tweets I
I noticed the same behavior in my app: when I include since_id in the
search API call, I often don't get all the tweets I should. If I run
without since_id, I see tweets with IDs that should have shown up in
the search where I included since_id.
Any response from Twitter? The since_id parameter
One interesting problem with this kind of book is what programming
language to use. The book is not about a programming language, but it
has to contain code examples. Whatever language you pick, you will
turn away potential readers who don't know that language. For example,
it looks like the
Same here; my app runs on Google App Engine and 40% of the requests to
the Twitter Search API get the 503 error message indicating rate
limiting.
Is there anything we as app authors can do on our side to alleviate
the problem?
/Martin
On Oct 5, 1:53 pm, Paul Kinlan paul.kin...@gmail.com
Chad,
Very nice service that will accelerate development for app developers
who search Twitter. Best of luck!
/Martin
On Sep 29, 7:18 pm, Chad Etzel jazzyc...@gmail.com wrote:
@Jesse, TweetHook is leveraging the Search API for now. The Streaming
API has a totally different EULA and other
Another data point: I also run a Python app on Google App Engine. It
hits the Twitter search API 3 times per minute, with different search
parameters. About 20% of my app's search requests get a 503L error
code, and the other 80% return search results as expected. There is no
clear pattern or
Doug,
Thanks for letting us know about the new request limit. I was worried
something was wrong on my side. Like the others are saying; it would
have been nice with a heads-up.
Cheers,
/Martin
you are doing so we can debug?
1.http://code.google.com/p/twitter-api/issues/detail?id=795
Thanks,
Doug
On Mon, Jul 13, 2009 at 4:38 PM, Martin Omander moman...@google.com
wrote:
Hi there,
Earlier today I ran afoul of the rate limit for updates through the
API. But no error
It is odd that my app is held to a rate limit that is hidden from me.
When I call the rate limit API, I get the rate for my IP address,
which is meaningless when it comes to status updates.
My only option is to keep sending status updates until I get a 403
error message back. I hope that won't
to see if a specific machine that is returning incorrect information.
Thanks,
Doug
On Mon, Jul 13, 2009 at 4:26 PM, Martin Omander moman...@google.com
wrote:
Hi there,
I'm getting the same thing, that is the rate limit for my IP address
rather than for the account... most
so we can debug?
1.http://code.google.com/p/twitter-api/issues/detail?id=795
Thanks,
Doug
On Mon, Jul 13, 2009 at 4:38 PM, Martin Omander moman...@google.com wrote:
Hi there,
Earlier today I ran afoul of the rate limit for updates through the
API. But no error was returned to my
Hi there,
I'm getting the same thing, that is the rate limit for my IP address
rather than for the account... most of the time. I run this curl
command
curl -u username:password http://twitter.com/account/rate_limit_status.xml
where username and password are the account's real username and
Hi there,
Earlier today I ran afoul of the rate limit for updates through the
API. But no error was returned to my app. To make sure my app wasn't
suppressing the error message, I sent an update using curl:
curl -u username:password -d status=testing
http://twitter.com/statuses/update.xml
-D
13 matches
Mail list logo
