Goodreads Developers discussion
oauth questions
date
newest »


Oauth is confusing. I'd highly recommend using a library. Additionally, I'd recommend reading a guide like this one:
http://hueniverse.com/oauth/
herse a really simple example written in ruby:
http://www.goodreads.com/topic/show/4...


While it is difficult at first once you get it working it really relieves alot of stress for devs and end users. As a dev you don't really want to be storing and protecting usernames/passwords and as an end user I really don't want to give out my info to everyone.
OAuth seems to be the route alot of major sites are taking so I expect to see more of it.

I don't deny the benefits of OAuth and I think it is a great step on the security front for web applications. However, if you look at an example of working on a mobile phone it requires you to open up a browser and then intercept the response from the browser...kind of a pain. Now if there is a library in your programming language of choice that takes care of everything is great. However if you are working without a library it is a pain.
So I am not denying the benefits of OAuth but with desktop, and especially mobile applications, it is a real pain. I have seen at least one web service previously that used OAuth for other web applications but provided a traditional authenticate method for desktop/mobile devices.

XAuth is better alternative for mobile/desktop/mobile widget developer; I hope Goodreads will support XAuth soon.
I get a message "Invalid OAuth Request" From what I understand I should be getting a token using that URL and key but I don't seem to be able to...any feedback.