On Fri, Jul 9, 2010 at 3:38 AM, Fabien Penso fabienpe...@gmail.com wrote:
Where my application http://twitter.com/apps/edit/14088 has readwrite
access permission.
This is fixed, what happened :
- My application had read-only access for the user (myself in fact), I
revoked access and asked for
On Wed, Jun 16, 2010 at 9:39 PM, Craig chanson9...@gmail.com wrote:
By the way, even when I try to tweet with just one word like: tweet,
it doesn't work. Just simple ascii characters. Is there any way you
can just intercept one of my test tweets and look at what, if anything
might be going
On Fri, Jul 9, 2010 at 3:24 AM, Fabien Penso fabienpe...@gmail.com wrote:
On Wed, Jun 16, 2010 at 9:39 PM, Craig chanson9...@gmail.com wrote:
By the way, even when I try to tweet with just one word like: tweet,
it doesn't work. Just simple ascii characters. Is there any way you
can just
Hi James,
It sounds like you have the correct information for your application. As you
are using your own personal access token and secret you don't need to be
doing any of the OAuth authorization steps, but you do need to sign any
request you make.
Are you using any PHP libraries to help you
Hi Craig, Taylor,
did you guys ever figure out what the problem was? I am having a very
similar issue to Craig.
I am trying to post a status update to Twitter from a server-side PHP
app. More specifically, it is to automatically tweet updates from a
news site I help develop.
I'm using all the
On Jun 30, 2010, at 14:32 , James Ford wrote:
One thing I'm perhaps not clear on, do I need xAuth for this to work?
You do need to get the access token somehow. That is what xAuth provides you.
That said, you sound like you are a server app. Twitter doesn't support xAuth
for server apps.
Thanks for the response.
I am using the consumer key and secret found here:
http://dev.twitter.com/apps/my
app id number
And the access token and secret found here: http://dev.twitter.com/apps/my
app id number/my_token
No joy.
On Jun 30, 9:47 pm, Andrew W. Donoho andrew.don...@gmail.com
Hi Matt,
Thanks for responding. My authorization header is still the same as
it was in my first message above. Here it is for another request I
just tried:
OAuth oauth_nonce=TEeSMm8q3m5abhmppain, oauth_signature_method=HMAC-
SHA1, oauth_timestamp=1276701304,
Hi Craig,
Do you know if the status update, status=my%20tweet is being encoded
correctly in your signature base string (which is the string used to create
your signature).
For the signature base string, the key/value pair would look like:
status%3Dmy%2520tweet
Have you tried your xAuth
My signature base string status pair looks like:
status%3Dmy%2520tweet
When I tried xAuth authentication with a * character in the password,
it didn't work at first. But once I double url encoded it, I was able
to authenticate no problem. So that definitely helps. I am now
double url encoding
By the way, even when I try to tweet with just one word like: tweet,
it doesn't work. Just simple ascii characters. Is there any way you
can just intercept one of my test tweets and look at what, if anything
might be going wrong on the server side?
-Craig
On Jun 16, 3:05 pm, Craig
I am in read/write mode.
I tried posting to two different twitter accounts without luck...my
dev account, where I know what the access secret and token is supposed
to be and another one I just created. I know my access token and
secret are being stored correctly and I believe they are being used
I agree that it's the wrong error. We have a new, better implementation of
OAuth waiting in the wings that's going to be much more helpful in this
regard.
I'm still trying to rule out some possibilities. Can you try and create a
new application, then grab the access token from the my access token
Just tried it. Same error. So at least that rules something out...
-Craig
On Jun 16, 5:19 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
I agree that it's the wrong error. We have a new, better implementation of
OAuth waiting in the wings that's going to be much more helpful in
Can you follow up with me off the list and I'll help you out tomorrow? We'll
need to compare signatures and work with me knowing your application
secrets. There's something subtle going on.
Taylor
On Wed, Jun 16, 2010 at 3:22 PM, Craig chanson9...@gmail.com wrote:
Just tried it. Same error.
Hey Craig,
Could you let us see what the authorization header you are sending
looks like (obfuscating your oauth keys and secrets)?
What you're aiming for is a header similar to this:
POST /1/statuses/update.xml HTTP/1.1
Accept: */*
Connection: close
User-Agent: OAuth gem v0.4.0
Content-Type:
No dice. I just tried creating a new app and using the new keys/token
to tweet. I'll go over my steps once more and see if I can track down
an issue somewhere...
On Jun 11, 8:53 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
xAuth in this case, I think, is unrelated to the issue.
Ok, so I believe my signature is correct because if I take out the
oauth_token parameter from the signature base I get an incorrect
signature error instead of the invalid/used nonce error. I am
definitely posting to the correct url: https://api.twitter.com/1/
statuses/update.xml because if I
Thanks for your quick reply! This error occurs consistently no matter
what nonce I'm using. My timestamp appears to be aligned with the
time from your response. I also tried a different nonce scheme and
that didn't seem to work either.
Here is my post body:
status=My%20Tweet
I just attempted
Sure I can do that, althought I'll have to get approved for xAuth on
that application as well. Will I have to request xAuth again?
Thanks,
Craig
On Jun 11, 8:10 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Based on another bug I've seen come up but have been unable to track
20 matches
Mail list logo
