Hi everyone,

I have recently started building an application which uses the
Streaming API for fetching geolocated tweets from a given area defined
by a bounding box. The tweets are analyzed for extracting some
features based on their text and afterwards I store for each tweet the
features (actually identified topics), time and location (I don;t need
info about the user's identity).
I am wondering whether my approach contrasts with the Twitter's API
TOS and especially  the term "You will not attempt or encourage others
to use or access the Twitter API to aggregate, cache (except as part
of a Tweet), or store place and other geographic location information
contained in Twitter Content". I have encountered many sites that use
aggregated tweets' location information, and thus I am not quite sure
how this term should be applied.

Thanks in advance!

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to