I am seeing the same issue. In my case, the first four iterations work
(i.e. I retrieve 400 users), but the next call gives me a 404.
Are you using page parameter? If so, it was recently deprecated, so
that would explain what you are seeing... the first page over and over
again. Check the API documentation to see how to use the cursor
parameter.
On Dec 6, 8:25 pm, hansamann sven.hai...@googlemail.com wrote:
Hi all,
my code
I am seeing this as well.
This may be related to the 404 issue reported recently too (http://
groups.google.com/group/twitter-development-talk/browse_thread/thread/
ece2aec4fe601bd9)
On Dec 5, 2:19 pm, Colby Palmer colbywo...@gmail.com wrote:
I noticed this today too and then saw this post. I
I added this as issue 1264 in the twitter-api issue tracker, which
you'll have to find on your own. It appears they don't trust me enough
to let me post links here yet. :D
On Dec 8, 1:01 pm, Randy randy.posyn...@gmail.com wrote:
I am seeing the same issue. In my case, the first four iterations
Graph. I'd re-run your test to
see if you were just very unlucky, or if the issue persists.
-John Kaluckihttp://twitter.com/jkalucki
On Tue, Dec 8, 2009 at 1:40 PM, Randy randy.posyn...@gmail.com wrote:
I added this to the issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id
Help from another programming site, use urlencode() . That does the trick.
On Wed, Nov 11, 2009 at 6:06 PM, mndasher mndas...@gmail.com wrote:
I store my content in a MySQL database. The website is using PHP. Data
fields are encoded so that html tags are using entities; i.e. p =
lt;pgt;
I can confirm we are having the same issue still with our geo coded
searches.
FWIW, the error is very similar to the one we got with non-geo
searches when we specified language (lang=en).
Just like the language search bug, you can get around this by putting
'since' in the url (since=2010-11-24)
