example.go is broken

[gladimdim]

I'm trying to use your package and compile example.go file.

However I got such compile errors for such Go version:
8g -V: 8g version 7002

Compile errors:
8g example.go
example.go:100: cannot use AT (type *oauth.AccessToken) as type oauth.Params in function argument
example.go:100: not enough arguments to function call
example.go:131: cannot use AT (type *oauth.AccessToken) as type oauth.Params in function argument
example.go:131: not enough arguments to function call

[gladimdim]

This was fixed by adding "nil" as seconds parameter for lines 100 and 131.

But another issue was found: after clicking "Sign In" page redirects to twitter's get access token page but with empty oauth_token:

https://api.twitter.com/oauth/authorize?oauth_token=

If CallBackUrl is not set for goauthcon, then oauth_token is generated but as I understand there is no functionality in your lib to proceed with twitter's VIN number.

[hokapoka]

Hi there

Sorry I modified the Get after making some changes to make the Consumer work with Google's Oauth tokens that were getting mangled, and didn't update the example although I did point it out in the readme file.

I've also not tested it with the twitter since making the changes to work with Google, it could be that the fixes I made to work with Google's Tokens have effected the twitter example.

I'll try to test it out and make any nessasary fixes.

As for entering the VIN number from twitter, no I've not made any provision for not using a callback, although would be very simple to add.

I'll add another example package that works with Google Buzz right now.

Thanks.

[hokapoka]

I've added a 2nd example, example_buzz that is a working example, if you change the respective consumer details.

I'll have another look at the Twitter example now.

[hokapoka]

I have just tested the original example after modifying the example.go to pass the new params and everything worked flawlessly.

My tests show that if you haven't changed the ConsumerKey & ConsumerSecrect, as well as the CallBackURL with relavant value you will be redirected to the URL that you cited above, where there's no token passed.

Maybe this should be caught by the Consumer, but either way you need the correct details poipulated before it will work for you.

I'll will look into what is necessary to change the Authorization methods so that it can be used in a console or other rather than using a http service to redirect the user. It appears that it's a relatively minor change.