[twitter-dev] Problems with 2-legged access to Twitter using OAuth gem (ruby)

2010-09-09 Thread EranD
Hi, I'm trying to get a server app to tweet messages to one specific account I own. I'm following Twitter's instructions on Twitter's wiki: http://developer.twitter.com/pages/oauth_single_token#ruby I can read information from twitter (e.g. get last 20 tweets), but when I try to update my status

[twitter-dev] Re: Problems with 2-legged access to Twitter using OAuth gem (ruby)

2010-09-09 Thread EranD
x27;ve pasted here has a mis-spelled key name for ":oauth_token" > (you've provided "oath_token" -- is this true of the code you are executing > as well? > > I haven't personally tested the 0.4.3 version of the Ruby gem, but have had > ongoing affect

[twitter-dev] Re: Problems with 2-legged access to Twitter using OAuth gem (ruby)

2010-09-09 Thread EranD
oken.get("/statuses/update.xml" has two problems... > > 1. should have the version slug added in.. /1/statuses/update.xml > 2. creating a status update requires the POST HTTP method (as opposed to > GET) > > You're very close, provided everything else is working corr

[twitter-dev] Re: Problems with 2-legged access to Twitter using OAuth gem (ruby)

2010-09-09 Thread EranD
Very strange. The token and access keys were all created yesterday by twitter. Swithcing to gem 0.3.6 didn't help either. On Sep 9, 5:08 pm, Tom van der Woerdt wrote: > Invalid/Expired token says it all.. > > Tom > > On 9/9/10 11:00 PM, EranD wrote: > >

[twitter-dev] Re: Problems with 2-legged access to Twitter using OAuth gem (ruby)

2010-09-09 Thread EranD
Very strange. The tokens and keys were generated by Twitter yesterday and still seem to be valid in the app interface. Switching to gem v0.3.6 did not help. On Sep 9, 5:08 pm, Tom van der Woerdt wrote: > Invalid/Expired token says it all.. > > Tom > > On 9/9/10 11:00