Just to show you how they care about compat. http://forum.developers.facebook.com/viewtopic.php?pid=250804#p250804
Twitter also claimed they were going on beta test OAuth2.0 before summer, asked about status of things, I had no answer. I guess it is not first in their schedule... We could eventually go back to an auth module just for facebook and their proprietary protocol :( mic 2010/8/29 Michele Comitini <[email protected]>: > Hi Narendran, > > Thanks for testing. > > If you can send a path I'll be happy to include it, I will take care > of trying to keep > compatibiltity, but do not worry much about it, since FB claims > oauth2.0 (which is still a draft) compat, but > they do not follow the spec in too many points, they are also stuck > into a preliminary draft revision of the protocol, > something like v2 while now the ieft draft is at v10. > > mic > > > 2010/8/29 Narendran <[email protected]>: >> Hello, >> I'm using the latest Facebook oauth module specified in this thread: >> http://groups.google.com/group/web2py/browse_thread/thread/a5d981ad6f2174e9/f0e9505ced78c653?lnk=gst&q=narendran#f0e9505ced78c653 >> >> I'd like to request access to extended user profile (email address and >> other info) during authentication, and looks like in order to do that, >> scope parameter has to be encoded in the auth url. >> >> Has anyone done this? What is the clean way of doing that? I'm right >> now modifying oauth_account.py to pass scope as a parameter to init >> function. But I'm worried that it may not work for other oauth >> implementations. >> >> -- >> Thanks >> Narendran >
