me too. I’m making data visualisations of the global origin of tweets on a given topic over a period of time, using the Twitter streaming API, node.js, socket.io and Google Maps. It works, but seems a great waste of bandwidth, as my options are:
- get all tweets with a global location range, then filter the text content on my search term.
- get all tweets for the term (track), then filter out those with a location.
In both cases, the vast majority are discarded, and amount to a huge amount of data being streamed.
so I’d love to be able to give location and track, and only get tweets that match both. this seems a better option to me than the current behaviour. does anyone know if there are plans to change this?