Well, they do have their ToS the law has so far placed in favor of usage of apps and apis regardless of ToS as long as it is "legal". Yet, due to massive litigation.

Best,

--------------
Edward H. Hotchkiss
http://www.edwardhotchkiss.com/
http://www.twitter.com/edwardhotchkiss/
--------------




On Nov 18, 2010, at 2:26 PM, Matthew Terenzio wrote:

We have every right in the world to gather this data for analysis without any permission. It's public. Redistributing it will be subject to fair use and copyright law but not gathering it and making broad analysis. That is what search engines do and so far the courts have said they have a right to cache copies on their own servers, not for public display necessarily, but in order to better analyze it. Oddly, the courts landed on the right side for once, saying that the greater good of the utility of search was a societal need and, in this case, more important than minor infringements, if any, on the site's copyrights.

On Wed, Nov 17, 2010 at 12:18 PM, Ryan Sarver <rsar...@twitter.com> wrote:
Companies have leveraged Twitter’s open API to analyze and report on
conversations and sentiment across the network since its inception.
These products have been indispensable in helping brands, marketers
and businesses engage with their customers on Twitter. This is an area
we want to support more fully, and today we are excited to announce a
partnership with Gnip to develop and market data products specifically
for these analysis and non-display companies. Gnip will sublicense
access to our public Tweets to developers interested in analyzing
large amounts of Twitter data.

Over the past year we have spoken with many companies and
entrepreneurs throughout the ecosystem who need easier access to more
data. In particular, companies building analysis and non-display
products have asked us for greater volume and coverage. Our
partnership with Gnip is built to address this need. Gnip will focus
exclusively on creating products to meet the existing and emerging
demands of companies creating non-display products. Check out Gnip’s
blog to learn more and to see details about their initial Twitter data
products: http://blog.gnip.com/gnip-twitter-partnership/.

Many of you may wonder what this means for elevated access and
whitelisting requests. Our default levels like Spritzer, Follow and
Track will not be changing, and will remain free and available
directly from Twitter. Companies and developers are encouraged to
begin development with these free APIs, available at
http://dev.twitter.com/pages/streaming_api. This does affect companies
wishing to create products which analyze Tweets and do not display
Tweets to end-users. Moving forward, we will begin to encourage these
companies needing elevated access for analysis and non-display
products to work with Gnip to find the right data products for their
commercial needs.

We’re excited about this partnership, and the support it offers the
data analysis and non-display market. You can learn more about the
details and Gnip by visiting http://gnip.com/twitter. Please let me
know if you have any questions about how this affects you and your
products.

To contact Gnip:
web: http://gnip.com
email: i...@gnip.com
twitter: http://twitter.com/gnip

Best, Ryan

--
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


--
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

--
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

<<inline: edward.png>>

Reply via email to