What's the problem with oauth_callback? The service providers don't support OAuth 1.0a?
A consumer can work with a mixture of service providers that support 1.0 and 1.0a, by sending an oauth_callback parameter when requesting a request token, and examining the response. If the response doesn't contain oauth_callback_confirmed=true, the service provider doesn't support 1.0a; so the consumer should add an oauth_callback parameter when redirecting the user to the service provider. The Accessor Secret extension is not supported by any service provider I know. And I think it's not applicable here, since there's no trusted server to hold the consumer secret. On Sep 23, 3:23 am, "Carl H." <charr...@gmail.com> wrote: > brightkite is not working due to the lack of support for > oauth_Callback on their side. Jaiku does not work either as > they don't support callback. MySpace and twitter should work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---