The streaming API will be our method to provide access large sets of data moving forward. We are working on a method to automate the handling requests to /gardenhose at the moment which should be deployed shortly. There is an open issue [1] for public_timeline and datamining feed trouble, but as you can tell it is not a priority given that /spritzer has open access, has been rock solid, and gives more data than the 600 tweet per minute available with a working datamining feed. If you need data, we encourage you to start with /spritzer and move to /gardenhose when the click through agreement system is finished in the near future.
1. http://code.google.com/p/twitter-api/issues/detail?id=582 Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 22, 2009 at 10:30 AM, AJ Chen <[email protected]> wrote: > The data mining feed is not functional for several days, and it will be > phased out shortly according to Alex's email yesterday. The better > replacement is streaming API. > -aj > > > On Fri, May 22, 2009 at 5:45 AM, junki <[email protected]> wrote: > >> >> Hi, there. >> >> I've got a "The Data Mining Feed"'s right about 1 mouth ago. >> Since then, I could obtained 600 recent public statuses per a minute >> with my shell script. >> >> But last few days, I could get only 20 tweets. "20" is acquired by >> normal API-Method. >> Does it mean that I was banned by Twitter API Team? >> The acount allowed "The Data Mining Feed" is http://twitter.com/jonki_bot >> >> Thanks to your help. >> >> --- >> Junki OHMURA (http://twitter.com/jonki) >> > > > > -- > AJ Chen, PhD > Co-Chair, Semantic Web SIG, sdforum.org > Technical Architect, healthline.com > http://web2express.org > Palo Alto, CA >
