Are the "various terms and agreements" that currently disallow this published anywhere?
After a brief look (perhaps I missed it) at: http://twitter.com/apirules http://twitter.com/tos http://help.twitter.com/forums/26257/entries/18311 As far as I can tell there isn't anything that explicitly disallows resyndicating or making "Twitter data available via an API". The TOS also states: "Tip: This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same." "Tip: We encourage and permit broad re-use of Content. The Twitter API exists to enable this." thanks On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki <j...@twitter.com> wrote: > Not at the moment, as we expect that the number of services that this will > apply to is small. We'll be clarifying data access and licensing over the > next few months. > > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > On Mon, Mar 8, 2010 at 9:57 PM, Abraham Williams <4bra...@gmail.com>wrote: > >> Is the specific set of requirements published anywhere? >> >> Abraham >> >> >> On Mon, Mar 8, 2010 at 06:50, John Kalucki <j...@twitter.com> wrote: >> >>> Your application description sounds like resyndication, which is not >>> allowed under various terms and agreements. You cannot make Twitter data >>> available via an API unless a very specific set of requirements are adhered >>> to. Contact a...@twitter.com to start this process. >>> >>> -John Kalucki >>> http://twitter.com/jkalucki >>> Infrastructure, Twitter Inc. >>> >>> >>> >>> On Mon, Mar 8, 2010 at 3:37 AM, Diz <sitov.crist...@gmail.com> wrote: >>> >>>> For the last 3 months I am experimenting the Search API. I'm focusing >>>> on the geo-location searching capabilities. >>>> >>>> For the beginning I started with my own city, but my intents are to >>>> extend to the major cities of my country: that will be at most ten. My >>>> idea of application is to offer real-time activity on each major city, >>>> through a proxy that caches all tweets and then serves them further to >>>> clients, filtered or non-filtered. Frequency of requests should be >>>> between 5 to 10 seconds, and that means I should do between 400 to 800 >>>> requests per hour just for one city, and probably between 4000 to 8000 >>>> requests for the whole application. >>>> >>>> My questions are: >>>> 1). Should I use Search API, or should I move to the Streaming API?! >>>> 2). To whom I should request whitelisting: the usual Search API or the >>>> Streaming API?! >>>> >>>> >>>> Thanks! >>>> >>> >>> >> >> >> -- >> Abraham Williams | Community Advocate | http://abrah.am >> TwitterOAuth | http://github.com/abraham/twitteroauth >> This email is: [ ] shareable [x] ask first [ ] private. >> > >
