I just did a quick search and the latest result was less then a minute old. Are you sure the lates result is actually lagged and not just old?
Also whitelisting will not help lag or really do anything on search.twitter.com. On Fri, May 8, 2009 at 10:14, Chad Etzel <jazzyc...@gmail.com> wrote: > > I will agree that the Search API can get laggy at times, but I've > never seen it 2 hours behind... > > The latest tweet with #ll containing a lat/lng corrd is this from > about 2.5 hours ago... > http://twitter.com/gmapsmania/status/1737161434 > > Have you tried more recently? Whenever possible, I recommend the > .json feed over the .atom feed, but that's just my preference. > Technically they should be identical (temporally speaking), but I have > an easier time with the format. > > -Chad > > On Fri, May 8, 2009 at 10:23 AM, vladocar <vlado...@gmail.com> wrote: > > > > Hi, > > > > I'm using this url for extracting Atom(xml) data: > > > > http://search.twitter.com/search.atom?q=%23ll&rpp=20 > > > > and with the same url I have 1-2 hour delay on my application > > > > http://www.allapis.com/Geo-Twitter-ll.aspx > > > > Why!? > > > > My application is all about fast geo tracking. > > > > I tryed to get "white list" permission from twitter, but they didn't > > respond me. > > > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
