There is considerable inconsistency, ambiguity and change in these areas.
For example, we announced the 50mm tweets/day thing recently. This is
frustrating. We're working to rationalize all of this.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.


On Fri, Mar 12, 2010 at 10:42 AM, M. Edward (Ed) Borasky
<zzn...@gmail.com>wrote:

> Am I to assume then that those who comment on tweet volume in the "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
>
>
>
> Quoting John Kalucki <j...@twitter.com>:
>
>  5e is intended to cover publication of general statistics about the
>> streams,
>> such as Tweets per second, etc., not the display of Tweets themselves.
>>
>> The new Commercial License should be a lot clearer.
>>
>> -John Kalucki
>> http://twitter.com/jkalucki
>> Infrastructure, Twitter Inc.
>>
>>
>> On Thu, Mar 11, 2010 at 9:51 PM, Stephen Rife <stephenr...@gmail.com>
>> wrote:
>>
>>
>>> 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
>>>
>>>
>>
>

Reply via email to