http://groups.google.com/group/twitter-development-talk/browse_thread/thread/98def90952bdab9c
On Sun, Mar 1, 2009 at 17:57, Sam K Sethi <samkse...@googlemail.com> wrote: > Hi > > I wonder if there is any value in twitter supporting the openid/oauth > hybrid extension > http://googledataapis.blogspot.com/2009/01/bringing-openid-and-oauth-together.html > > This would allow us 3rd party developers to create a login mechanism for > our own sites but wrap the Authentication and Authorisation request up in > one call to twitter but I guess this requires twitter to support openid. > > Thanks in advance > > Sam > > www.twitblogs.com/ssethi > > This email is: [ ] bloggable [ ] twittable [ ] ask first [X] private > > > Sent from: Poplar Eng United Kingdom. > > 2009/3/1 Paul Kinlan <paul.kin...@gmail.com> > > Hi Sam, >> >> I think most things other than a basic username and password will confuse >> most people, which is why asking for their twitter username and password is >> done (rightly or wrongly) because people know it, use it all the time on >> twitter and don't have to remember yet another password. >> >> I will give JainRains solution a look over. Trouble is, it looks two >> phase, log-in via openId/facebook/etc then hook up your twitter account >> (using oAuth); obviously once you have set up your twitter account your only >> ever have to log in using the JainRain stuff. I do like using the twitter >> account and password (like many app developers) because its central, you can >> verifiy the details and let people use your service in one simple step and >> you don't need another external sevice to authenticate against. I just >> worry that using external services will limit who uses Twitter apps, and I >> also worry that managing the credentials myself will negate all the benefits >> that oAuth provides (because most people will use the same password as their >> twitter password). >> >> On http://oauth.twe2.com you only ever type anything when you are >> redirected to Twitters site, twe2 doesn't ask for anything ever. In my >> opinon it is the cleanest thing from a UX point of view, however, it's not >> (from what I have been told) how your supposed to use oAuth. >> >> Paul. >> >> 2009/3/1 Sam K Sethi <samkse...@googlemail.com> >> >>> Hi Paul >>> >>> >>> As you know we already have a working version of Twitters OAuth on a test >>> site http://ouath.twitblogs.com and will integrate into our live site >>> when twitter let us. The way we are looking to overcome the user login >>> issue is to use JainRain's www.rpxnow.com and associate a users ID to >>> their OAuth token. >>> >>> Our worry is will this all confuse non-technical users >>> >>> Thanks in advance >>> >>> Sam >>> >>> www.twitblogs.com/ >>> >>> This email is: [ ] bloggable [ ] twittable [ ] ask first [X] private >>> >>> >>> 2009/3/1 Dossy Shiobara <do...@panoptic.com> >>> >>> >>>> On 3/1/09 1:28 PM, Petermdenton wrote: >>>> >>>>> >>>>> Dossy, serioulsy, no one is saying the sky is falling. This list is for >>>>> application developers to discuss development topics as they please. >>>>> You >>>>> may know everything, but for those of us who wish to discuss >>>>> >>>> >>>> We need to resist spreading FUD. Twitter has its problems, but creating >>>> ones where there aren't any helps no one. >>>> >>>> >>>> -- >>>> Dossy Shiobara | do...@panoptic.com | http://dossy.org/ >>>> Panoptic Computer Network | http://panoptic.com/ >>>> "He realized the fastest way to change is to laugh at your own >>>> folly -- then you can let go and quickly move on." (p. 70) >>>> >>> >>> >> > -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison Wisconsin United States.
