The existing EULA has its confusing parts and is at the end of its life. The
Commercial License is much better conceived and is aligned with where
Twitter is going, and is not based on where we were 12+ months ago when the
EULA first was released.
On Sun, Apr 11, 2010 at 6:16 PM, M. Edward (Ed) Borasky
<zn...@comcast.net>wrote:
> There is also the issue of what we can do with the Sample and Filter
> endpoints regarding, for example, tweets per day or tweets per second.
> It's not all that difficult or inaccurate to multiply Sample
> ("Spritzer") tweet counts by 20. ;-) I think I'll post this one to the
> question list on Google Moderator.
>
> --
> M. Edward (Ed) Borasky
> http://borasky-research.net/m-edward-ed-borasky/ @znmeb
>
> "A mathematician is a device for turning coffee into theorems." ~ Paul
> Erdős
>
>
> On 04/11/2010 05:54 PM, Dewald Pretorius wrote:
> > Thanks for the quick response, John.
> >
> > The best will then be to wait for post-Chirp.
> >
> > As is, the current EULA could also be interpreted to prevent such
> > uses, and that kind of nebulous wording is no basis upon which to
> > expend any creative or development effort.
> >
> > On Apr 11, 9:20 pm, John Kalucki <j...@twitter.com> wrote:
> >> Both of those use cases are fine. The intent was to prevent people from
> >> publishing counts of Tweets per day or similar metrics. (I make no
> pretense
> >> at defending this intent, I'm the messenger.) Go forth and wordle.
> >>
> >> This EULA is near the end of its life and has been rewritten into the
> >> Commercial Data License, which Doug and Barkari will be discussing on
> day
> >> two of Chirp. If you have questions about how access under the EULA will
> >> evolve to access under the License, that would be a good place to start.
> >>
> >> -John Kaluckihttp://twitter.com/jkalucki
> >> Infrastructure, Twitter Inc.
> >>
> >>
> >>
> >> On Sun, Apr 11, 2010 at 4:22 PM, Dewald Pretorius <dpr...@gmail.com>
> wrote:
> >>> With reference to:
> >>> http://twitter.com/pdfs/streaming_api_eula.pdf
> >>
> >>> Section 5 (ii) (e):
> >>> "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."
> >>
> >>> Question:
> >>
> >>> Assumimg I build a website that uses the Streaming API, is my
> >>> interpretation correct that the following is against the TOS?
> >>
> >>> 1) Counting and displaying to the website users how many times the
> >>> word "earthquake" occurs in tweets over a certain period of time.
> >>
> >>> 2) Building and displaying to the website users a tag cloud of words/
> >>> phrases in tweets.- Hide quoted text -
> >>
> >> - Show quoted text -
> >
> >
>
>
> --
> M. Edward (Ed) Borasky
> borasky-research.net/m-edward-ed-borasky
>
> "A mathematician is a device for turning coffee into theorems." ~ Paul
> Erdős
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
>
