Re: [twitter-dev] oauth/Authenticate keeps giving me PIN code

On the request_token step of the OAuth flow, are you setting an explicit oauth_callback pointing to where you want the user to be redirected after they have authorized? @episod - Taylor Singletary On Thu, Jul 14, 2011 at 12:09 AM, Paul wrote:

Re: [twitter-dev] oAuth problem with AIR desktop app - Failed to validate oauth signature and token

Hi. I have the same issue, but may i ask why you are performing a GET request with a POST signature? HTTP POST should be: POST /oauth/request_token \r\n \r\n callback=..&nonce=&... Not in the way you've shown us: HTTP POST: https://api.twitter.com/.../oauth_callback=..&;... Secondly, have you

Re: [twitter-dev] OAuth error

Hello! I found out what the problem was. The $oauth->fetch($url) needed to specify it was a GET call like: $oauth->fetch($url, null, OAUTH_HTTP_METHOD_GET, array('Connection'=>'close')); It works without those parameters for some versions of PHP+Pecl-Oauth and not for other :) Thanks a lot fo

Re: [twitter-dev] OAuth error

Hi Sreejata, Thanks for providing this information. Are you able to find out what the server is actually sending to the Twitter API. The code you've provided shows where the error is happening but not what information is being sent to the API. Without knowing what is being sent by your code it is

Re: [twitter-dev] OAuth error

Matt! Thank you SO much for the reply... I will try and explain what else I found out. A test example is: setToken($access_token, $access_token_secret); $url = "http://api.twitter.com/1/statuses/home_timeline.xml";; $oauth->fetch($url); $json = json_decode($oauth->getLastResponse(),

Re: [twitter-dev] OAuth

Hi Reet, Our developer resources site includes guidance and examples on how to use OAuth with the Twitter API. You can find more information on the following pages... Authentication: http://dev.twitter.com/pages/auth Libraries: https://dev.twitter.com/pages/libraries Using One Access To

Re: [twitter-dev] OAuth error

Hi, A 400 error indicates something in the request you are making is malformed. Are you using a library to make requests or did you create your own wrapper? If you created your own library for making requests you may instead want to try one of the libraries listed on our developer resources site:

Re: [twitter-dev] OAuth error

The time was in sync and I still used ntpd to reset it. No use. I tried to use the same script on different server, same user -> 400 error (bad request) Tried on new server, different user, same script -> it works! So I'm lead to believe something might be wrong with the twitter user a/c? Is

Re: [twitter-dev] OAuth error

Hi, if you reinstall the os, take a look of the time config of the server, i got 4xx error when the timezone of my server was missconfig. regrets! 2011/6/19 antiphobe > I am using a script to try and access the user timeline script. The > script works. The server the script was originally run

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Yes, it works. Thanks :-) --Regards, Denzil On Mon, Jun 6, 2011 at 9:10 PM, Tom van der Woerdt wrote: > In that case, try removing everything related to the req variable. Seems > it's all unrelated to the actual request (unless the oauth library is very > badly designed, of course). Line 22 a

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

In that case, try removing everything related to the req variable. Seems it's all unrelated to the actual request (unless the oauth library is very badly designed, of course). Line 22 all the way up to 35. Tom On 6/6/11 5:38 PM, Correa Denzil wrote: Well, it turns out it's not the case. Both

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa D

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Well, of course, don't literally replace the variables, but figure out a way to use the req object. I don't know anything about that object so I can't help you there. Tom On 6/6/11 5:28 PM, Correa Denzil wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): Fil

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Tom : Are you sure? This gives me a : Traceback (most recent call last): File "oauth_test.py", line 41, in resp, content = req.request(url, "GET") AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt wrote: >

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

In the "Make the auth request" part you make a request using "client" instead of the already prepared and signed "req" variable. You should use "req" to make the request. Tom On 6/6/11 5:10 PM, Correa Denzil wrote: Tom : Thanks for the reply. 1. You don't sign the test variable, you sign th

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Tom : Thanks for the reply. 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. I have changed the same 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. I don'

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. Tom On 6/6/11 4:54 PM, Correa Denzil wrote: Is that Pyt

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Is that Python? : Yes 1. You aren't signing using the proper url. Is the end point URL wrong? 2. You aren't using anything related to the signature on the request (req) I am a newbie to Python. I am trying to dabble using OAuth. I understand the OAuth flow but somehow what I am doing seems a bit

Re: [twitter-dev] Oauth Rate Limit 150 per hour?

Is that Python? Anyway, not relevant. 1. You aren't signing using the proper url. 2. You aren't using anything related to the signature on the request (req). Tom On 6/6/11 4:43 PM, Correa Denzil wrote: Hi, I am performing OAuth to sign my requests. I am not developing a web app. I am trying

Re: [twitter-dev] Oauth in Twitter via Python

Tom : I probably missed the point. I see the targeted users, their data is public and accessible using no authentication but the API limits are too small. I can't gain OAuth access from them. I would like to increase this to more API calls using OAuth. --Regards, Denzil On Sun, Jun 5, 2011 at

Re: [twitter-dev] Oauth in Twitter via Python

If you have the permission of the users, you can probably use their OAuth tokens, which gives you an almost infinite API limit (actually it's still 350 per user, but you won't easily break that). If you want to perform an analysis on a group of users without their consent (without OAuth access)

Re: [twitter-dev] Oauth in Twitter via Python

Oh! I should avoid creating multiple user accounts in that case. I would like to perform analysis on a target set of users and not streams. How do I proceed? I should add that 350 requests per hour is highly insufficient for my use case. --Regards, Denzil On Sat, Jun 4, 2011 at 11:33 PM, Tom

Re: [twitter-dev] Oauth in Twitter via Python

I'd like to point out that this is against the TOS. You should limit your API requests where possible - for a normal application with user interaction you won't need more than 350 per hour. If you do some sort of data analysis, you may need to use streams instead. Tom On 6/4/11 7:53 PM, Corr

Re: [twitter-dev] Oauth in Twitter via Python

Tom : Thanks. I will create multiple user accounts. I guess about 20 (350 * 20 = 7000 considering 1 request per second) should solve my issue. --Regards, Denzil On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdt wrote: > If you authenticate, all requests (except for search) will go into th

Re: [twitter-dev] Oauth in Twitter via Python

If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which e

Re: [twitter-dev] Oauth in Twitter via Python

Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Gifford wrote: > The way I'm reading it

Re: [twitter-dev] Oauth in Twitter via Python

The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzil wrote: > Hi, > > I am collecting Twitter data for my research. The API says that : > > [1] "Anonymous calls are based on the IP of the host and are

Re: [twitter-dev] Oauth problem error 401

Hey Javier, We do not support OAuth 2.0 but OAuth 1.0a. If you're looking for a Twitter / OAuth 1.0a library, take on look on this page: https://dev.twitter.com/pages/libraries Hope that helps! Arnaud / @rno 2011/5/19 Javier Solís > Hi, i have the problem related her

Re: [twitter-dev] OAuth Authorization screen on Windows Phone 7 (WebBrowser control)

Hi Chris, Matthieu and any others running into this issue: On May 3, 2011, at 5:00 PM, LoungeFlyZ wrote: > Something has changed in the last few days and now the page is > rendering a little "better" but scrolling/panning/zooming isnt working > & i cant enter text in the username or password fiel

Re: [twitter-dev] oAuth passthrough

Hi Scott, There's an extension to OAuth that our team developed for this purpose -- while it's not incredibly wide-spread, it's a viable way to defer credentials. Check out http://dev.twitter.com/pages/oauth_echo -- the docs are very Twitter-centric in this case, but the model can really be gener

Re: [twitter-dev] OAuth token lifetime

2011/4/23 yeohray : > If my app has used OAuth to log on, and can now send tweets, how long > can I use the token for?  Is it indefinite, or a set amount of time, > after which I have to repeat the OAuth logon process again? Hi, quote from the FAQ: How long does an access token last? We do not

Re: [twitter-dev] Oauth from iFrame

Hi Trevor, We make small security tweaks all the time -- IFRAMEs make it very difficult for the end user to verify the authenticity of twitter.com while they are entering their login credentials -- the user should always be able to clearly see the URL in the browser's standard representation of a

Re: [twitter-dev] oAuth Tweet of me api call Could not authenticate

Abraham! nice to see you here! I'm having problem with oAuth, experiencing always 401 not authorized.. did you have been reported about this error? any solution or tip/trick about this? Rgds -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:

Re: [twitter-dev] oAuth Tweet of me api call Could not authenticate

You are making the retweets_of_me request directly with cURL instead of with TwitterOAuth. You should do something like: $content = $connection->get('statuses/retweets_of_me'); Abraham - Abraham Williams | Hacker Advocate | abrah.am Just launched from Answerly

Re: [twitter-dev] OAuth Login Issues

Hey there, This happens now & then right now, even when you're doing everything correct -- it should be happening less frequently in the near future. Often a simple refresh of the authorize or authenticate page will correct the issue. If you're seeing the issue consistently and without fail, veri

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

Re: [twitter-dev] oAuth Authorization Header

The order of parameters in the Authorization header aren't required to match the base string order, but it's often simpler to debug if they do. The only requirements on the Authorization header is that it starts with "OAuth " and parameters are alpha-numeric, wrapped in quotes, and separated with c

Re: [twitter-dev] OAuth Token expires or no?

Tokens do not expire. Jan On Thu, Feb 3, 2011 at 6:32 PM, Lab Tech wrote: > I am developing an auto post app and last night it worked perfectly, > this morning however I am getting a 401 "Could not authenticate you." > error on both my app and the test file from the library > https://github.com/

Re: [twitter-dev] OAuth Token expires or no?

Correct, tokens don't expire. If you're getting that, either your calls are being sent incorrect or permission has been revoked. Scott. On 3 Feb 2011, at 17:32, Lab Tech wrote: > I am developing an auto post app and last night it worked perfectly, > this morning however I am getting a 401 "Coul

Re: [twitter-dev] OAuth 401 Unauthorized failure

Hi Brian, A couple of questions so we can investigate: 1. What was the response body content we returned with the 401? 2. What was the basestring you used? Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn wrote: > Hi

Re: [twitter-dev] oAuth reporting a status update error when none exists

It sound to me like your code might be making the same API request twice. This would result in the status getting posted and the error message you end up with. If you are commonly creating statuses with the same text it might just seem like a new status is getting posted when they are not. Abraha

Re: [twitter-dev] Oauth issue on iPhone Development - Multiple Users posting to Single Account with No UI

I have implemented this method: http://icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse Any idea on how to add the access token in this? Thanks a bunch. A On Oct 15, 2010, at 9:19 AM, Taylor Singletary wrote: > There's some background on this approach here: http://bit.ly/1t

Re: [twitter-dev] Oauth issue on iPhone Development - Multiple Users posting to Single Account with No UI

Is there any other direction- I have implemented the token, but it does not connect to a specific account. The token allows me to log on to any account through the application. I want to lock down the app to one specific account. Thank you for the help. A On Oct 15, 2010, at 9:19 AM, Taylor Si

Re: [twitter-dev] Oauth issue on iPhone Development - Multiple Users posting to Single Account with No UI

There's some background on this approach here: http://bit.ly/1token On dev.twitter.com we provide a feature that lets you easily get your own access token as the owner of the application. You then utilize that token whenever it makes sense to. We don't have an explicit Objective-C example of this

Re: [twitter-dev] Oauth issue on iPhone Development - Multiple Users posting to Single Account with No UI

Is there somewhere I can find documentation on this? Thanks again for the quick response. A On Oct 15, 2010, at 8:22 AM, Tom van der Woerdt wrote: > You can simply include the access tokens in the application. You don't > need anything else. > > Tom > > > On 10/15/10 5:43 AM, Anthony wrote:

Re: [twitter-dev] Oauth issue on iPhone Development - Multiple Users posting to Single Account with No UI

You can simply include the access tokens in the application. You don't need anything else. Tom On 10/15/10 5:43 AM, Anthony wrote: > I have be searching high and low to find out if Oauth will allow some > form of embedding the log-in info for a single account from the > iphone. I was using the b

Re: [twitter-dev] OAuth request token URL

you can refer to the demo program "gridtwit": http://code.google.com/p/gridtwit/ especially the files: "gridtwit_client_oauth_demo\Demo_Description.doc" and "gridtwit_client_oauth_demo\liboauth-0.9.1\tests\gridtwit.c" It details oauth authentication flow and coding(c++, liboauth). ---

Re: [twitter-dev] oauth and tokens what up with that?

you can refer to the demo program "gridtwit": http://code.google.com/p/gridtwit/ It details oauth authentication flow and coding(c++, liboauth). 2010/9/24 Taylor Sin

Re: [twitter-dev] oauth and tokens what up with that?

Hi Mike, We have a fairly easy path to acquiring an access token just for your own account/application combination. You can find out more about it at http://dev.twitter.com/pages/oauth_single_token Taylor On Thu, Sep 23, 2010 at 10:33 AM, Mike the Pike wrote: > require_once('twitteroauth.php')

Re: [twitter-dev] OAuth request token URL

Our system is quirky. There technically isn't a boolean flag set on an application that dictates whether it's a "web" or "desktop" application -- instead the boolean is a derived value based on the presence of a default callback URL. Think of this callback URL as a placeholder -- while it should ha

Re: [twitter-dev] OAuth request token URL

Yes, you can dynamically provide a callback URL, but you still need to enter one in the applications settings. Scott. On 23 Sep 2010, at 07:34, kengimel wrote: > Hi, > > I recently register my twitter application and obtained my OAuth > consumer credentials. > > However i noticed that when re

Re: [twitter-dev] Oauth problems?

You should encode the values in the Authorization: header. Tom On 9/10/10 11:50 PM, MTCoder wrote: > i have written code (working code for a client app) up to the point of > posting/reading to a twitter timeline. > The user has allowed my app access and i have the token and token > secret. > Als

Re: [twitter-dev] oAuth and applications that run in the background

Here is some more info about using an access token for a single account: http://dev.twitter.com/pages/oauth_single_token Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first

Re: [twitter-dev] oAuth and applications that run in the background

> I have an application (PHP script), that runs as a CRON job on a Linux > server. It uses cURL and basic authentication to retrieve users > profiles and statuses. > > Now that basic authentication is no longer supported, I need to switch > to oAuth, but with oAuth, there's a level of interactivit

Re: [twitter-dev] OAuth limit exceeded and error message reads 'Basic authentication is not supported'?

As far as I know, it's a known issue. Tom On 9/8/10 3:03 AM, Tim Haines wrote: > Hi guys, > > I haven't fully confirmed this is what's going on, but it appears an > account I use for doing only user/show calls, and ONLY via oauth is > getting some bad error messages. > > I think in this case t

Re: [twitter-dev] OAUTH on J2ME forums

On 9/6/10 11:46 AM, Amid Lad wrote: > hi all. > i'm building an application in j2me. > but, i get stuck on oauth. > should i get request token everytime user want to login ? > should user enter pin code everytime ? > should i get access token everytime ? > > if no, how to authenticate user ? shoul

Re: [twitter-dev] oauth verify credentials error

On Sat, 04 Sep 2010 20:55:19 +0200 Tom van der Woerdt wrote: > On 9/4/10 8:51 PM, Bernd Stramm wrote: > > On Sat, 04 Sep 2010 20:34:50 +0200 > > Tom van der Woerdt wrote: > > > >> On 9/4/10 8:13 PM, Bernd Stramm wrote: > >>> On Sat, 04 Sep 2010 19:02:11 +0200 > >>> Tom van der Woerdt wrote: >

Re: [twitter-dev] oauth verify credentials error

On 9/4/10 8:51 PM, Bernd Stramm wrote: > On Sat, 04 Sep 2010 20:34:50 +0200 > Tom van der Woerdt wrote: > >> On 9/4/10 8:13 PM, Bernd Stramm wrote: >>> On Sat, 04 Sep 2010 19:02:11 +0200 >>> Tom van der Woerdt wrote: >>> On 9/4/10 6:08 PM, rrd wrote: > I have a website which gets friend

Re: [twitter-dev] oauth verify credentials error

On Sat, 04 Sep 2010 20:34:50 +0200 Tom van der Woerdt wrote: > On 9/4/10 8:13 PM, Bernd Stramm wrote: > > On Sat, 04 Sep 2010 19:02:11 +0200 > > Tom van der Woerdt wrote: > > > >> On 9/4/10 6:08 PM, rrd wrote: > >>> I have a website which gets friends timeline by twitter api. I use > >>> oauth

Re: [twitter-dev] oauth verify credentials error

On 9/4/10 8:13 PM, Bernd Stramm wrote: > On Sat, 04 Sep 2010 19:02:11 +0200 > Tom van der Woerdt wrote: > >> On 9/4/10 6:08 PM, rrd wrote: >>> I have a website which gets friends timeline by twitter api. I use >>> oauth 1.0 My website worked without any problem in the last 1,5 >>> year, but from

Re: [twitter-dev] oauth verify credentials error

On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt wrote: > On 9/4/10 6:08 PM, rrd wrote: > > I have a website which gets friends timeline by twitter api. I use > > oauth 1.0 My website worked without any problem in the last 1,5 > > year, but from 1st September something changed. > > > > When

Re: [twitter-dev] oauth verify credentials error

On 9/4/10 6:08 PM, rrd wrote: > I have a website which gets friends timeline by twitter api. I use > oauth 1.0 My website worked without any problem in the last 1,5 year, > but from 1st September something changed. > > When I try to add a new user my app redirects me to the twitter oauth > authent

Re: [twitter-dev] OAuth Authentication & Authorization interchangeability?

The tokens you get back from authenticate and authorize are permanent and do not expire. They will continue to work unless the user revokes your application, you regenerate your applications consumer key/secret, or your application is deleted or suspended. The tokens you get back will be the same

Re: [twitter-dev] OAuth Authentication & Authorization interchangeability?

On 9/2/10 8:24 PM, Jonathan del Strother wrote: > Hi, > Our site offers cross-site logins using Twitter's authentication oauth > url, and also has post-to-twitter functionality using the > authorization url. To what extent are the tokens obtained from either > of these interchangeable? It seems l

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

Great. I'll take a look at the most recent version of the ruby gem as soon as I get a chance. >From my experience, 0.3.4 was a very solid release. I'll follow up when I've had a chance to review. Thanks, Taylor On Wed, Sep 1, 2010 at 2:38 PM, Damon Clinkscales wrote: > On Wed, Sep 1, 2010 at

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

On Wed, Sep 1, 2010 at 3:25 PM, Taylor Singletary wrote: > Hi Damon, > Verify that your application has a "default callback URL" set on your app's > page on dev.twitter.com -- the existence of that field is what determines > whether we'll automatically be sending you into out of band mode or note.

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

Hi Damon, Verify that your application has a "default callback URL" set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into out of band mode or note. Further, while that default callback URL needs to exist on your

Re: [twitter-dev] OAuth rate limit of 150

Hi Roger, It sounds like the OAuth part of your request isn't being seen by our servers. A rate limit of 150 will be reported whenever you make a request without authorisation. Can you share the code you are using to make the requests so we can see what might be going wrong? Thanks, Matt On Mon,

Re: [twitter-dev] OAuth/authentication language setting

Hi, It sounds like the language is being detected successfully as some of the text is translated, but also looks like we're missing some translations. I know in the bug report you explained which strings were in English and which were in French but could I ask you to provide a screenshot as well.

Re: [twitter-dev] Oauth "Incorrect signature" Error

On Wed, Aug 18, 2010 at 10:40:11AM -0700, Olu wrote: > Hi, I've been able to get a token and secret for an user but however, > I'm getting an error while trying to use the status/update call. I've > googled the problem and tried several solutions but none seems to > work. I'm not sure what the prob

Re: [twitter-dev] Oauth "Incorrect signature" Error

First guesses: your current implementation is incompatible for statuses containing space characters or non-alphanumeric characters. You are rawurlencoding your status parameter while building your signature base string.. which is correct -- except, you should have URL encoded your status value bef

Re: [twitter-dev] oauth friends_timeline request

On 8/16/10 10:34 PM, rustbucket wrote: > I'm in the middle of creating a twitter app using appcelerator, which > means I'm limited to javascript. Luckily I've managed to get > everything up and running using the oauth libraries available on > google code but I'm stuck on what is probably an obvious

Re: [twitter-dev] OAuth authentication issuse

On 8/16/10 6:41 PM, Jims wrote: > Hi guys, > > request":"/1/statuses/update.json","error":"Could not authenticate > you. > > I am trying to post a tweet to one of my accounts using oAuth, with a > script I wrote on PERL. I'm sending the request as a POST with the > required tokens in the header.

Re: [twitter-dev] OAuth Newb Question

Have a look at my PHP library TwitterOAuth. It is easy to get started on and supports just about everything. Feel free to ping me if you have any questions. http://github.com/abraham/twitteroauth Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects

Re: [twitter-dev] OAuth Newb Question

On 8/15/10 1:11 AM, artguillotine wrote: > I have an application already created in php that access' twitter. > There is a big switch to OAuth coming this week. How hard is it to > add OAuth to an existing application and is there any examples or > previous discussions in the groups? Do I have to

Re: [twitter-dev] OAuth + Whitelisting, transition questions

On 8/13/10 8:08 PM, Matt Trinneer wrote: > Hello, > > I'm curious to understand how the transition to OAuth will take place > for whitelisted accounts. Currently I have 2 streaming accounts, > which if I understand correctly will not be impacted at all, and a > whitelisted basic auth access (20k/

Re: [twitter-dev] OAuth and immediate redirect back to my site without questions

On 8/13/10 12:15 PM, Krot Vyacheslav wrote: > Hello, all! > I am a newbie to twitter api, so i have a simple question. I'm making > single sign on with twitter on my site. Everything works fine, but one > thing reallly annoyes me! If the client is signed in twitter and has > already granted access

Re: [twitter-dev] OAuth and impact on Twitter userbase / volume

On 8/13/10 4:31 AM, TheGuru wrote: > I'm curious to post this question to see if Twitter has fully thought > out the impact of forcing OAuth onto their API applications. While it > may appear to be a more secure method preferred in principle by users, > the fact of the matter is that one of the ma

Re: [twitter-dev] oauth API and application name

On 8/13/10 2:46 AM, Stan Miasnikov wrote: > Hi, > > I have implemented the oauth for a desktop application. The > application has been approved and I get the token back and also can > make HTTP requests using the token. However, when I post an update > using the app, it shows "...via API" instead

Re: [twitter-dev] OAuth and Hardware

One implementation option you have is to build only the portions of OAuth that you need to meet your goals. On dev.twitter.com we provide a feature that allows you to retrieve the access token for your own account, owning the application. You would then hard code this access token and your API keys

Re: [twitter-dev] OAuth and Hardware

On 8/11/10 6:30 PM, ERenken wrote: > So how can I use OAuth on a hardware device we are creating that > doesn't have a UI? Can I share the key between all the devices? This > is only twittering to 1 account that we have created. Seems like > OAuth is going to make stuff like this harder for peop

Re: [twitter-dev] OAuth Via AppleScript

On 8/11/10 5:52 PM, isaiah1112 wrote: > I have been developing a complete OAuth Library for Twitter in > AppleScript (I know, some people thought it was impossible but it > isn't). The trouble is, I can authorize OAuth and get my token and > secret from Twitter without any issues. However, once I

Re: [twitter-dev] OAuth singing on BlackBerry

Twittterapime is the only java me library for oauth 2010/8/9, Bess : > Is twitterapime the only OAuth lib for BB? > > Anyone is able to use Twitter4J / SignOAuth in BB J2ME? > > On Aug 7, 5:13 am, David Francisco Tavárez > wrote: >> Why don't you use twitterapime? >> >> 2010/8/7, BBTweet Media Pl

Re: [twitter-dev] OAuth singing on BlackBerry

Why don't you use twitterapime? 2010/8/7, BBTweet Media Player : > BB is J2ME but has some quirks that did not allow me to use the > library I tired. I am just handling the twitter communication on my > own. > > On Aug 7, 1:01 am, Bess wrote: >> You need Twitter to approve before you can use xAu

Re: [twitter-dev] oauth/request_token issue - 401 unauthorized

Hi Ivan, With OAuth you have to choose either to use header-based auth or query-string auth. Here you're doing both simultaneously. Your POST to api.twitter.com/oauth/request_token shouldn't include any of the oauth_* parameters. Also worth noting that the force_login=true parameter does not apply

Re: [twitter-dev] Oauth Echo Twitpic problems

Hi Gerard, Though I know it doesn't sound like it should matter, can you try your request against Twitpic after inserting spaces after each comma in your Authorization Header? Also want to make sure that you aren't executing your verify_credentials request in the preparation sequence (calling the

Re: [twitter-dev] OAuth and Streaming API

Kostya, the streaming API OAuth implementation should not have been affected. Are you still seeing these issues? If so, can you send me a message off list with connection details (the user making the request, the app the access token belongs to, the URL requested, the app being used)?    ---Mark

Re: [twitter-dev] OAuth, Stream API, desktop apps, general question

Desktop apps should be on User Streams, not on stream.twitter.com: http://apiwiki.twitter.com/ChirpUserStreams http://apiwiki.twitter.com/User-Stream-Implementation-Suggestions You should keep connections open as long as is practical and reduce connection churn to a minimum. -John Kalucki http:/

Re: [twitter-dev] Oauth rate status?

Hi, On Thu, Jul 15, 2010 at 05:52, johnw wrote: > In using the account rate status call, I only seem to get the basic > auth status back of 150 left.  Where can I get the oauth status (the > 350)? You need to authenticate with Twitter using OAuth. See the Authentication section of the documentat

Re: [twitter-dev] (OAuth) Favorite create and destroy malfunctioning, confirmed in Twurl

Yeah, this is a known error in the documentation on dev.twitter.com. The correct format for the command is: /1/favorites/create/:id.format and /1/favorites/destroy/:id.format Give those a try and you should find they work correctly. We have updates to the docs queued up for release this week. Th

Re: [twitter-dev] oAuth and callback function

In general, I recommend explicitly specifying your oauth_callback on the request token step, whether you're doing out of band auth or doing standard OAuth flows. If performing out-of-band auth, provide oauth_callback=oob. While there's nothing wrong with relying on what you've stored in your applic

Re: [twitter-dev] oAuth and callback function

check the config.php file if you defined the callback url there. On Wed, Jun 30, 2010 at 6:23 PM, EastSideDev wrote: > I changed the url for my callback function, and updated that > information in my application settings on the twitter API site. The > problem I am running into, is that I am sti

Re: [twitter-dev] oAuth and callback function

I've only done PIN based authentication, but, my understanding of the protocol was that you supply the callback url in your oauth request token call? Are you seeing that you are getting the old callback after updating the code in the request token step? George On Wed, Jun 30, 2010 at 9:23 PM, E

Re: [twitter-dev] Oauth Echo and Drupal

Hi Tim, I'm not familiar with the Drupal OAuth module, but can help you a little bit. Hopefully that module is a bit flexible in the different approaches you can use to perform OAuth with it. Essentially, you need to build a "mock request" that you won't actually execute against an endpoint at Tw

Re: [twitter-dev] oAuth for server-side applications

You're likely best served by taking the approach of implementing only the parts of OAuth you need to complete your single-user use case. (Highly recommend using a library). We provide a feature that makes it easy for you to get your own access token from dev.twitter.com, which you can hard code int

Re: [twitter-dev] oauth status update returning error 401 invalid / used nonce

xAuth in this case, I think, is unrelated to the issue. If you can use a different key and use the "my token" feature to get your access token, then try to tweet using that token, it will sufficiently express the problem I think. Taylor On Jun 11, 2010, at 2:48 PM, Craig wrote: > Hello, > > I h

Re: [twitter-dev] oauth status update returning error 401 invalid / used nonce

Based on another bug I've seen come up but have been unable to track consistently, can you try creating a new application and doing the oauth dance and then trying to make the status update again using the new keys and the new access tokens? Thanks! On Friday, June 11, 2010, Craig wrote: > Thank

Re: [twitter-dev] oauth status update returning error 401 invalid / used nonce

We have a few (difficult to pin down) edge cases where we throw a "bad nonce" error in an otherwise legit scenario -- often while we are under heavy amounts of load. Is this error consistent for you no matter what nonce you use? Do you know if your timestamp is aligned with the time indicated in

Re: [twitter-dev] OAuth Base String generation

Thanks for the clarification Taylor George On Fri, Jun 11, 2010 at 10:14 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > It kind of depends on how you tilt your head and look at it sometimes. > > One way of looking at it is that POST body elements already are URL-encoded > (at l

Re: [twitter-dev] OAuth Base String generation

It kind of depends on how you tilt your head and look at it sometimes. One way of looking at it is that POST body elements already are URL-encoded (at least when we're talking about "application/x-www-form-urlencoded" type bodies). When you send a POST request, you already must URL encode the body

  1   2   3   >