date:20101118

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

Re: [twitter-dev] URGENT: Advice on building the correct API stream

2010-11-18 Thread Neil Sheth

Hi Adam,

Thanks for your advice, just wanted to ask if you have a link to the
solution you mentioned for point 2 i.e. the Search API?

Regards
Neil

On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote:

 On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote:
  I have asked our developers to implement the statuses/filter API stream,
  however they have come back with the following:
 
  1) We will not be able to fetch previous tweets for the accounts because
  count parameter can not be used for default role (but can be used for
  increased access level roles e.g. Birddog, Shadow).

 If by previous tweets you mean tweets in the past, that is never
 available with the streaming API. Higher access levels won't give you
 older tweets either. For past tweets you need to use the search API.
 But the search API is rate limited, and it tends to fail if many
 search terms are used, so that is also limited. Frankly, past tweets
 are not available in large quantities with any portion of the API.

 
  2) Also, if streaming connections is closed (reason can be anything) than
 we
  will not be able to fetch the tweets for that connection closed period.
 So
  we do also need a monitoring job to monitor the daemon/backgroun process
  that fetch the tweets.
 Yes, you should always have a monitor running to verify that the
 streaming API collection process is still working. There are failures
 on the order of once a month or more in my experience. This is much
 better than in the past. These may crash your collection script.

 The answer is again the search API, which can be used to fill in the
 missing tweets lost during the failure, but the limitations mentioned
 above still apply.

 In general, if you are planning on capturing *all* tweets for a set of
 words or users, and *never* losing any, you are setting an impossible
 goal. Aiming for a very high level of accuracy is all you are going to
 achieve. With the right coding 99% or better is possible.

 
  Any help from anyone would be great
 
  Thanks
  Neil
 
  On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote:
 
  I'm using the streaming API to pull in tweets at that rate for several
  sites with no problem. The default access level gives you all the
  tweets for up to 5,000 users.
  http://dev.twitter.com/pages/streaming_api_methods#statuses-filter
 
  From my experience, if you create a useful site for this level of
  users, you can go back later with a much stronger argument for higher
  access later.
 
  If you are using PHP, I recommend Fenn Bailey's Phirehose library to
  manage the connection.
  http://code.google.com/p/phirehose/
 
  If you architect your tweet collection code so that all tweets are put
  into a normalized database, and the rest of the code only uses the
  database and not the API, you can easily change to a new type of API
  connection later. But if all you want now is tweets, the streaming API
  is good for now.
 
  On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com
 wrote:
   Great - thanks Tom.  For our site we will be pulling in quite few
   thousand
   tweets per hour.  Do you see any limitation with this API?
  
   On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote:
  
   Just wanted to chime in quickly. I've been using Site Streams in
   production for over a month now and have found them to be absolutely
   fantastic. Really rock solid. If Site Streams are indeed what you're
   looking
   for, I wouldn't let the beta tag scare you away.
  
   Taylor Singletary wrote:
  
   Hi Neil,
  
   What are you particularly trying to accomplish with your Twitter
   Integration? How are tweets used in the application? What APIs were
   you
   leveraging when you were planning a REST-only solution?
  
   While Site Streams is officially beta right now, it's very
 reliable
   --
   but whether it's the right solution for you really depends on what
   you're looking to accomplish.
  
   Thanks,
   Taylor
  
   On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com
   mailto:sheth.n...@gmail.com wrote:
  
  We have previously raised a request to obtain twitter
 whitelisting
   but
  have been told by Twitter (Brian) that we have built the wrong
  solution.  Our developers are struggling to understand which
   solution
  they need to build for our site www.mystweet.com
  http://www.mystweet.com in order to get
  whitelisted.  They have stated that they are unsure which one to
  choose:
  
  1) http://dev.twitter.com/pages/site_streams   - twitter
 recommend
  this for the kind of solution which we want to implement, but
 this
   is
  still in beta
  
  2) http://dev.twitter.com/pages/user_streams_suggestions  - but
   this
  is not what they would allow for our case.
  
  Can you please advise what solution needs to be built?  We're
   hoping
  to correct this before they go on their holidays
  
  Thanks
  
  
  PREVIOUS

[twitter-dev] Q : retrieve the following/followers list (for Obj-C)

2010-11-18 Thread Azzam Alsudais

Hi everyone,

I'm new to Twitter API, and currently working on my Graduation Project
for my Bs. in Computer Science..
My project is simply an iPhone app, and I need to integrate my app
with Twitter, so that I can retrieve the user's following/followers
lists

Any method or code to do that ?

Thanks in advance :)

-- 
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-dev] Number of favorites per tweet

2010-11-18 Thread Tijs

For a given tweet, I'd like to check the number of favorites.

I've been search for a solution and read through the API
documentation, yet it looks like there's no easy way to currently do
this, right? Anyone to suggest an alternative?

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

Re: [twitter-dev] URGENT: Advice on building the correct API stream

2010-11-18 Thread Adam Green

Neil:

If you mean a link to the Twitter doc on the search API, that is here:
http://dev.twitter.com/doc/get/search

I've also written a detailed comparison of the search API vs. the
streaming API that may help your coders pick the right solution:
http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/

If you wanted a solution to the specific issue of filling in missing
tweets with the search API, I don't know of an example that covers
exactly that, but the basic idea is:
- Collect tweets with the streaming API and the track parameter for
your keywords. Make the id_str of each tweet the primary key of the
table where they are stored.
- Monitor the created_at value for the most recent tweet added to the
database with a cron job that runs every five minutes or so. If tweets
arrive less frequently for your keywords, make this a longer interval.
- If the monitor script finds that no new tweets have been stored
within your test interval, it can use the search API to gather tweets
based on the same keywords. The search API returns up to 15 pages of
results in reverse date order, with up to 100 tweets per page. So even
tweets for active topics will still available from search.
- As tweets arrive from search, compare the id_str of the new tweets
with those in the database. Add the ones that aren't already there.
Your search code should stop making requests when you get to older
tweets you already have in the DB.

This basically gives you real-time tweets from the streaming API, and
automatic back filling for missed tweets with the search API.

I've probably exhausted the patience of others on this topic, so
contact me directly if you need more help: 140...@gmail.com

On Thu, Nov 18, 2010 at 3:05 PM, Neil Sheth sheth.n...@gmail.com wrote:
Hi Adam,

Thanks for your advice, just wanted to ask if you have a link to the
solution you mentioned for point 2 i.e. the Search API?

Regards
Neil

On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote:

On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote:
I have asked our developers to implement the statuses/filter API stream,
however they have come back with the following:

1) We will not be able to fetch previous tweets for the accounts because
count parameter can not be used for default role (but can be used for
increased access level roles e.g. Birddog, Shadow).

If by previous tweets you mean tweets in the past, that is never
available with the streaming API. Higher access levels won't give you
older tweets either. For past tweets you need to use the search API.
But the search API is rate limited, and it tends to fail if many
search terms are used, so that is also limited. Frankly, past tweets
are not available in large quantities with any portion of the API.

2) Also, if streaming connections is closed (reason can be anything)
than we
will not be able to fetch the tweets for that connection closed period.
So
we do also need a monitoring job to monitor the daemon/backgroun process
that fetch the tweets.
Yes, you should always have a monitor running to verify that the
streaming API collection process is still working. There are failures
on the order of once a month or more in my experience. This is much
better than in the past. These may crash your collection script.

The answer is again the search API, which can be used to fill in the
missing tweets lost during the failure, but the limitations mentioned
above still apply.

In general, if you are planning on capturing *all* tweets for a set of
words or users, and *never* losing any, you are setting an impossible
goal. Aiming for a very high level of accuracy is all you are going to
achieve. With the right coding 99% or better is possible.

Any help from anyone would be great

Thanks
Neil

On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote:

I'm using the streaming API to pull in tweets at that rate for several
sites with no problem. The default access level gives you all the
tweets for up to 5,000 users.
http://dev.twitter.com/pages/streaming_api_methods#statuses-filter

From my experience, if you create a useful site for this level of
users, you can go back later with a much stronger argument for higher
access later.

If you are using PHP, I recommend Fenn Bailey's Phirehose library to
manage the connection.
http://code.google.com/p/phirehose/

If you architect your tweet collection code so that all tweets are put
into a normalized database, and the rest of the code only uses the
database and not the API, you can easily change to a new type of API
connection later. But if all you want now is tweets, the streaming API
is good for now.

On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth sheth.n...@gmail.com
wrote:
Great - thanks Tom. For our site we will be pulling in quite few
thousand
tweets per hour. Do you see any limitation with this

[twitter-dev] Re: How do I find the URL of a Twitter user WWW page, having only their twitterID?

2010-11-18 Thread @Red_Eyes

Try this: http://twitter.com/?id=21358135 (That's my ID, BTW)

Regards



On Nov 18, 6:00 pm, Kaspa kacper.sul...@gmail.com wrote:
 The title says it all. Been looking for some time now.
 (I know I can lookup the API for user detail and then use that. That's
 not what I want, I want a way of directly putting the URL together)

 Are URLs that directly use userIDs in some way prohibited?

-- 
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-dev] Re: How do I find the URL of a Twitter user WWW page, having only their twitterID?

2010-11-18 Thread @Red_Eyes

You can do it, but you have to be logged in first which suggests that
this would be a rate limited lookup.

eg: http://twitter.com/?id=

Regards



On Nov 18, 6:00 pm, Kaspa kacper.sul...@gmail.com wrote:
 The title says it all. Been looking for some time now.
 (I know I can lookup the API for user detail and then use that. That's
 not what I want, I want a way of directly putting the URL together)

 Are URLs that directly use userIDs in some way prohibited?

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

Re: [twitter-dev] Re: How do I find the URL of a Twitter user WWW page, having only their twitterID?

2010-11-18 Thread Tom van der Woerdt

Doesn't seem to work with #newtwitter.

Tom


On 11/18/10 11:14 PM, @Red_Eyes wrote:
 You can do it, but you have to be logged in first which suggests that
 this would be a rate limited lookup.
 
 eg: http://twitter.com/?id=
 
 Regards
 
 
 
 On Nov 18, 6:00 pm, Kaspa kacper.sul...@gmail.com wrote:
 The title says it all. Been looking for some time now.
 (I know I can lookup the API for user detail and then use that. That's
 not what I want, I want a way of directly putting the URL together)

 Are URLs that directly use userIDs in some way prohibited?
 

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

Re: [twitter-dev] Re: How do I find the URL of a Twitter user WWW page, having only their twitterID?

2010-11-18 Thread Abraham Williams

Second tip:
http://blog.abrah.am/2010/04/little-known-twitter-and-twitterapi.html

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Thu, Nov 18, 2010 at 14:15, Tom van der Woerdt i...@tvdw.eu wrote:

 Doesn't seem to work with #newtwitter.

 Tom


 On 11/18/10 11:14 PM, @Red_Eyes wrote:
  You can do it, but you have to be logged in first which suggests that
  this would be a rate limited lookup.
 
  eg: http://twitter.com/?id=
 
  Regards
 
 
 
  On Nov 18, 6:00 pm, Kaspa kacper.sul...@gmail.com wrote:
  The title says it all. Been looking for some time now.
  (I know I can lookup the API for user detail and then use that. That's
  not what I want, I want a way of directly putting the URL together)
 
  Are URLs that directly use userIDs in some way prohibited?
 

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

Re: [twitter-dev] URGENT: Advice on building the correct API stream

2010-11-18 Thread Neil

This is great advice, many thanks.

Will keep your blog and personal email address in mind for the future

Sent from my iPhone

On 18 Nov 2010, at 21:56, Adam Green 140...@gmail.com wrote:

Neil:

If you mean a link to the Twitter doc on the search API, that is here:
http://dev.twitter.com/doc/get/search

This basically gives you real-time tweets from the streaming API, and
automatic back filling for missed tweets with the search API.

I've probably exhausted the patience of others on this topic, so
contact me directly if you need more help: 140...@gmail.com

On Thu, Nov 18, 2010 at 3:05 PM, Neil Sheth sheth.n...@gmail.com
wrote:

Hi Adam,

Thanks for your advice, just wanted to ask if you have a link to the
solution you mentioned for point 2 i.e. the Search API?

Regards
Neil

On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote:

On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth
sheth.n...@gmail.com wrote:
I have asked our developers to implement the statuses/filter API
stream,

however they have come back with the following:

1) We will not be able to fetch previous tweets for the accounts
because
count parameter can not be used for default role (but can be used
for

increased access level roles e.g. Birddog, Shadow).

If by previous tweets you mean tweets in the past, that is never
available with the streaming API. Higher access levels won't give
you

older tweets either. For past tweets you need to use the search API.
But the search API is rate limited, and it tends to fail if many
search terms are used, so that is also limited. Frankly, past tweets
are not available in large quantities with any portion of the API.

2) Also, if streaming connections is closed (reason can be
anything)

than we
will not be able to fetch the tweets for that connection closed
period.

So
we do also need a monitoring job to monitor the daemon/backgroun
process

that fetch the tweets.

Yes, you should always have a monitor running to verify that the
streaming API collection process is still working. There are
failures

on the order of once a month or more in my experience. This is much
better than in the past. These may crash your collection script.

The answer is again the search API, which can be used to fill in the
missing tweets lost during the failure, but the limitations
mentioned

above still apply.

In general, if you are planning on capturing *all* tweets for a
set of
words or users, and *never* losing any, you are setting an
impossible
goal. Aiming for a very high level of accuracy is all you are
going to

achieve. With the right coding 99% or better is possible.

Any help from anyone would be great

Thanks
Neil

On 16 November 2010 22:19, Adam Green 140...@gmail.com wrote:

I'm using the streaming API to pull in tweets at that rate for
several

sites with no problem. The default access level gives you all the
tweets for up to 5,000 users.
http://dev.twitter.com/pages/streaming_api_methods#statuses-filter

From my experience, if you create a useful site for this level of
users, you can go back later with a much stronger argument for
higher

access later.

If you are using PHP, I recommend Fenn Bailey's Phirehose
library to

manage the connection.
http://code.google.com/p/phirehose/

If you architect your tweet collection code so that all tweets
are put

into a normalized database, and the rest of the code only uses the
database and not the API, you can easily change to a new type of
API
connection later. But if all you want now is tweets, the
streaming API

is good for now.

On Tue, Nov 16, 2010 at 5:06 PM, Neil Sheth

Re: [twitter-dev] Enabling Geotagging to user tweet

2010-11-18 Thread Abraham Williams

You can send users directly to https://twitter.com/account/geo which is
mobile friendly.

http://blog.abrah.am/2010/04/little-known-twitter-and-twitterapi.html

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Thu, Nov 18, 2010 at 01:08, Francis Chong siu.y...@gmail.com wrote:

 We are developing an twitter app with geotagging.

 From the Twitter Geotagging API Best Practices
 http://twitter.com/account/settings/geo
 , we noted user can enable or disable geotagging from their account.
 If the setting is disabled, we should redirect user to geo setting
 page.

 The problem is when user try to open the page
 http://twitter.com/account/settings/geo
 (mobile geo setting URL), and if user has not login to twitter.com,
 they will be redirected to mobile.twitter.com.

 After user logged in, they are sent to their timeline. There are no
 way they can find the geo setting page there -- unless they try to
 enable the desktop version of the page and manually open the setting
 page, which is not very user friendy.

 Any hint how we can do to improve this issue? or is this a bug on
 twitter homepage that could be fixed?

 --
 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-dev] Re: xAuth request returns 401, need help

*bump*

I've run my base string through an oAuth verifier (http://quonos.nl/
oauthTester/), and it all checks out!

Any ideas?

On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:
 Hey all,

 This is my first post in this group, hi!

 I am having trouble making a request 
 onhttps://api.twitter.com/oauth/access_token.
 I've been at this for 2 days and I can't make any progress.  I feel
 like everything matches up with all examples, documentation, and other
 forum posts perfectly.

 Here is my post body:

 x_auth_username=oauth_test_execx_auth_password=twitter-
 xauthx_auth_mode=client_auth

 Here is my base string (using the example's test credentials):

 POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
 %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
 %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
 %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
 %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
 %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

 Here is my Authorization header:

 OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
 F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
 oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
 oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
 %2F2QQvtbelsWk48%3D

-- 
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-dev] Re: Twitter + Gnip Partnership

2010-11-18 Thread Scott J

I would like to know the answer to this as well.  What will the limits
be on the statuses/filter?

On Nov 17, 9:44 am, Dewald Pretorius dpr...@gmail.com wrote:
 Ryan,

 The Gnip blog post states:

 [QUOTE]Twitter Decahose. This volume-based product is comprised of 10%
 of the full firehose. Starting today, developers who want to access
 this sample rate will access it via Gnip instead of Twitter. Twitter
 will also begin to transition non-display developers with existing
 Twitter Gardenhose access over to Gnip.[/QUOTE]

 How does this affect the basic statuses/sample method of the Streaming
 API? Are you discontinuing it? If so, when?

-- 
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-dev] Re: xAuth request returns 401, need help

2010-11-18 Thread themattharris

Hey Chrys,

A couple of things to check first:

1. Have you been granted xAuth access?
2. Double check the timestamp of your request is within 10 or so
minutes of the time returned by Twitter's servers. Our server time is
in UTC.
3. Verify your encoding is correct. For example: a password like ab$
%123 should be in your basestring as ab%2524%2525%2526123 and in your
post body as ab%24%25%26123.

Best,
Matt

On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:
 *bump*

 I've run my base string through an oAuth verifier (http://quonos.nl/
 oauthTester/), and it all checks out!

 Any ideas?

 On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:







  Hey all,

  This is my first post in this group, hi!

  I am having trouble making a request 
  onhttps://api.twitter.com/oauth/access_token.
  I've been at this for 2 days and I can't make any progress.  I feel
  like everything matches up with all examples, documentation, and other
  forum posts perfectly.

  Here is my post body:

  x_auth_username=oauth_test_execx_auth_password=twitter-
  xauthx_auth_mode=client_auth

  Here is my base string (using the example's test credentials):

  POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
  %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
  %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
  %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
  %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
  %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

  Here is my Authorization header:

  OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
  F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
  oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
  oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
  %2F2QQvtbelsWk48%3D

-- 
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-dev] Re: xAuth request returns 401, need help

1. Yes
2. Interesting point. I'm probably not sending a UTC timestamp!
3. We take care of this

Thanks! I'm going to play with the timstamp.

On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
 Hey Chrys,

 A couple of things to check first:

 1. Have you been granted xAuth access?
 2. Double check the timestamp of your request is within 10 or so
 minutes of the time returned by Twitter's servers. Our server time is
 in UTC.
 3. Verify your encoding is correct. For example: a password like ab$
 %123 should be in your basestring as ab%2524%2525%2526123 and in your
 post body as ab%24%25%26123.

 Best,
 Matt

 On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:







  *bump*

  I've run my base string through an oAuth verifier (http://quonos.nl/
  oauthTester/), and it all checks out!

  Any ideas?

  On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:

   Hey all,

   This is my first post in this group, hi!

   I am having trouble making a request 
   onhttps://api.twitter.com/oauth/access_token.
   I've been at this for 2 days and I can't make any progress.  I feel
   like everything matches up with all examples, documentation, and other
   forum posts perfectly.

   Here is my post body:

   x_auth_username=oauth_test_execx_auth_password=twitter-
   xauthx_auth_mode=client_auth

   Here is my base string (using the example's test credentials):

   POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
   %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
   %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
   %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
   %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
   %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

   Here is my Authorization header:

   OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
   F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
   oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
   oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
   %2F2QQvtbelsWk48%3D

-- 
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-dev] Re: xAuth request returns 401, need help

Ok, I looked into it.  According to the iPhone SDK documentation, I am
indeed sending the UTC (GMT) timestamp.

Still not sure what else could be wrong?

Is this the right Content-Type?

Content-Type = application/x-www-form-urlencoded; charset=utf-8;

On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
 Hey Chrys,

 A couple of things to check first:

 1. Have you been granted xAuth access?
 2. Double check the timestamp of your request is within 10 or so
 minutes of the time returned by Twitter's servers. Our server time is
 in UTC.
 3. Verify your encoding is correct. For example: a password like ab$
 %123 should be in your basestring as ab%2524%2525%2526123 and in your
 post body as ab%24%25%26123.

 Best,
 Matt

 On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:







  *bump*

  I've run my base string through an oAuth verifier (http://quonos.nl/
  oauthTester/), and it all checks out!

  Any ideas?

  On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:

   Hey all,

   This is my first post in this group, hi!

   I am having trouble making a request 
   onhttps://api.twitter.com/oauth/access_token.
   I've been at this for 2 days and I can't make any progress.  I feel
   like everything matches up with all examples, documentation, and other
   forum posts perfectly.

   Here is my post body:

   x_auth_username=oauth_test_execx_auth_password=twitter-
   xauthx_auth_mode=client_auth

   Here is my base string (using the example's test credentials):

   POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
   %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
   %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
   %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
   %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
   %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

   Here is my Authorization header:

   OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
   F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
   oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
   oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
   %2F2QQvtbelsWk48%3D

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

Re: [twitter-dev] Re: xAuth request returns 401, need help

2010-11-18 Thread Matt Harris

OK, but is the UTC timestamp actually accurate? we've heard of a number of
phones whose date/time are wildly wrong. It maybe find but it's quite
common.

Your content-type is fine.
Matt


On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader chr...@gmail.com wrote:

 Ok, I looked into it.  According to the iPhone SDK documentation, I am
 indeed sending the UTC (GMT) timestamp.

 Still not sure what else could be wrong?

 Is this the right Content-Type?

 Content-Type = application/x-www-form-urlencoded; charset=utf-8;

 On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
  Hey Chrys,
 
  A couple of things to check first:
 
  1. Have you been granted xAuth access?
  2. Double check the timestamp of your request is within 10 or so
  minutes of the time returned by Twitter's servers. Our server time is
  in UTC.
  3. Verify your encoding is correct. For example: a password like ab$
  %123 should be in your basestring as ab%2524%2525%2526123 and in your
  post body as ab%24%25%26123.
 
  Best,
  Matt
 
  On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:
 
 
 
 
 
 
 
   *bump*
 
   I've run my base string through an oAuth verifier (http://quonos.nl/
   oauthTester/), and it all checks out!
 
   Any ideas?
 
   On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:
 
Hey all,
 
This is my first post in this group, hi!
 
I am having trouble making a request onhttps://
 api.twitter.com/oauth/access_token.
I've been at this for 2 days and I can't make any progress.  I feel
like everything matches up with all examples, documentation, and
 other
forum posts perfectly.
 
Here is my post body:
 
x_auth_username=oauth_test_execx_auth_password=twitter-
xauthx_auth_mode=client_auth
 
Here is my base string (using the example's test credentials):
 
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
%26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
   
 %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec
 
Here is my Authorization header:
 
OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
%2F2QQvtbelsWk48%3D

 --
 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-dev] Re: xAuth request returns 401, need help

Yes I compared the UTC timestamp that my phone is generating with the
actual UTC timestamp, and they were the same.

Is there anything else I can show you for more information?

No matter what, I just keep getting a 401 response from Twitter.

On Nov 18, 6:41 pm, Matt Harris thematthar...@twitter.com wrote:
 OK, but is the UTC timestamp actually accurate? we've heard of a number of
 phones whose date/time are wildly wrong. It maybe find but it's quite
 common.

 Your content-type is fine.
 Matt







 On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader chr...@gmail.com wrote:
  Ok, I looked into it.  According to the iPhone SDK documentation, I am
  indeed sending the UTC (GMT) timestamp.

  Still not sure what else could be wrong?

  Is this the right Content-Type?

  Content-Type = application/x-www-form-urlencoded; charset=utf-8;

  On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
   Hey Chrys,

   A couple of things to check first:

   1. Have you been granted xAuth access?
   2. Double check the timestamp of your request is within 10 or so
   minutes of the time returned by Twitter's servers. Our server time is
   in UTC.
   3. Verify your encoding is correct. For example: a password like ab$
   %123 should be in your basestring as ab%2524%2525%2526123 and in your
   post body as ab%24%25%26123.

   Best,
   Matt

   On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:

*bump*

I've run my base string through an oAuth verifier (http://quonos.nl/
oauthTester/), and it all checks out!

Any ideas?

On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:

 Hey all,

 This is my first post in this group, hi!

 I am having trouble making a request onhttps://
  api.twitter.com/oauth/access_token.
 I've been at this for 2 days and I can't make any progress.  I feel
 like everything matches up with all examples, documentation, and
  other
 forum posts perfectly.

 Here is my post body:

 x_auth_username=oauth_test_execx_auth_password=twitter-
 xauthx_auth_mode=client_auth

 Here is my base string (using the example's test credentials):

 POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
 %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
 %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
 %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
 %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth

  %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

 Here is my Authorization header:

 OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
 F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
 oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
 oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
 %2F2QQvtbelsWk48%3D

  --
  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-dev] Re: xAuth request returns 401, need help

Does the order of the params in either the Authorization or Base
string matter?

Here are my Request Headers:

Authorization = OAuth oauth_timestamp=\1290134876\, oauth_nonce=
\D3EC42D2-A37F-4298-987D-0F9603B0C9C7\, oauth_version=\1.0\,
oauth_consumer_key=\xxx\, oauth_signature_method=\HMAC-SHA1\,
oauth_signature=\MOWT%2BaSs35RhzvRRMVxRG0Y5p0E%3D\;
Content-Length = 71;
Content-Type = application/x-www-form-urlencoded;
charset=utf-8;

Here is my actual base string:

POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3Dxxx%26oauth_nonce%3DD3EC42D2-
A37F-4298-987D-0F9603B0C9C7%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1290134876%26oauth_version%3D1.0%26x_auth_mode
%3Dclient_auth%26x_auth_password%3Dxxx%26x_auth_username%3Dchrysb

On Nov 18, 6:47 pm, Chrys Bader chr...@gmail.com wrote:
 Yes I compared the UTC timestamp that my phone is generating with the
 actual UTC timestamp, and they were the same.

 Is there anything else I can show you for more information?

 No matter what, I just keep getting a 401 response from Twitter.

 On Nov 18, 6:41 pm, Matt Harris thematthar...@twitter.com wrote:







  OK, but is the UTC timestamp actually accurate? we've heard of a number of
  phones whose date/time are wildly wrong. It maybe find but it's quite
  common.

  Your content-type is fine.
  Matt

  On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader chr...@gmail.com wrote:
   Ok, I looked into it.  According to the iPhone SDK documentation, I am
   indeed sending the UTC (GMT) timestamp.

   Still not sure what else could be wrong?

   Is this the right Content-Type?

   Content-Type = application/x-www-form-urlencoded; charset=utf-8;

   On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
Hey Chrys,

A couple of things to check first:

1. Have you been granted xAuth access?
2. Double check the timestamp of your request is within 10 or so
minutes of the time returned by Twitter's servers. Our server time is
in UTC.
3. Verify your encoding is correct. For example: a password like ab$
%123 should be in your basestring as ab%2524%2525%2526123 and in your
post body as ab%24%25%26123.

Best,
Matt

On Nov 18, 5:31 pm, Chrys Bader chr...@gmail.com wrote:

 *bump*

 I've run my base string through an oAuth verifier (http://quonos.nl/
 oauthTester/), and it all checks out!

 Any ideas?

 On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:

  Hey all,

  This is my first post in this group, hi!

  I am having trouble making a request onhttps://
   api.twitter.com/oauth/access_token.
  I've been at this for 2 days and I can't make any progress.  I feel
  like everything matches up with all examples, documentation, and
   other
  forum posts perfectly.

  Here is my post body:

  x_auth_username=oauth_test_execx_auth_password=twitter-
  xauthx_auth_mode=client_auth

  Here is my base string (using the example's test credentials):

  POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
  %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
  %26oauth_nonce%3DE0E37C06-F12A-407B-8D80-20C78FF6183A
  %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
  %3D1288223176%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth

   %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec

  Here is my Authorization header:

  OAuth oauth_timestamp=1288223176, oauth_nonce=E0E37C06-
  F12A-407B-8D80-20C78FF6183A, oauth_version=1.0,
  oauth_consumer_key=JvyS7DO2qd6NNTsXJ4E7zA,
  oauth_signature_method=HMAC-SHA1, oauth_signature=IwPFrvb0PExyS
  %2F2QQvtbelsWk48%3D

   --
   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-dev] Re: Number of favorites per tweet

I was after this same thing a few weeks ago and was told there is no
way to get this information from the official Twr. API as of now...

But somehow twitfave does this.

And they have an API:
http://twitfave.com/home/about/api

The portion you need is in getting information about a single tweet
- you need to parse faved_by and count.

===
Mohan Arun
www.mohanarun.com

-- 
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-dev] Re: Twitter + Gnip Partnership

We have every right in the world to gather this data for analysis
without
any permission. It's public.

No.

You don't get to compile posts from a discussion forum into a
product, under the idea that such posts are public domain.
They are not. - Unless you own the forum or have a deal with the
forum owner,
and you stated in the TOS
that all posts made in the forum can be repackaged commercially
and only you have the right to do that.

I am not saying this on my own, this is from one of the newsletters I
receive,
which covered this exact same topic, I would be happy to share the
relevant
text of the newsletter if someone is interested ...

- - -
Mohan Arun
www.mohanarun.com


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

Re: [twitter-dev] Re: Twitter + Gnip Partnership

I don't care what your newsletter says. I'm talking about American law.

On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote:

 We have every right in the world to gather this data for analysis
 without
 any permission. It's public.

 No.

 You don't get to compile posts from a discussion forum into a
 product, under the idea that such posts are public domain.
 They are not. - Unless you own the forum or have a deal with the
 forum owner,
 and you stated in the TOS
 that all posts made in the forum can be repackaged commercially
 and only you have the right to do that.

 I am not saying this on my own, this is from one of the newsletters I
 receive,
 which covered this exact same topic, I would be happy to share the
 relevant
 text of the newsletter if someone is interested ...

 - - -
 Mohan Arun
 www.mohanarun.com


 --
 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-dev] Re: Regarding using twitter api or twitter stuffs in my website

You dont need api for this.

Just grab profile widget frm here and embed the code in your site.

http://twitter.com/about/resources/widgets

Mohan Arun L.

-- 
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-dev] Re: geocode question

Many people have done something similar - plotting tweets on a map.

http://twitdom.com/twittermap-2/
www.trendsmap.com

how to do this code-wise? It must be in the API.

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

Re: [twitter-dev] Twitter + Gnip Partnership

2010-11-18 Thread Edward Hotchkiss

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

Re: [twitter-dev] Re: Twitter + Gnip Partnership

Just to clarify. I never said they were Public Domain. Twitter or the user
own the copyrights. Probably both. I meant it has been made public
information, thereby granting some rights to those it was made public to. I
wouldn't have a right to redistribute a book written by you, but I have
every right to quote it in an article I write about you.
More importantly, I can read 1000 books by 1000 different people and then
write a paper that says 50% of the books written contained the word 'Obama'
and  and the average amount of times Obama was used in a book was 14.
I wouldn't be breaking any laws.
But who cares.
In the future, if you want to access the Twitter data for such usage with
any sort of speed you will pay to do so. It won't even be worth the headache
if you can devise an alternative.

On Thu, Nov 18, 2010 at 11:35 PM, Matthew Terenzio mteren...@gmail.comwrote:

 I don't care what your newsletter says. I'm talking about American law.


 On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote:

 We have every right in the world to gather this data for analysis
 without
 any permission. It's public.

 No.

 You don't get to compile posts from a discussion forum into a
 product, under the idea that such posts are public domain.
 They are not. - Unless you own the forum or have a deal with the
 forum owner,
 and you stated in the TOS
 that all posts made in the forum can be repackaged commercially
 and only you have the right to do that.

 I am not saying this on my own, this is from one of the newsletters I
 receive,
 which covered this exact same topic, I would be happy to share the
 relevant
 text of the newsletter if someone is interested ...

 - - -
 Mohan Arun
 www.mohanarun.com


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

Re: [twitter-dev] Re: Number of favorites per tweet

2010-11-18 Thread Edward Hotchkiss

I personally from one machine have most of Twitter in the past 2  
months indexed. Yes it's possible. The Twitter Advocates who are  
dickheads [yeah you guys] suspended all of my apps but one [luckily I  
don't use my personal account of course for my work when I mentioned  
methods for this].


ToS vs. The Law. It's a huge question.

Best,

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





On Nov 18, 2010, at 10:54 PM, L. Mohan Arun wrote:


I was after this same thing a few weeks ago and was told there is no
way to get this information from the official Twr. API as of now...

But somehow twitfave does this.

And they have an API:
http://twitfave.com/home/about/api

The portion you need is in getting information about a single tweet
- you need to parse faved_by and count.

===
Mohan Arun
www.mohanarun.com

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

Re: [twitter-dev] Twitter + Gnip Partnership