I am a bit concerned. I remember at one point it being between 30-45 days. Now it seems to be getting smaller by about 1-day per month. Last month it was closer to 10 days.
Is it basically going to keep getting smaller and smaller until we get V2 of the API, or will we be forced to all use only streaming services and then locally cache everything that we'd want to search for any time period? I know there are a LOT of problems inherent in the massive scaling out of Twitter, and this is just a symptom of them- but at the same time I can only imagine how unusable Google would be if you only had a 7-day window to Search in, and couldn't get any content made prior to that. Very worried about this soon being a 2-3 day window. dave On Jul 26, 4:11 am, Flashing Moose <flashingmo...@gmail.com> wrote: > Hmm, then i can't use the API for this project, thx for replies guys. > > On 26 jul, 04:10, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > > I believe the tweet retention in Twitter Search has always been 7 > > days. > > > On Jul 25, 1:18 pm, Flashing Moose <flashingmo...@gmail.com> wrote: > > > > Hello, having some trouble with the API because only the messages from > > > the last 7 days show up: > > > > example: > > > feed://search.twitter.com/search.atom?q=from%3AstimulusHome > > > > Yes, there must be older posts in there... but how do i get to them? > > > > I read about the Operator Limits: > > > filter:links operator: > > > results are limited to 7 days > > > source: operator: > > > results are limited to 7 days > > > queries must contain at least one keyword parameter with the source: > > > operator > > > lang= operator: > > > results are limited to 7 days > > > location operator: > > > results are limited to 7 days > > > > but i'm not using filter, source, language or location do i? > > > > regards, Moose
