[twitter-dev] Re: Invalid / used nonce
Hello Taylor! I don't think the error has something to do with the access token, because sometimes the error is thrown during my request to retrieve a Request Token. I'm afraid the error has something to do with encodings or something similar. Also, I would like to know if there is an advised way to generate the nonce value. I was using the formula of the OAuth library : it concatenates the timestamp and a random integer value, and then it applies a MD5 hash on it. Maybe you or someone else know another way that works to generate this value. Regards. Mounir Regragui On 29 juil, 18:15, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Mounir, In this case I'm fairly confident then that it's the Twitter API implementation of OAuth that's at fault here and these invalid nonce errors are spurious for you. While I hate to suggest working around bugs like this, it might be your best strategy -- if you encounter an invalid nonce error, pause for a few moments, regenerate the request with a different nonce and timestamp, and try again. If you find a case where it's repeatably throwing you this error, for example -- you notice that it only happens for a certain access token, or it only happens when you're using certain characters in the POST body or nonce -- then please bring it to our attention. Scalability projects, among other things, have prevented our engineering team from rolling out a reimplementation of our OAuth back end that will fix aggravating issues like these, among other things. Taylor On Thu, Jul 29, 2010 at 12:43 AM, Mounir Regragui reg.mou...@gmail.comwrote: Hello everybody, Yesterday I was exposing an issue I encoutered. My code was working perfectly, and then I started having a 401 error code with this error message : errorInvalid / used nonce/error when I make API calls. I thought it was solved because yesterday I did some API calls that made it through. However this issue is still here today. Actually, when I make API calls (POST, GET or OAuth requests), sometimes everything works fine, sometimes i have the Invalid / used nonce error. As I told Taylor yesterday, I am sure that that the system time is correct (because when I change it, nothing works), and because as I said, when i try to send a request with the exact same code running, sometimes it fails, sometimes it does not. Here are dumps of the communications I tried to send a tweet, had an error :http://pastebin.com/ur2JYtnM A few seconds later, i run the exact same code and it is valid : http://pastebin.com/6knpLHBW (I will reset my key and secret ^^) I really do not know where the issue comes from, because the code was running flawlessly last week! Any kind of help appreciated. Regards. Mounir Regragui
[twitter-dev] Getting Started...
Hello, I'm trying to migrate my code across to using oAuth, and there is no class for oAuth in the language I use, so I'm having to drop in at the deep end. At the moment, I am a bit stuck, I keep getting a 401 when I request a token. I have created this as my signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%3DAXpCOWR4c2IZVlSGNXvdZg%26auth_nonce%3DQP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk%26auth_signature_method%3DHMAC-SHA1%26auth_timestamp%3D1280511571%26auth_version%3D1.0 Created a signed hash of this, using my Consumer Secret Base-64 encoded the hash since it was non-unicode URL Encoded the Base-64 string which then gives me: oAuth oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_callback=oob, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1280511571, oauth_consumer_key=AXpCOWR4c2IZVlSGNXvdZg, oauth_signature=4zCns2DZTQzmo2HpYY99dhJVl5A%3D, oauth_version=1.0 But when I make the POST request with the above set, I still get a 401 Unauthorised. Could someone steer me in the right direction please? Thanks :) Andy
[twitter-dev] OAuth 2.0 status?
Hello all, What is the status of OAuth 2.0 implementation on twitter? Is there any service to begin/learn how to use it to build client applications for twitter? Thanks! mic
[twitter-dev] Streaming API for lists
Hey there! I wanted to know if Twitter will integrate lists into the streaming API. Thx.
Re: [twitter-dev] Streaming API for lists
We were planning to do lists, but we postponed the feature to get the bulk of User Streams to market sooner and to also get User Streams out to more users. We'll consider lists as an add-on later. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Jul 30, 2010 at 4:13 AM, sexyprout abom...@gmail.com wrote: Hey there! I wanted to know if Twitter will integrate lists into the streaming API. Thx.
[twitter-dev] Re: since_id not getting since_id :)
I've also noticed issues with since_id on multiple API calls. The docs state for since_id... If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available. I've found this to not be true and many methods return the newest Tweets. Rhys On Jul 29, 6:04 am, Matt Harris thematthar...@twitter.com wrote: Hey Gary, I think you mean the search API but i'm not sure. If you can provide an example of the request you are making to the API, the response (as search changes quickly) and the ID you then use for since_id i'll take a look and check what's happening. Best, Matt On Wed, Jul 28, 2010 at 4:45 AM, Gary gbre...@gmail.com wrote: Hi, I've got a question about since_id and if it actually works. The API states - since_id: returns tweets with status ids greater than the given id. So when I get a list of 100 twitter messages, I store the maximum id in that group, which I get from the id property after stripping out tag:search.twitter.com,2005: and use that id for my since_id the next time I run the query. The problem is I've noticed I get back id's that I've already seen in previous requests when using since_id. It is fine for me I just ignore them I just thought I'd bring it to the attention of you guys, unless I've misinterpreted this functionality. Thanks, Gary -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] http://www.twitter.com/?status= problem with special characters
I think I found a problem with the status update using GET. http://twitter.com/?status=foo%20bar will work, correctly unescaping characters in the status textarea: foo bar However when trying to change the update using this url: http://www.twitter.com/?status=foo%20bar, the user gets redirected to twitter.com/?status=foo%2520bar (notice the %25) which results into the escaped status in the textarea: foo%20bar
[twitter-dev] Trill
Hi Guys Today we launched our Twitter App for Nokia S60 devices . its live on OVI . you can get it at http://store.ovi.com/content/49452 . I would love to have your feedback on the same . Please feel free to let me know what you like /dislike about Trill and how can we make it better. Looking forward to your feedback Regards Prashant
Re: [twitter-dev] Need inputs to implement Twitter app using xAuth
It is not that difficult. However, that would be a good time saving if you reused some of those libraries. On Thu, Jul 29, 2010 at 3:20 AM, Sambath Chandran sambat...@gmail.comwrote: But I just want to know one thing. How much difficult to implement making xAuth call in Java without any libraries? Thanks, Sambath On Thu, Jul 29, 2010 at 11:29 AM, Sambath Chandran sambat...@gmail.comwrote: Thanks a lot Ernandes and Abraham. Regards, Sambath On Wed, Jul 28, 2010 at 9:33 PM, Abraham Williams 4bra...@gmail.comwrote: Twitter4j supports xAuth: http://goo.gl/ZmM2 Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Jul 28, 2010 at 02:29, Sambath Chandran sambat...@gmail.comwrote: All, I am implementing an application to receive and the latest tweet from the twitter. After refering to twitter website, I concluded to use xAuth authentication for my development. Can anybody let me know is there any ready to use java library for xAuth? Basially I want to know to how to make xAuth work with Java. Thanks, Sambath -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets.
Re: [twitter-dev] http://www.twitter.com/?status= problem with special characters
Hey, Thanks for the email. The URL pattern you are using is incorrect which is why you are seeing the status get dropped. For the ?status= URLs to work you should make sure your links follow this pattern: http://twitter.com/home?status=url%20encoded%20message Missing the /home will mean the status isn't maintained on redirects or logins so you'll want to make sure you use that pattern instead. I'll let the team know about the double encoding issue on redirect from www.twitter.com to twitter.com but to be safe you should use the URL pattern above and not rely on the redirect. Thanks, Matt On Fri, Jul 30, 2010 at 6:59 AM, warpdesign nicolas.r...@gmail.com wrote: I think I found a problem with the status update using GET. http://twitter.com/?status=foo%20bar will work, correctly unescaping characters in the status textarea: foo bar However when trying to change the update using this url: http://www.twitter.com/?status=foo%20bar, the user gets redirected to twitter.com/?status=foo%2520bar (notice the %25) which results into the escaped status in the textarea: foo%20bar -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Twitter annotations release date?
Hi guys, any news on the annotations roll out date? Its been a wee while since I last heard anything (unless I missed it, in which case 'Sorry!'). Has the spec been finalised or are you still hammering it out? PS if anyone is interested in annotations, check out my app at www.tweetplugs.com, I think it's quite nifty!
[twitter-dev] isConnected() function always returning false
Hi there,
I'm adding @anywhere into our website, for the purpose of tweeting the
title/URL of specific pages. I'm running into one issue regarding the
isConnected() function - it always seems to return false. This is
preventing me from determining if the user is truly connected or not,
resulting in my Sign In link getting displayed every time. When
testing, I know I'm connected because I'm able to tweet. Has anyone
had this happen before? This is the relevant code snippet:
twttr.anywhere(function (T) {
var currentUser,
screenName;
if ( T.isConnected() ) {
currentUser = T.currentUser;
screenName = currentUser.data('screen_name');
$('#twitter-box #twitter-username-
placeholder').html('Signed in as b' + screenName + '/b. span
id=signout class=fake-linkSign out of Twitter/span.');
} else {
$('#twitter-box #twitter-username-
placeholder').html('Logged out of Twitter. span id=signin
class=fake-linkClick here to Sign In/span');
}
T(#twitter-box #twitter-box-placeholder).tweetBox({
label : Share this page on Twitter,
defaultContent : window.document.title + http://be.net;
+ window.location.pathname,
onTweet : processTweetCallback
}); // tweetBox
}); // twttr
[twitter-dev] Twitter Planned Network Maintenance on Sat, July 31st
Hi Developers, Twitter’s hosting provider, NTT America, is upgrading a portion of our internal network starting on July 31st at 11PM Pacific (August 1st, at 600 UTC). This maintenance will last approximately five hours. During this time, there may be intermittent periods when some users are unable to use Twitter. During these intermittent periods, end-users will see Twitter's maintenance page ( http://media.tumblr.com/tumblr_l6e4wrBkaA1qznz0d.png ) while API requests will return HTTP 500-series status codes. Thanks! Taylor
[twitter-dev] Whitelisting takes 7 days or 72 hours?
Hi there, We have submitted whitelisting application 3-4 days ago and still haven't received any response. API documentation says it would take upto 72 hours. But I also saw somewhere it stated it would take upto 7 days. So I was just curious how long will it take to get response from Twitter? Apologies if I missed something. Thanks!
Re: [twitter-dev] Whitelisting takes 7 days or 72 hours?
Hi Rohit, We're behind in processing whitelisting requests and I don't have a good estimate of turn around time to give you right now. We're also in the process of re-evaluating our whitelisting policies. While we've never been cavalier in granting privileges to detailed requests for additional permissions, we are evaluating requests more critically now. We strive to respond to every incoming request, but due to request volume, there are times we may neglect to respond directly to unapproved requests. Feel free to send me an email with more details about your request (the @username you made the request from and any other details), and I'll see what the hold up is. Thanks! Taylor On Fri, Jul 30, 2010 at 3:18 PM, Rohit Shah honestfollow...@gmail.comwrote: Hi there, We have submitted whitelisting application 3-4 days ago and still haven't received any response. API documentation says it would take upto 72 hours. But I also saw somewhere it stated it would take upto 7 days. So I was just curious how long will it take to get response from Twitter? Apologies if I missed something. Thanks!
Re: [twitter-dev] Discovering Who To Follow through the Twitter API
Is this in the API, or just on the web site? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Developers, We're rolling out new features to the site today called Suggestions for You, These features help users discover relevant Twitter users to follow, based on social graph analytics and algorithms designed by our user relevance team. You can read more about this feature announcement in our blog post at http://blog.twitter.com/2010/07/discovering-who-to-follow.html. Twitter's vision for how and where these relevant recommendations will surface can be found on our website. With the API, developers can build similar features in their applications or, as we expect many of you will want to do, invent new utilizations for the data. Methods will be available for obtaining suggestions for the current user as well as getting the users recommended as similar to another user. Look for developer documentation on these new platform resources soon. Finding relevant accounts to follow on Twitter is about to get easier. What will you build? Taylor Singletary Developer Advocate http://twitter.com/episod
[twitter-dev] Re: Discovering Who To Follow through the Twitter API
Hi Ed, An API for this feature is coming very soon... And you're going to love it! Taylor On Friday, July 30, 2010, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this in the API, or just on the web site? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Developers, We're rolling out new features to the site today called Suggestions for You, These features help users discover relevant Twitter users to follow, based on social graph analytics and algorithms designed by our user relevance team. You can read more about this feature announcement in our blog post at http://blog.twitter.com/2010/07/discovering-who-to-follow.html. Twitter's vision for how and where these relevant recommendations will surface can be found on our website. With the API, developers can build similar features in their applications or, as we expect many of you will want to do, invent new utilizations for the data. Methods will be available for obtaining suggestions for the current user as well as getting the users recommended as similar to another user. Look for developer documentation on these new platform resources soon. Finding relevant accounts to follow on Twitter is about to get easier. What will you build? Taylor Singletary Developer Advocate http://twitter.com/episod
Re: [twitter-dev] Re: Discovering Who To Follow through the Twitter API
I'm still trying to figure out who gets recommended when someone follows me ... thinking about crowdsourcing it. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Ed, An API for this feature is coming very soon... And you're going to love it! Taylor On Friday, July 30, 2010, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Is this in the API, or just on the web site? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Developers, We're rolling out new features to the site today called Suggestions for You, These features help users discover relevant Twitter users to follow, based on social graph analytics and algorithms designed by our user relevance team. You can read more about this feature announcement in our blog post at http://blog.twitter.com/2010/07/discovering-who-to-follow.html. Twitter's vision for how and where these relevant recommendations will surface can be found on our website. With the API, developers can build similar features in their applications or, as we expect many of you will want to do, invent new utilizations for the data. Methods will be available for obtaining suggestions for the current user as well as getting the users recommended as similar to another user. Look for developer documentation on these new platform resources soon. Finding relevant accounts to follow on Twitter is about to get easier. What will you build? Taylor Singletary Developer Advocate http://twitter.com/episod
[twitter-dev] Re: Uploading photo w\ OAuth echo
Basically what you do in an echo is make an oAuth request to the verify_credentials.json page, but you don't do the actual request - instead, you take the Authorization: header and send it to Twitpic. So, no, you don't add anything else than you would have for a normal call to verify_credentials. Tom On Jul 29, 3:21 pm, Bondi roibo...@gmail.com wrote: Hi. I also keep getting 401 from Twitpic. Just to make sure - do we need to add the realm to the signature calculation ? Or only to the header ? Thanks for the help, Roi.
[twitter-dev] Re: Getting Started...
I don't immediately see what's wrong, but consider tracing your steps. You already have a class that creates the authorization header. Feed it some information which you know to be correct, and check for the outcome. You could use these: http://dev.twitter.com/pages/auth#request-token - all information is there, including values which you get between the steps. Tom On Jul 30, 11:46 am, Andy Dixon andy.di...@zxcreative.com wrote: Hello, I'm trying to migrate my code across to using oAuth, and there is no class for oAuth in the language I use, so I'm having to drop in at the deep end. At the moment, I am a bit stuck, I keep getting a 401 when I request a token. I have created this as my signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%3DAXpCOWR4c2IZVlSGNXvdZg%26auth_nonce%3DQP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk%26auth_signature_method%3DHMAC-SHA1%26auth_timestamp%3D1280511571%26auth_version%3D1.0 Created a signed hash of this, using my Consumer Secret Base-64 encoded the hash since it was non-unicode URL Encoded the Base-64 string which then gives me: oAuth oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_callback=oob, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1280511571, oauth_consumer_key=AXpCOWR4c2IZVlSGNXvdZg, oauth_signature=4zCns2DZTQzmo2HpYY99dhJVl5A%3D, oauth_version=1.0 But when I make the POST request with the above set, I still get a 401 Unauthorised. Could someone steer me in the right direction please? Thanks :) Andy
[twitter-dev] Re: Invalid / used nonce
Hi Mounir, I'm using this code myself, maybe you can transform it to the language you use. http://www.devonferns.com/cocoablog/?p=45 Tom On Jul 30, 11:32 am, Mounir Regragui reg.mou...@gmail.com wrote: Hello Taylor! I don't think the error has something to do with the access token, because sometimes the error is thrown during my request to retrieve a Request Token. I'm afraid the error has something to do with encodings or something similar. Also, I would like to know if there is an advised way to generate the nonce value. I was using the formula of the OAuth library : it concatenates the timestamp and a random integer value, and then it applies a MD5 hash on it. Maybe you or someone else know another way that works to generate this value. Regards. Mounir Regragui On 29 juil, 18:15, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Mounir, In this case I'm fairly confident then that it's the Twitter API implementation of OAuth that's at fault here and these invalid nonce errors are spurious for you. While I hate to suggest working around bugs like this, it might be your best strategy -- if you encounter an invalid nonce error, pause for a few moments, regenerate the request with a different nonce and timestamp, and try again. If you find a case where it's repeatably throwing you this error, for example -- you notice that it only happens for a certain access token, or it only happens when you're using certain characters in the POST body or nonce -- then please bring it to our attention. Scalability projects, among other things, have prevented our engineering team from rolling out a reimplementation of our OAuth back end that will fix aggravating issues like these, among other things. Taylor On Thu, Jul 29, 2010 at 12:43 AM, Mounir Regragui reg.mou...@gmail.comwrote: Hello everybody, Yesterday I was exposing an issue I encoutered. My code was working perfectly, and then I started having a 401 error code with this error message : errorInvalid / used nonce/error when I make API calls. I thought it was solved because yesterday I did some API calls that made it through. However this issue is still here today. Actually, when I make API calls (POST, GET or OAuth requests), sometimes everything works fine, sometimes i have the Invalid / used nonce error. As I told Taylor yesterday, I am sure that that the system time is correct (because when I change it, nothing works), and because as I said, when i try to send a request with the exact same code running, sometimes it fails, sometimes it does not. Here are dumps of the communications I tried to send a tweet, had an error :http://pastebin.com/ur2JYtnM A few seconds later, i run the exact same code and it is valid : http://pastebin.com/6knpLHBW (I will reset my key and secret ^^) I really do not know where the issue comes from, because the code was running flawlessly last week! Any kind of help appreciated. Regards. Mounir Regragui
[twitter-dev] Re: Getting Started...
Just going to chime in that I'm having the same problem with my own implementation, despite following the documentation exactly. Even sending the exact header that Tom linked to, OAuth oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_callback=http%3A%2F%2Flocalhost%3A3005%2Fthe_dance %2Fprocess_callback%3Fservice_provider_id%3D11, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1272323042, oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_signature=8wUi7m5HFQy76nowoCThusfgB%2BQ%3D, oauth_version=1.0, I'm still getting 401 Unauthorized returns from the server. The same thing happens when I try to use an existing library, which is why I turned to trying to make one myself to figure out what's causing this error. I've got my own post on this group with further details into my specific problem, but getting an answer to this one would help me as well. Stephen On Jul 30, 4:46 am, Andy Dixon andy.di...@zxcreative.com wrote: Hello, I'm trying to migrate my code across to using oAuth, and there is no class for oAuth in the language I use, so I'm having to drop in at the deep end. At the moment, I am a bit stuck, I keep getting a 401 when I request a token. I have created this as my signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%3DAXpCOWR4c2IZVlSGNXvdZg%26auth_nonce%3DQP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk%26auth_signature_method%3DHMAC-SHA1%26auth_timestamp%3D1280511571%26auth_version%3D1.0 Created a signed hash of this, using my Consumer Secret Base-64 encoded the hash since it was non-unicode URL Encoded the Base-64 string which then gives me: oAuth oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_callback=oob, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1280511571, oauth_consumer_key=AXpCOWR4c2IZVlSGNXvdZg, oauth_signature=4zCns2DZTQzmo2HpYY99dhJVl5A%3D, oauth_version=1.0 But when I make the POST request with the above set, I still get a 401 Unauthorised. Could someone steer me in the right direction please? Thanks :) Andy
