There isn't quite enough information in this email to provide a definitive answer. Providing a predicate list and an example of an unexpected match would be helpful in describing the Streaming API behavior.
Note that the predicates are logical ORs, so that any match will cause a delivery. These are not logical ANDs. So, if a user in your following file tweets without geodata, you'll get a tweet without geodata. The only known issues with track are around non-space-separated languages, such as Chinese, Japanese and, I think, Arabic, language representations. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Apr 27, 2010 at 6:17 AM, epomqo <wenzi0...@gmail.com> wrote: > Dear all, > > Good morning! I have been experiencing some problems when I was trying > to use streaming api to get filtered tweets, and I have no idea why > they happened :( > > Specifically I wanted to get tweets from specific users within > specified locations. I got some advices here and I proceeded > successfully with this command: > > curl -d @following -d @locations > http://stream.twitter.com/1/statuses/filter.json > -u > > The problem is that when I was checking the filtered results, there > are still quite a lot tweets appeared without geographical > information, and tweets from users that I didn't include in the > following list. So there seems some inaccuracy in this filtering > function. > > Any ideas or suggestions? Thanks! > > Best, > epomqo > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >