[twitter-dev] Re: oauth just to post status
I meant to add, I want to use oauth for this so I get the 'via DummyOauthApp' line in the tweet. On May 13, 9:50 pm, tayknight wrote: > Hi all. My app, once it gets going, is mainly going to post status > updates as mentions to followers. For instance, the app, called > DummyOauthApp will post a statuses/update like '@tayknight blah blah > blah'. > > So, i don't need my app to authenticate itself to oauth as tayknight, > but as itself DummyOauthApp. Does this mean I need to generate an > access token/secret pair for the app itself and continually reuse this > pair to call statuses/update? > > Thanks.
[twitter-dev] oauth just to post status
Hi all. My app, once it gets going, is mainly going to post status updates as mentions to followers. For instance, the app, called DummyOauthApp will post a statuses/update like '@tayknight blah blah blah'. So, i don't need my app to authenticate itself to oauth as tayknight, but as itself DummyOauthApp. Does this mean I need to generate an access token/secret pair for the app itself and continually reuse this pair to call statuses/update? Thanks.
[twitter-dev] Re: 401: Unauthorized application or token on friendship/exists
Well, I feel like a moron. Thanks for the help. Sorry to have asked you to spend time on something so ridiculously simple. On Apr 30, 11:04 am, Abraham Williams <4bra...@gmail.com> wrote: > friendships/exists.json > *not* > friendship/exists.json > > > > On Tue, Apr 28, 2009 at 11:06, tayknight wrote: > > > I'm fairly sure I'm getting a proper token. Using the page > >http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.htmlI > > get the same signature as in my failing url. > > > GET looks like: > >http://twitter.com/friendship/exists.json? > > oauth_consumer_key=Rg4VBVUvAoThpl78duF3Rg > > &oauth_nonce=375494971125145587 > > &oauth_signature=xWCdscsa6I4GJphDIQAnsDmjyhM%3D > > &oauth_signature_method=HMAC-SHA1 > > &oauth_timestamp=1240933535 > > &oauth_token=765803-e2mAy2wkQy4wRI9LQC73cZwbiwmmJ7mZJh04MZiWk > > &oauth_version=1.0 > > &user_a=tayknight > > &user_b=wxtweet<http://twitter.com/friendship/exists.json?%0Aoauth_consumer_key=Rg4VB...> > > > I must be missing something obvious. Other GETs work. I can provide > > secrets to TwitterAPI folks if they want to help debug. > > > Thanks. > > -- > Abraham Williams |http://the.hackerconundrum.com > Hacker |http://abrah.am|http://twitter.com/abraham > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, WI, United States
[twitter-dev] 401: Unauthorized application or token on friendship/exists
I'm fairly sure I'm getting a proper token. Using the page http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html I get the same signature as in my failing url. GET looks like: http://twitter.com/friendship/exists.json? oauth_consumer_key=Rg4VBVUvAoThpl78duF3Rg &oauth_nonce=375494971125145587 &oauth_signature=xWCdscsa6I4GJphDIQAnsDmjyhM%3D &oauth_signature_method=HMAC-SHA1 &oauth_timestamp=1240933535 &oauth_token=765803-e2mAy2wkQy4wRI9LQC73cZwbiwmmJ7mZJh04MZiWk &oauth_version=1.0 &user_a=tayknight &user_b=wxtweet I must be missing something obvious. Other GETs work. I can provide secrets to TwitterAPI folks if they want to help debug. Thanks.
[twitter-dev] Re: Friendship Create
Hey, Paul. I'm bumping my head against a similar thing in friendship/ exists (which is a GET request, and I'm getting a 401 error, not 500). I know the parameters have to be sorted for signature creation. But the OAuth spec docs seem to contradict if they have to be sorted in the actual request. In [1] is seems to say they have to be. But in [2], is clearly shows they aren't sorted lexigraphically. Matt, I'd love to have some clarification on this. Thanks to both of you. [1] http://oauth.net/core/1.0/#sig_norm_param [2] http://oauth.net/core/1.0/#anchor30 (please see A.5.3. On Apr 27, 4:52 pm, Paul Kinlan wrote: > I have just checked the library and whilst it sorts the keys, I don't think > it sorts the library sorts actual query string when it makes the request. I > will have to check that bit out. > > Paul. > > 2009/4/27 Dossy Shiobara > > > > > On 4/27/09 5:29 PM, Paul Kinlan wrote: > > >> Bellow is an example query. > > >>http://twitter.com/friendships/create.xml?screen_name=twollo&oauth_no... > > > "s" comes after "o". > > > OAuth 1.0 specification mandates the parameters be sorted when the > > signature is computed. Are you doing this? > > > Also, getting HTTP 500 Server Error ... I ran into that when I was using > > HTTP Authorize header authentication and didn't "Parameter Encode" the > > signature. > > > -- > > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > > Panoptic Computer Network |http://panoptic.com/ > > "He realized the fastest way to change is to laugh at your own > > folly -- then you can let go and quickly move on." (p. 70) > >
[twitter-dev] Re: getting an error about read-write access. Why?
Thanks. That got it. Once i started sending oauth_access_type everything worked. Did I miss this somewhere in the API docs? On Apr 27, 10:32 am, Matt Sanford wrote: > Hi there, > > Did you recently change the application from Read to Read/Write? > The error message is a little misleading since R/RW is now on a per- > token basis [1]. I suggest re-authorizing the user and see if the > error continues. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://code.google.com/p/twitter-api/issues/detail?id=302 > > On Apr 26, 2009, at 10:34 PM, tayknight wrote: > > > > > My OAuth application, in 'Edit Application Settings' shows 'Read & > > Write' is checked. Yet, when I try an api method that requires POST, > > I'm getting a 401 "error":"Read-only application cannot POST". Why > > would this be? Neither the user making the request nor the OAuth app > > have their status set to protected. > > > Thanks for the help. > >
[twitter-dev] getting an error about read-write access. Why?
My OAuth application, in 'Edit Application Settings' shows 'Read & Write' is checked. Yet, when I try an api method that requires POST, I'm getting a 401 "error":"Read-only application cannot POST". Why would this be? Neither the user making the request nor the OAuth app have their status set to protected. Thanks for the help.
