On further consideration, I really believe that twitter itself should do this, given that you set the callback when you're creating/editing the application AND you set it to "browser". It appears to me as if these options are purely cosmetic. I shouldn't have to set the callback when Twitter already knows what that callback is!
----- Ryan Bigg Mocra - Premier iPhone and Ruby on Rails Consultants w - http://mocra.com e - [email protected] p - +61 432 937 289 or +61 7 3102 3237 skype - radarlistener On 18/06/2009, at 6:36 PM, Lachlan Hardy wrote: > > I'm using the OAuth gem, but I had a similar problem. > > You need to ensure you are specifying the oauth_callback in your > request. > > eg @request_token = @consumer.get_request_token(:oauth_callback => > "http://example.com/auth";) > > instead of > > @request_token = @consumer.get_request_token
