It now appears to be working with max_id. I was in the process of
gathering data to fill out an issue report when it failed to fail. ;-)
Murphy, where are you? ;-)
On Jan 12, 9:37 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote:
I'm testing this and it looks like I can reproduce an Internal
RE: Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status with
Oh ... I thought I was doing something wrong. But I was getting
Internal Server Error, not 404. Here's what I was doing (Perl, but
the HTTP should be obvious):
q = $search_string,
geocode = $geocode,
rpp = 100,
max_id = $max_id,
page = $page
On
Somebody's corollary to Murphy's Law: When a programmer writes logic
into his Perl Twitter app to dump the handle and error objects in YAML
on an error, so he can send the data to Twitter, he stops getting
'Internal Server Error' from Twitter. ;-)
On Jan 12, 10:56 am, M. Edward (Ed) Borasky
Andy - I'm experiencing the the same problem. All geosearches result
in:
{error:Couldn't find Status with ID=7406995447}
On Jan 12, 11:38 am, andy_edn andygup@gmail.com wrote:
RE:Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
I'm testing this and it looks like I can reproduce an Internal Server
Error when I use the call
_uri: !!perl/scalar:URI::http
http://api.twitter.com/1/search.json?rpp=100page=1q=geocode=40.645%2C-124.763%2C100mimax_id=7678398633
_uri_canonical: !!perl/scalar:URI::http
done
On Jan 3, 4:06 pm, Mark McBride mmcbr...@twitter.com wrote:
John, can you open an issue on the code
tracker?http://code.google.com/p/twitter-api/issues
---Mark
http://twitter.com/mccv
On Sun, Jan 3, 2010 at 1:17 PM, John munz...@gmail.com wrote:
another thing i've noticed is
another thing i've noticed is that search doesn't return as many
records as when you do a search on twitter.com. You can verify using
#tests. Returns about 5 records using the API while twitter.com
returns about 20+. Could be related to the issue above.
John, can you open an issue on the code tracker?
http://code.google.com/p/twitter-api/issues
---Mark
http://twitter.com/mccv
On Sun, Jan 3, 2010 at 1:17 PM, John munz...@gmail.com wrote:
another thing i've noticed is that search doesn't return as many
records as when you do a search on
