Re: [twitter-dev] Re: Geocoded searches broken
This happened in my script too. Try to put since=2010-11-29 (today stamp) in your url request might solve the problem On Mon, Nov 29, 2010 at 6:56 AM, bob.hitching b...@hitching.net wrote: seeing the same problem on http://geome.me, for example - http://search.twitter.com/search.json?geocode=37.44452,-122.161304,7kmq=love Response includes: ... warning:adjusted since_id to 9031872674339840 due to temporary error ... thanks to Randy for the workaround. help us Twitter! On Nov 28, 10:41 am, MikeUCUD michaelmcca...@gmail.com wrote: I'm having the same issue. It worked again for a little while, but hasn't worked in a day or 2. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Regards, Judotens M. Budiarto, @judotens | 2557A0A2 http://judotens.com | http://dunialain.net -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Geocoded searches broken
Hi all, We're working to fix this issue as quickly as we can. Thanks for all the great examples. Taylor On Mon, Nov 29, 2010 at 1:11 AM, Judotens Budiarto judot...@gmail.comwrote: This happened in my script too. Try to put since=2010-11-29 (today stamp) in your url request might solve the problem On Mon, Nov 29, 2010 at 6:56 AM, bob.hitching b...@hitching.net wrote: seeing the same problem on http://geome.me, for example - http://search.twitter.com/search.json?geocode=37.44452,-122.161304,7kmq=love Response includes: ... warning:adjusted since_id to 9031872674339840 due to temporary error ... thanks to Randy for the workaround. help us Twitter! On Nov 28, 10:41 am, MikeUCUD michaelmcca...@gmail.com wrote: I'm having the same issue. It worked again for a little while, but hasn't worked in a day or 2. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Regards, Judotens M. Budiarto, @judotens | 2557A0A2 http://judotens.com | http://dunialain.net -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Geocoded searches broken
I'm having the same issue. It worked again for a little while, but hasn't worked in a day or 2. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Geocoded searches broken
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) Not sure why but this appears to be related to the snowflake change on Friday. At least that is when these seem to have broke. On Nov 26, 10:53 am, Mack D. Male master...@gmail.com wrote: Since yesterday, geocoded searches have been broken intermittently. Sometimes results are returned normally, then for stretches of time (30 minutes or more) no results are returned. During that time, there's a warning like the following: adjusted since_id to 8230615843933184 due to temporary error Here's a query that at this very moment (~11:55 AM) returns zero results:http://search.twitter.com/search?q=near:%22Edmonton,Alberta%22 It stopped working about an hour ago (~10:55 AM MST). Any information on this? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Geocoded searches broken
seeing the same problem on http://geome.me, for example - http://search.twitter.com/search.json?geocode=37.44452,-122.161304,7kmq=love Response includes: ... warning:adjusted since_id to 9031872674339840 due to temporary error ... thanks to Randy for the workaround. help us Twitter! On Nov 28, 10:41 am, MikeUCUD michaelmcca...@gmail.com wrote: I'm having the same issue. It worked again for a little while, but hasn't worked in a day or 2. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Geocoded searches broken
I can also confirm the same problem across multiple twitter clients. It also looks like any seaches including filter:links also return zero results. On Nov 27, 4:28 am, Hrishikesh Bakshi bakshi.hrishik...@gmail.com wrote: I am facing the same issue. I tried from different IP addresses just to make sure. I met more people on IRC with the same problem. I get the exact same warning each time. warning: adjusted since_id to 8376324073257984 due to temporary error On Fri, Nov 26, 2010 at 1:53 PM, Mack D. Male master...@gmail.com wrote: Since yesterday, geocoded searches have been broken intermittently. Sometimes results are returned normally, then for stretches of time (30 minutes or more) no results are returned. During that time, there's a warning like the following: adjusted since_id to 8230615843933184 due to temporary error Here's a query that at this very moment (~11:55 AM) returns zero results: http://search.twitter.com/search?q=near:%22Edmonton,Alberta%22 It stopped working about an hour ago (~10:55 AM MST). Any information on this? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
