Application based on Search API
Diz
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!
John Kalucki
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
Abraham Williams
Abraham Williams | Community Advocate | http://abrah.am
TwitterOAuth | http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.
John Kalucki
Will Fleming
Andrew Badera
http://twitter.com/pdfs/streaming_api_eula.pdf
... see Restrictions ...
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
Diz
generate an API! I also didn't specify anything about resyndicating
content.
I just want to offer real-time activity on a web interface, and beside
that analyze cached tweets to generate statistics.
Anyone, following me?!
On Mar 10, 12:33 am, Will Fleming <wflemin...@gmail.com> wrote:
> Are the "various terms and agreements" that currently disallow this
> published anywhere?
>
> After a brief look (perhaps I missed it) at:http://twitter.com/apiruleshttp://twitter.com/toshttp://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.
>
Andrew Badera
realtime. Maybe the Search API in a supplementary fashion ... is there
whitelisting for the Search API specifically?
--ab
Mark McBride
Stephen Rife
On 3月10日, 午後10:22, Andrew Badera <and...@badera.us> wrote:
> Not sure about the REST/Search API, but on the Streaming side:
>
> http://twitter.com/pdfs/streaming_api_eula.pdf
>
> ... see Restrictions ...
>
Reading the Content License Agreement for the streaming API I am
confused by how the granting of a license to publicly display the
content from the streams (1i. Content License) works with the
obligation to use only for internal purposes. What does "internal
purposes" mean here? Does the "unless expressly authorized herein"
part negate the restriction to not release the data publicly? Or this
just to prevent people from reselling the data?
---- from CLA start ------
1. Content License.
"Twitter grants you a nonexclusive, revocable
license to use the Content to: (i) use, reproduce, distribute,
transmit, publicly display and publicly perform the Content thereof,
solely on and through your Service. "
....
5. Your Obligations.
(e) User Data.
You may only use the Content and Content Feed and any data resulting
or provided therefrom for internal purposes only and, unless expressly
authorized herein, you may not publicly release or disclose any data
or usage statistics or other information (in the aggregate or
otherwise) regarding the Content. You agree to and will make
available to Twitter any data, usage statistics or
other information (in the aggregate) regarding the access and use of
the Content.
---- from CLA end ------
- Steve Rife
DIgital Garage
http://twitter.com/melobubu
John Kalucki
The new Commercial License should be a lot clearer.
M. Edward (Ed) Borasky
"trade press" by simply looking at status IDs as they go by, using the
*REST* API, are exempt from this? I keep running into blog posts by
"social media scientists" who are using status ID as a proxy for total
tweet volume - there's even a web site that just displays the status
ID counting up!
What about people who are using the publicly-available "sample" and
"filter" streams? Is it a violation of TOS to publish statistics
derived from those? I ask because I've actually done that - right here
on this list! If I'm not supposed to do that, I apologize. But it's
stuff that people are insanely curious about, both for business
reasons and for the sheer entertainment value of the "Twitter
phenomenon".
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos