[twitter-dev] basic authentication not supported error
hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- 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] About http response:Failed to validate oauth signature and token in India
Dears, We found a log-in problem ONLY happened in India. We implemented a mediatek widget and use xAuth for authentication. The testers in India try to log in Twitter, however, sometimes they cannot log in and receive a http response below: Failed to validate oauth signature and token Would you mind helping us to resolve this issue? Thanks! Sincerely, Cathy -- 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] how to get the ammount of a hashtag I started?
Hi: I have a blog and I want to start some hashtags. my idea is to set the hashtag winner through the number of times this hashtag has being used. I tried with the search query http://search.twitter.com/search.atom?q=#myhashtag but it does not return the total counter. How can I get it? Thanks so much -- 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] About http response:Failed to validate oauth signature and token in India
Just a guess: could it be related to using non-ASCII characters that get encoded improperly? Tom On 2/10/11 8:09 AM, Cathy Yeh wrote: Dears, We found a log-in problem ONLY happened in India. We implemented a mediatek widget and use xAuth for authentication. The testers in India try to log in Twitter, however, sometimes they cannot log in and receive a http response below: Failed to validate oauth signature and token Would you mind helping us to resolve this issue? Thanks! Sincerely, Cathy -- 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] basic authentication not supported error
Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- 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 -- *What I have is not a dream, because I will make it a reality.* -- 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] basic authentication not supported error
As Paresh mentioned, Your URL needs to be: a) pointed to the *api* subdomain b) versioned -- always *1* at this time c) specifying a format - usually either *json* or *xml* And should use: a) the screen_name parameter instead of an interpolated URI element to avoid issues with all-integer screen names. * * In your case you want to issue a GET to this URL instead: * http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=shanebond1982 * * * Taylor * * @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 3:30 AM, Paresh Nakhe paresh.na...@gmail.comwrote: Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- 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 -- *What I have is not a dream, because I will make it a reality.* -- 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: basic authentication not supported error
hi taylor and paresh i am creating a slideshow of 40 users recent tweet one after another in flash now some of them show when i ctrl enter and some of them dont some of this give me this error errors error code=53Basic authentication is not supported/error /errors im using this code loadTwitterXML(http://api.twitter.com/1/statuses/user_timeline.xml? screen_name=+listArr[twitcount]); how to use oauth to show usertimeline thanks On Feb 10, 8:09 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: As Paresh mentioned, Your URL needs to be: a) pointed to the *api* subdomain b) versioned -- always *1* at this time c) specifying a format - usually either *json* or *xml* And should use: a) the screen_name parameter instead of an interpolated URI element to avoid issues with all-integer screen names. * * In your case you want to issue a GET to this URL instead: *http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=shane... * * * Taylor * * @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 3:30 AM, Paresh Nakhe paresh.na...@gmail.comwrote: Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- 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 -- *What I have is not a dream, because I will make it a reality.* -- 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] posting status
Is there an easy way of posting tweets from a desktop client without using any external library? -- 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: Intermittent 401 errors calling access_token
I'm seeing intermittent issues as well on the /oauth/access_token endpoint. Have you ever gotten to the bottom of this or is it just best to handle the error and retry? Below is a capture of my HTTP requests: POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_signature=Thb80hXw6LKjiz1h8MFrNewp0KQ%3D, oauth_version=1.0, oauth_nonce=1474364130, oauth_signature_method=HMAC-SHA1, oauth_consumer_key=..., oauth_token=F2nCVegyxBKNa3TwjsoHolet5Env6ZvzV37xhQkmM, oauth_verifier=REGEX_FAILED, oauth_timestamp=1297355206 User-Agent: Java/1.6.0_22 Host: api.twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-type: application/x-www-form-urlencoded Content-Length: 0 HTTP/1.1 401 Unauthorized Date: Thu, 10 Feb 2011 16:26:46 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1297355206-55942-36174 Last-Modified: Thu, 10 Feb 2011 16:26:46 GMT X-Runtime: 0.00838 Content-Type: text/html; charset=utf-8 Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Set-Cookie: k=64.134.151.133.1297355206199446; path=/; expires=Thu, 17-Feb-11 16:26:46 GMT; domain=.twitter.com Set-Cookie: guest_id=129735520622032993; path=/; expires=Sat, 12 Mar 2011 16:26:46 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCE5uZRAuAToHaWQiJTUxZDA2OTQxYjBjYTM2%250AZjg2YzQwOGM2MjgxOWM0MjRkIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--35de5076b33181311e1eec89909ae50eb393d70f; domain=.twitter.com; path=/; HttpOnly Vary: Accept-Encoding Connection: close -- 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: Intermittent 401 errors calling access_token
Hi Peter, Curious if the oauth_verifier=REGEX_FAILED in your authorization header here is the actual value you sent or some kind of post-obfuscation you've made? If it's the actual value you sent, I'd take a look at the execution path that might cause that. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 8:40 AM, Peter Motyka pmot...@gmail.com wrote: I'm seeing intermittent issues as well on the /oauth/access_token endpoint. Have you ever gotten to the bottom of this or is it just best to handle the error and retry? Below is a capture of my HTTP requests: POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_signature=Thb80hXw6LKjiz1h8MFrNewp0KQ%3D, oauth_version=1.0, oauth_nonce=1474364130, oauth_signature_method=HMAC-SHA1, oauth_consumer_key=..., oauth_token=F2nCVegyxBKNa3TwjsoHolet5Env6ZvzV37xhQkmM, oauth_verifier=REGEX_FAILED, oauth_timestamp=1297355206 User-Agent: Java/1.6.0_22 Host: api.twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-type: application/x-www-form-urlencoded Content-Length: 0 HTTP/1.1 401 Unauthorized Date: Thu, 10 Feb 2011 16:26:46 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1297355206-55942-36174 Last-Modified: Thu, 10 Feb 2011 16:26:46 GMT X-Runtime: 0.00838 Content-Type: text/html; charset=utf-8 Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Set-Cookie: k=64.134.151.133.1297355206199446; path=/; expires=Thu, 17-Feb-11 16:26:46 GMT; domain=.twitter.com Set-Cookie: guest_id=129735520622032993; path=/; expires=Sat, 12 Mar 2011 16:26:46 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCE5uZRAuAToHaWQiJTUxZDA2OTQxYjBjYTM2%250AZjg2YzQwOGM2MjgxOWM0MjRkIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--35de5076b33181311e1eec89909ae50eb393d70f; domain=.twitter.com; path=/; HttpOnly Vary: Accept-Encoding Connection: close -- 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: Streaming API maintenance: brief delivery pause and an increased likelihood for duplicate tweets
Yesterday's maintenance resulted in about of 5 seconds of latency on Tweets, and about 10% of social events were delayed by about 10 minutes. No data was lost. We're going to perform another maintenance on social events now. You may experience duplicate social events for several seconds up to about two minutes. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Feb 9, 2011 at 1:15 PM, John Kalucki j...@twitter.com wrote: We are performing a maintenance activity shortly that will increase the likelihood of duplicate tweets and other messages on all Streaming APIs: User Streams, Site Streams, and stream.twitter.com. There may also be a brief pause in delivery. No tweets or other messages will be lost during this maintenance event. The maintenance window is predicted to be approximately 2 minutes long and may occur between 1:15pm PST / 21:15 UTC and 3:30pm PST / 23:15 UTC. Note that this possibility of duplications has always been documented on the Streaming API at: http://dev.twitter.com/pages/streaming_api_concepts#quality-of-service. -John Kalucki Twitter, Inc. http://twitter.com/jkalucki -- 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] Update on Whitelisting
Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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] Update on Whitelisting
Well I guess this old blog article is irevs now: How Twitter Dropped The Ball on Whitelisting Apps: If you've been wondering about whitelisting and why your app never got Approved [or Denied] then read on. Several weeks ago I posted a ticket per Twitter ordinance on getting a registered Twitter App Whitelisted. The app was for helping users manage their lists and use an intuitive drag and drop interface. To get the data for lists we only receive 20 users on a list of up to 500 twitter users [20 lists per user]. So I needed to be whitelisted to go to product launch. The benefits include but are not limited to an increase from 350 REST calls to 20,000 per hour. Realistically a lot of apps are requesting a lot of data, and 350 calls per hour just does not cut it. See just how much Twitter cares about their developers, the very people that Drive traffic and make it what it is today. A singularity. A massive ecosystem of it?s own. And it's all powered by Apps. While I waited patiently, this message thread popped up on the official TwitterAPI List. You need to read it all to get it in context. This is about a week old. How often should you send a request to be whitelisted? I am finding that in the span of time while I?m waiting for an answer, the nature of my project has changed drastically. So I then resend a request. Does this affect whether you will be whitelisted or not? And should I wait for a rejection before rerequesting in the future? Thank you, - Cassie Hi Cassie, We're almost always behind in processing whitelisting requests. Due to volume, we can't respond to all requests. If the nature of your project has changed, you should feel free to re-apply ? even if you were already granted whitelisted status, as the nature of a project is certainly taken into account in the decision making process. Feel free to follow up with me privately at list with the username you?ve filed a whitelisting request under for expanded discussion. Thanks, Taylor [Taylor Singletary, @episod] We're almost always behind in processing whitelisting requests. Due to volume, we can't respond to all requests? Really? Is not responding at all to whitelisting requests an official policy? If you mean you can't respond quickly, that makes sense. If you mean you can't approve all requests, I agree. But is no response at all a smart, polite, or even efficient way to deal with requests from developers? It seems like a guaranteed way to create discouraged developers. I know you try hard to be responsive, Taylor, and the fact that you will discuss this off-list proves this. So I'm guessing this is a policy you are just repeating. Maybe you can go back to management and point out the flaws in this approach? If a decision is made to deny a whitelist request, and at least a few minutes are spent on that decision, wouldn't it make more sense to reply with a denial? Otherwise the developer is left to repeat the request, which must use up more time for Twitter HQ than sending a denial in the first place. Repeated requests with no response leaves the developer with the opinion that Twitter doesn't want a third-party ecosystem, which clearly isn't the case. It also fills this list with messages from annoyed developers, which doesn't send a good message to new developers. Why can't someone reply with Sorry, we can't approve this request right now due to insufficient resources, but we appreciate your interest in Twitter development. Please try again in the future, as we may have more resources available at that time How many seconds does it take to send this type of email? [Adam] Hi Adam, The lack of response to some requests is due more to them going unread than being explicitly denied. I make a best effort to keep up with the volume of requests and approve or deny each that I process (balanced with my other responsibilities). These produce an email response. To be honest, the volume of requests is so high that we have to take a divide conquer approach, processing recent and dated requests alike. Obviously, this is suboptimal, which is why I welcome direct inquiries to help focus attention. I can't really disclose the volume of requests, but it is more than you probably imagine and the vast majority of them are not actionable due to an insufficient amount of information. We're actively working on a better model for whitelisting as a concept execution, as well as providing a more actionable funnel to ensure that the current situation of developers falling through the cracks is minified. Taylor [@episod] This is a reasonable response, and I'm not trying to give you personally a hard time. I'm hoping that Dick, Ev, Ryan, and other managers will see this and realize that they are turning away developers by not devoting enough resources to this issue. I'm sure if they were asked, they?d say they devote huge resources to developers, which
[twitter-dev] Re: Search API intermittently returning invalid results
We're seeing the exact same problem in our application. We happen to be using the Twitter ruby gem, but we are experiencing the same behavior. -Ryan On Feb 9, 3:22 pm, chouck cho...@gnipcentral.com wrote: I've been using curl to access search.twitter.com and recently I've noticed that occasionally it is returning invalid tweets. I'm searching for a query-term that shows up very infrequently in the tweet stream, and am using the curl command: curl http://search.twitter.com/search.atom?q=query- termrpp=99result_type=recentsince_id=35409539146719234 What I've found is that about 99% of the time I get back an empty response, just the feed tag wrapped around the meta data for the query but no results. But if I just run the exact same curl command over and over again, occasionally I'll get a response with a full payload of 99 tweets, none of which have anything to do with my search terms. Subsequent executions of the same curl command return the response w/o any tweets in it. Its a little hard to explain, but I have a log file that shows: curl - no tweets curl - no tweets curl - no tweets curl - 99 unrelated tweets curl - no tweets All running the same command via cut-and-paste and all within the space of a few seconds. More often than not, it seems like the invalid tweets are all somehow related, as if I had gotten the response for some other active query. Anyone else seeing anything this problem? The log file is 16K compressed, let me know if you'd like me to send it in. Thanks, -Chris -- 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] OAuth Twitter 401 Unauthorized
Sending signed OAuth header:
Authorization: OAuth oauth_nonce=twitterecm1297372838828,
oauth_callback=http%3A%2F%2Ftwitter.myurl.com%2Fwf%2Fwf
%2Fservlet.method
%2Fcom.iflow.wf.cpn.twitter.TwitterTest.testCallback,
oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1297372838828,
oauth_consumer_key=05aXcuPKpDAQMR**,
oauth_signature=O%2F4RKChkbfXCt%2Bp73%2**,
oauth_version=1.0
to URL: https://api.twitter.com/oauth/request_token
and get Respnoseheaders:
null:[HTTP/1.1 401 Unauthorized]
X-Runtime:[0.00684]
Content-Length:[44]
X-Transaction:[1297372843-99326-52182]
Expires:[Tue, 31 Mar 1981 05:00:00 GMT]
Last-Modified:[Thu, 10 Feb 2011 21:20:43 GMT]
X-Revision:[DEV]
Set-Cookie:
[_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJaOchEuAToHaWQiJTBmYWI3MGQ3ZTExYTYz
%250ANzc2ZTE4Y2Y3MWIwYzIwMjg5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
ca7e3ee9b6aee2cb024341be086688bee84c3aac; domain=.twitter.com; path=/;
HttpOnly, guest_id=129737284366960543; path=/; expires=Sat, 12 Mar
2011 21:20:43 GMT, k=188.22.59.201.1297372843662357; path=/;
expires=Thu, 17-Feb-11 21:20:43 GMT; domain=.twitter.com]
Connection:[close]
Server:[hi]
Cache-Control:[no-cache, no-store, must-revalidate, pre-check=0, post-
check=0]
Pragma:[no-cache]
Status:[401 Unauthorized]
Date:[Thu, 10 Feb 2011 21:20:43 GMT]
Vary:[Accept-Encoding]
Content-Type:[text/html; charset=utf-8]
and when reading from the URL (opening input stream):
java.io.IOException: Server returned HTTP response code: 401 for URL:
https://api.twitter.com/oauth/request_token
Java Code:
PrintWriter pw = res.getWriter();
String timestamp = + new Date().getTime();
String nonce = twitterecm + timestamp;
String httpParameters = oauth_callback= +
URLEncoder.encode(TWITTER_CALLBACKURL, UTF-8)
+ oauth_consumer_key= + URLEncoder.encode(CONSUMER_KEY,
UTF-8)
+ oauth_nonce= + URLEncoder.encode(nonce, UTF-8)
+ oauth_signature_method=HMAC-SHA1
+ oauth_timestamp= + timestamp
+ oauth_version=1.0;
String signatureBase = POST
+ + URLEncoder.encode(REQUESTTOKEN_ENDPOINT,
HttpUtils.UTF_8)
+ + URLEncoder.encode(httpParameters, UTF-8);
pw.write(br/br/bSIGNATUREBASE/b: + signatureBase);
String signatureKey = CONSUMER_SECRET + ;
pw.write(br/bSIGNATUREKEY/b: + signatureKey);
// sign URL with consumer secret
String signature = getSignature(signatureBase, signatureKey);
pw.write(br/br/bSIGNATURE/b: + signature);
String header = OAuth oauth_nonce=\ +
URLEncoder.encode(nonce, UTF-8)
+ \, oauth_callback=\ +
URLEncoder.encode(TWITTER_CALLBACKURL, UTF-8)
+ \, oauth_signature_method=\HMAC-SHA1
+ \, oauth_timestamp=\ + timestamp
+ \, oauth_consumer_key=\ +
URLEncoder.encode(CONSUMER_KEY, UTF-8)
+ \, oauth_signature=\ + URLEncoder.encode(signature,
HttpUtils.UTF_8)
+ \, oauth_version=\1.0
+ \;
pw.write(br/br/bHEADER:/b Authorization: +
header.replace(,, ,br/));
String urlStr = REQUESTTOKEN_ENDPOINT;
pw.write(br/br/bTO URL/b: + urlStr);
URL url = new URL(urlStr);
HttpURLConnection conn = (HttpURLConnection)
url.openConnection();
conn.setRequestProperty(Authorization, header);
conn.setRequestMethod(POST);
conn.setDoOutput(true);
OutputStreamWriter writer = new
OutputStreamWriter(conn.getOutputStream(), UTF-8);
writer.write(httpParameters);
writer.flush();
StringBuilder answer = new StringBuilder();
BufferedReader reader = new BufferedReader(new
InputStreamReader(conn.getInputStream(), UTF-8));
String line;
while ((line = reader.readLine()) != null) {
answer.append(line);
}
writer.close();
reader.close();
pw.write(br/ + answer.toString());
pw.flush();
pw.close();
Pleas help, tried lots of different things, Google API with
OAuthConsumer, OAuthProvider etc. too, got always the same response.
Thx, Andy
--
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] Update on Whitelisting
Thanks for finally making this clear, Ryan. I've been critical of the way Twitter was handling whitelisting for months now. Hiding and ignoring are not good ways to build a developer community. While it would be great to have the possibility of whitelisting, it is much worse to offer that promise to clients and investors and then not be able to deliver it. Now nobody can make plans based on whitelisting. As Edward pointed out in his response, the really devastating thing would be for Twitter to still offer whitelisting on the side to a chosen few. If this is supposed to be a level playing field, please make sure it really is. Breaking that promise would be the worst form of lying. This doesn't have to eliminate apps. It just forces them to change focus. As you say, as long as you are doing things for users, instead of for investors, there is still a huge field to play in, and to make money. This week I have gotten multiple requests to work on projects that tweet for users, and tweet to accounts that are read by users. The key is that this is done for actual Twitter accounts. I see no problem building a solid revenue stream on this type of consulting. I also want to build sites that can be used by many thousands of users, and then monetize them by selling mobile apps, or advertising. I don't see how this change would block that. What is now blocked is the idea of following every user, and every follower of that user, without any actual users asking to do so. Trying to suck in all data and make money on the resulting analysis is not going to happen. Was there ever any money in that anyway? Now the next step in opening up this marketplace is to create multiple resellers of Twitter API data, and let them compete on price. Giving Gnip a monopoly over this market makes no sense. Twitter's biggest problem is the huge volume of requests. By blocking whitelisting you are forcing some developers to cheat by creating multiple accounts and distributing their requests across them. That can never be stopped. What you have to do is make it inefficient, by letting multiple resellers complete and drive the price of Twitter data down. Then the strongest reseller will take the load off of you and offer enough value added that developers will be willing to pay for data. That will never happen when only one reseller sets the price. You are riding a tiger. Good luck, and try to stay open and honest. This is a good step on that path. I've been watching software companies try to manage their developer communities for 31 years. As long as you tell the truth, you will succeed. On Thu, Feb 10, 2011 at 4:43 PM, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker:
[twitter-dev] should search and streaming apis return similar tweets for equivalent geolocation areas
Hi, I have been running some tests to gather tweets from users within a geo area using both the search API (with the geocode parameter) and the streaming API (with the statuses/filter method locations parameter). I have noticed that the streaming API returns far less tweets for an equivalent area expressed either as a latlong+radius for the search API or as a bounding box for the streaming API. Is this normal or should we expect a similar result set with both methods? In the doc it says that the streaming API will only return tweets that are created using the Geotagging API (and within the bounding box) but the search API will preferentially use the Geotagging API, but will fall back to the Twitter profile location. Can this explain why I see much more results with the search API? Thanks, Colin -- 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] Update on Whitelisting
On Thu, 10 Feb 2011 17:26:17 -0500, Adam Green 140...@gmail.com wrote: Now the next step in opening up this marketplace is to create multiple resellers of Twitter API data, and let them compete on price. Giving Gnip a monopoly over this market makes no sense. Twitter's biggest problem is the huge volume of requests. By blocking whitelisting you are forcing some developers to cheat by creating multiple accounts and distributing their requests across them. That can never be stopped. What you have to do is make it inefficient, by letting multiple resellers complete and drive the price of Twitter data down. Then the strongest reseller will take the load off of you and offer enough value added that developers will be willing to pay for data. That will never happen when only one reseller sets the price. +1000 -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Update on Whitelisting
Hi Ed, Some quick answers to a few specific points below: That brings up an interesting question. Suppose I'm using a web-based service like HootSuite that *isn't* using Site Streams (at least, I think they aren't using Site Streams). They're then getting 350 API calls per hour via oAuth in the znmeb account from their IP address. Now I log on to Twitter using the standard web app from my workstation. Do I get another 350 calls per hour because I have my own IP address, or are all IP addresses authenticated as znmeb sharing that 350? With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour. @znmeb using YoruFukurou has 350 requests per hour. Using one user request in Twitter for iPhone does not effect the user quota for YoruFukurou. A related question - how far away from production is Site Streams, and is there a plan to encourage services like HootSuite to migrate to Site Streams? It seems like it would be a big win for them (and all the other web-based Twitter platforms). Site Streams is nearing availability for general use -- there are a few more t's to cross and i's to dot. In fact, HootSuite is currently a Site Streams beta consumer. Taylor -- 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] Update on Whitelisting
On Thu, 10 Feb 2011 15:11:09 -0800, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few specific points below: With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour. @znmeb using YoruFukurou has 350 requests per hour. Using one user request in Twitter for iPhone does not effect the user quota for YoruFukurou. Ah ... sounds good ... except for the buy an iPhone part, anyhow ;-) A related question - how far away from production is Site Streams, and is there a plan to encourage services like HootSuite to migrate to Site Streams? It seems like it would be a big win for them (and all the other web-based Twitter platforms). Site Streams is nearing availability for general use -- there are a few more t's to cross and i's to dot. In fact, HootSuite is currently a Site Streams beta consumer. Thanks! That's great news - I'm a HootSuite user again. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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: Update on Whitelisting
Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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: Update on Whitelisting
Quick question, are the whitelists IP based? It's been a couple years since we requested the whitelisting, which was granted, but I am curious how that will affect us if we add more IP ranges to our servers? Thanks, Ben -- 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: Update on Whitelisting
EXACTLY, i posted my opinion, result? Luckily we dont use this shit matt/tayor: an app suspended. On Feb 10, 2011, at 7:19 PM, Fishst1k wrote: Quick question, are the whitelists IP based? It's been a couple years since we requested the whitelisting, which was granted, but I am curious how that will affect us if we add more IP ranges to our servers? Thanks, Ben -- 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 Regards, Edward Hotchkiss edw...@edwardhotchkiss.com http://www.edwardhotchkiss.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] posting status
Which external libraries do you use? Have a look at the update status documentation. On Fri, Feb 11, 2011 at 3:05 AM, twt kritikasing...@gmail.com wrote: Is there an easy way of posting tweets from a desktop client without using any external library? -- 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 -- xxx The butterfly does not count years, but moments, and therefore has enough time. - Rabindranath Tagore -- 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] Update on Whitelisting
Correction, Ed: Rate limiting is considered on an IP + user basis only at this time, while authenticated, not by client + user. Hold-over from the old world. Taylor On Thu, Feb 10, 2011 at 3:11 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few specific points below: That brings up an interesting question. Suppose I'm using a web-based service like HootSuite that *isn't* using Site Streams (at least, I think they aren't using Site Streams). They're then getting 350 API calls per hour via oAuth in the znmeb account from their IP address. Now I log on to Twitter using the standard web app from my workstation. Do I get another 350 calls per hour because I have my own IP address, or are all IP addresses authenticated as znmeb sharing that 350? With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour. @znmeb using YoruFukurou has 350 requests per hour. Using one user request in Twitter for iPhone does not effect the user quota for YoruFukurou. A related question - how far away from production is Site Streams, and is there a plan to encourage services like HootSuite to migrate to Site Streams? It seems like it would be a big win for them (and all the other web-based Twitter platforms). Site Streams is nearing availability for general use -- there are a few more t's to cross and i's to dot. In fact, HootSuite is currently a Site Streams beta consumer. Taylor -- 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: Update on Whitelisting
Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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: Update on Whitelisting
On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] OAuth Twitter 401 Unauthorized
Hi,
You may want to look at Twitter4J's source code.
It just works.
https://github.com/yusuke/twitter4j
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On Feb 11, 2011, at 07:21 , ayjay wrote:
Sending signed OAuth header:
Authorization: OAuth oauth_nonce=twitterecm1297372838828,
oauth_callback=http%3A%2F%2Ftwitter.myurl.com%2Fwf%2Fwf
%2Fservlet.method
%2Fcom.iflow.wf.cpn.twitter.TwitterTest.testCallback,
oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1297372838828,
oauth_consumer_key=05aXcuPKpDAQMR**,
oauth_signature=O%2F4RKChkbfXCt%2Bp73%2**,
oauth_version=1.0
to URL: https://api.twitter.com/oauth/request_token
and get Respnoseheaders:
null:[HTTP/1.1 401 Unauthorized]
X-Runtime:[0.00684]
Content-Length:[44]
X-Transaction:[1297372843-99326-52182]
Expires:[Tue, 31 Mar 1981 05:00:00 GMT]
Last-Modified:[Thu, 10 Feb 2011 21:20:43 GMT]
X-Revision:[DEV]
Set-Cookie:
[_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJaOchEuAToHaWQiJTBmYWI3MGQ3ZTExYTYz
%250ANzc2ZTE4Y2Y3MWIwYzIwMjg5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
ca7e3ee9b6aee2cb024341be086688bee84c3aac; domain=.twitter.com; path=/;
HttpOnly, guest_id=129737284366960543; path=/; expires=Sat, 12 Mar
2011 21:20:43 GMT, k=188.22.59.201.1297372843662357; path=/;
expires=Thu, 17-Feb-11 21:20:43 GMT; domain=.twitter.com]
Connection:[close]
Server:[hi]
Cache-Control:[no-cache, no-store, must-revalidate, pre-check=0, post-
check=0]
Pragma:[no-cache]
Status:[401 Unauthorized]
Date:[Thu, 10 Feb 2011 21:20:43 GMT]
Vary:[Accept-Encoding]
Content-Type:[text/html; charset=utf-8]
and when reading from the URL (opening input stream):
java.io.IOException: Server returned HTTP response code: 401 for URL:
https://api.twitter.com/oauth/request_token
Java Code:
PrintWriter pw = res.getWriter();
String timestamp = + new Date().getTime();
String nonce = twitterecm + timestamp;
String httpParameters = oauth_callback= +
URLEncoder.encode(TWITTER_CALLBACKURL, UTF-8)
+ oauth_consumer_key= + URLEncoder.encode(CONSUMER_KEY,
UTF-8)
+ oauth_nonce= + URLEncoder.encode(nonce, UTF-8)
+ oauth_signature_method=HMAC-SHA1
+ oauth_timestamp= + timestamp
+ oauth_version=1.0;
String signatureBase = POST
+ + URLEncoder.encode(REQUESTTOKEN_ENDPOINT,
HttpUtils.UTF_8)
+ + URLEncoder.encode(httpParameters, UTF-8);
pw.write(br/br/bSIGNATUREBASE/b: + signatureBase);
String signatureKey = CONSUMER_SECRET + ;
pw.write(br/bSIGNATUREKEY/b: + signatureKey);
// sign URL with consumer secret
String signature = getSignature(signatureBase, signatureKey);
pw.write(br/br/bSIGNATURE/b: + signature);
String header = OAuth oauth_nonce=\ +
URLEncoder.encode(nonce, UTF-8)
+ \, oauth_callback=\ +
URLEncoder.encode(TWITTER_CALLBACKURL, UTF-8)
+ \, oauth_signature_method=\HMAC-SHA1
+ \, oauth_timestamp=\ + timestamp
+ \, oauth_consumer_key=\ +
URLEncoder.encode(CONSUMER_KEY, UTF-8)
+ \, oauth_signature=\ + URLEncoder.encode(signature,
HttpUtils.UTF_8)
+ \, oauth_version=\1.0
+ \;
pw.write(br/br/bHEADER:/b Authorization: +
header.replace(,, ,br/));
String urlStr = REQUESTTOKEN_ENDPOINT;
pw.write(br/br/bTO URL/b: + urlStr);
URL url = new URL(urlStr);
HttpURLConnection conn = (HttpURLConnection)
url.openConnection();
conn.setRequestProperty(Authorization, header);
conn.setRequestMethod(POST);
conn.setDoOutput(true);
OutputStreamWriter writer = new
OutputStreamWriter(conn.getOutputStream(), UTF-8);
writer.write(httpParameters);
writer.flush();
StringBuilder answer = new StringBuilder();
BufferedReader reader = new BufferedReader(new
InputStreamReader(conn.getInputStream(), UTF-8));
String line;
while ((line = reader.readLine()) != null) {
answer.append(line);
}
writer.close();
reader.close();
pw.write(br/ + answer.toString());
pw.flush();
pw.close();
Pleas help, tried lots of different things, Google API with
OAuthConsumer, OAuthProvider etc. too, got always the same response.
Thx, Andy
--
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:
Re: [twitter-dev] Re: Update on Whitelisting
Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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: Update on Whitelisting
Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no longer planning on gradually increasing rate limits, as has been stated many times in the past, would be appreciated. -- 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: Update on Whitelisting
Yes, Do tell. I have a whitelisted app, but came to the realization that I needed to switch to IP based so that all users of the application would have a higher DM limit--critical as my app is a social learning tool for mobile users. Now it looks like my project is dead in the water. Having each person have their own account is fine, but the 250 per day DMs is the problem. Is there any way to increase DMs per day for accounts? I suspect that Twitter may need to rethink this change as there are some applications that needed the whitelisting for DMs while the hourly limits were never a problem. Bitting my nails and waiting for an answer On Feb 10, 6:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Update on Whitelisting
Hi Taylor, Could you please elaborate on IP + user ? Does this mean that the rate of 350/hour is applicable per user? Alternatly, does this mean I can have more than 1 user using the same IP and having seperate rate buckets( 350 each per hour). Thanks Regards Umashankar Das On Fri, Feb 11, 2011 at 7:07 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Correction, Ed: Rate limiting is considered on an IP + user basis only at this time, while authenticated, not by client + user. Hold-over from the old world. Taylor On Thu, Feb 10, 2011 at 3:11 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few specific points below: That brings up an interesting question. Suppose I'm using a web-based service like HootSuite that *isn't* using Site Streams (at least, I think they aren't using Site Streams). They're then getting 350 API calls per hour via oAuth in the znmeb account from their IP address. Now I log on to Twitter using the standard web app from my workstation. Do I get another 350 calls per hour because I have my own IP address, or are all IP addresses authenticated as znmeb sharing that 350? With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour. @znmeb using YoruFukurou has 350 requests per hour. Using one user request in Twitter for iPhone does not effect the user quota for YoruFukurou. A related question - how far away from production is Site Streams, and is there a plan to encourage services like HootSuite to migrate to Site Streams? It seems like it would be a big win for them (and all the other web-based Twitter platforms). Site Streams is nearing availability for general use -- there are a few more t's to cross and i's to dot. In fact, HootSuite is currently a Site Streams beta consumer. Taylor -- 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] Update on Whitelisting
Ideally then Twitter limits the maximum number of followers, because what good the company had many followers and not speak to them, my project for example needed to talk to each follower individually, not to be in the same time could divide this into three or four days, but with the limit of Dm 250 per day, how to do this with a client who has 10,000 followers? since we have no more to whitelisting, tks Carlos Eduardo On Thu, Feb 10, 2011 at 7:43 PM, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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] Custom Follow Button
Can anyone point me to any good AJAX/Jquery/PHP scripts that use a custom follow button? I find the @Anywhere follow buttons to be too big for my needs. Quy -- 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: Update on Whitelisting
Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Hope that helps clarify. Best, Ryan -- Ryan Sarver @rsarver http://twitter.com/rsarver On Thu, Feb 10, 2011 at 6:17 PM, Orian Marx (@orian) or...@orianmarx.comwrote: Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no longer planning on gradually increasing rate limits, as has been stated many times in the past, would be appreciated. -- 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: Update on Whitelisting
On Thu, 10 Feb 2011 18:46:46 -0800, Ryan Sarver rsar...@twitter.com wrote: Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Interesting - I had an incident last week where I was running out of calls in #newtwitter - that's why I asked about HootSuite. I never did figure out what happened. I'm running them both now and not running out. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Twitter Feeds
I need a twitter feed link on our web page, The behaviour should be like this. When link is clicked a twitter login page should appear and after loging in i should get the feeds of that user. Plese Help Thanks -- 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: Update on Whitelisting
Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- 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
