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
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 taykni...@gmail.com 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
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 taykni
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.
=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
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
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
