If my understanding is correct, the only way you can imitate Facebook
connect when using Twitter OAuth, is to scrape the Twitter login page
and authorization page and hide them from the user, i.e., login on
behalf of the user, and authorize on behalf of the user, assuming that
you first ask the user for his Twitter username and password (which
side-steps one of the major proclaimed benefits of OAuth in that the
user never has to give his credentials to your app).
I think Twitter will bitch-slap you if you do that.
On Sep 29, 9:45 pm, "joeygreen...@gmail.com" <joeygreen...@gmail.com>
> I'm implementing both facebook connect and Twitter+Oauth for an
> iPhone app I'm currently working on. I really like the way facebook
> connect makes it seem that you're still in the app and not visiting
> some external website. Also, it kind of messes with the flow of my app
> because when you sign into facebook connect you have this snappy
> interface and when you sign into Twitter+Oauth you can really notice
> that you're being redirected to a website.
> So, what I'm wanting to do is make my Twitter+Oauth process be more
> like, if not identical, to how facebook connect works. My question is,
> does the user need to know that they are going to twitter to login?
> Most users are probably unaware that they are using a webpage when
> they are using facebook connect.
> In my scenerio, would it be better to imitate the facebook connect
> experience or just keep it where you know you're being sent to twitter?