Re: A Problem with the web view. [was: Re: [twitter-dev] Please confirm this OAuth flow ...]

Hi Andrew, On May 27, 2011, at 7:02 AM, Andrew W. Donoho wrote: > My question: Am I in error? Does Twitter return a different callback value > for the "No, Thanks" case. If not, I humbly request that Twitter add this > important, for a better user experience, notification. We actually do have

A Problem with the web view. [was: Re: [twitter-dev] Please confirm this OAuth flow ...]

Gentlefolk, There is a problem with the web view/three legged OAuth mechanism. The OAuth sign-in mechanism gives no indication to either the browser or an embedded web view that the user has pressed "No, Thanks". In both login methods, our app is left hanging in the middle of

Thank You! [was: Re: [twitter-dev] Please confirm this OAuth flow ...]

On May 20, 2011, at 04:11 , Tom van der Woerdt wrote: > I don't work for Twitter - let's get that cleared up first. Mr. Harris does. Tom, Please accept my apologies. As you were so helpful and provided such detailed advice, I assumed you were tracking this list as an employee of Twi

Re: [twitter-dev] Please confirm this OAuth flow ...

On 5/20/11 6:36 AM, Andrew W. Donoho wrote: Tom, Thank you for your answers. As I read other threads, I am finding ambiguity reemerging. Pardon my pedantry, I want to nail this down correctly the first time. As you know, I have a hard deadline to get these fixes implemented and deployed.

Re: [twitter-dev] Please confirm this OAuth flow ...

Tom, Thank you for your answers. As I read other threads, I am finding ambiguity reemerging. Pardon my pedantry, I want to nail this down correctly the first time. As you know, I have a hard deadline to get these fixes implemented and deployed. It appears that there is a diff

Re: [twitter-dev] Please confirm this OAuth flow ...

Abraham, I am not in the least interested in arguing, my point being that our differing subjective interpretations are meaningless. Since this isn't a statute, we needn't spend endless hours teasing the intent out of it, we can just ask the guys who wrote it what they meant. As we have now do

Re: [twitter-dev] Please confirm this OAuth flow ...

On Thu, May 19, 2011 at 08:18, hax0rsteve wrote: > > 1) it isn't > Ask users if they know that JavaScript can be inserted into UIWebViews that can read their password and I think you will find most of them will be surprised. > C) it doesn't > > Twitter.com is being framed within the applicatio

Re: [twitter-dev] Please confirm this OAuth flow ...

Appliances. I've been quite excited for quite a while now about Twitter's possibilities in "the Internet of things". Imagine, for instance, wall sockets that tweet their power consumption. Bathroom scales that tweet your weight. We've started talking to chip manufacturers about the development pr

Re: [twitter-dev] Please confirm this OAuth flow ...

An Arduino. And yes, that's a vanishingly small minority of of users. #imaginationfail On 19 May 2011, at 16:20, Tom van der Woerdt wrote: > Can you name a modern device on which people will want a client with access > to direct messages, without a webbrowser? I can't. > > Tom > > > On 5

Re: [twitter-dev] Please confirm this OAuth flow ...

> Can you name a modern device on which people will want a client with > access to direct messages, without a webbrowser? I can't. A terminal? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@flo

Re: [twitter-dev] Please confirm this OAuth flow ...

Can you name a modern device on which people will want a client with access to direct messages, without a webbrowser? I can't. Tom On 5/19/11 5:17 PM, Adriaan Pelzer wrote: Understood. In other words, there is no way to consume the authenticated parts of the Twitter API on devices without web

Re: [twitter-dev] Please confirm this OAuth flow ...

1) it isn't C) it doesn't Of course, it depends how you read it. But what really matters is what Twitter intended when they wrote it. +1 for an official twitter comment please. On 19 May 2011, at 16:13, Tom van der Woerdt wrote: > http://dev.twitter.com/pages/api_terms -> II. Principles ->

Re: [twitter-dev] Please confirm this OAuth flow ...

Understood. In other words, there is no way to consume the authenticated parts of the Twitter API on devices without web browsers anymore? This severe limitation will haunt Twitter in future, without a doubt. Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds

Re: [twitter-dev] Please confirm this OAuth flow ...

http://dev.twitter.com/pages/api_terms -> II. Principles -> 1. Don't surprise users -> C. Your application should not: -> replicate, frame, or mirror the Twitter website or its design. Tom On 5/19/11 5:10 PM, hax0rsteve wrote: Tom, Could you clarify : If using a web view is against the To

Re: [twitter-dev] Please confirm this OAuth flow ...

On May 19, 2011, at 9:53 AM, Tom van der Woerdt wrote: > Also, don't display it in a WebView, use the normal browser instead and use a > callback URL with a custom scheme - for example myapp://. Let the browser > redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty > su

Re: [twitter-dev] Please confirm this OAuth flow ...

Tom, Could you clarify : If using a web view is against the ToS, could you state which section ? And if "it soon will be" (which conflicts with the above), what makes you think so ? Did I miss something ? Also, if someone from the Twitter team could confirm either of these, this would be mu

Re: [twitter-dev] Please confirm this OAuth flow ...

Like I mentioned in my post - use the actual browser which includes an address bar (that's what it's about - without the address bar the user doesn't know it's actually twitter.com and you might just as well use xAuth, lol). Use a callback URL which includes a custom scheme (myapp://oauth_redir

Re: [twitter-dev] Please confirm this OAuth flow ...

If using a UIWebView is against the TOS, how should app developers (standalone apps, that is) authenticate without xauth, in the light of yesterday's announcements? Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds http://www.wewillraakyou.com

Re: [twitter-dev] Please confirm this OAuth flow ...

1. Yep 2. NO. There's no difference in oauth/authorize and oauth/authenticate, except that authenticate will simply pass the "accept/deny" screen if the user has already accepted the app. Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom s

[twitter-dev] Please confirm this OAuth flow ...

Gentle Twitter Support Folks, There is an ambiguity in the OAuth flow for mobile devices. As I now have little time to move from xAuth to OAuth, I would appreciate it if Twitter Support would confirm the following OAuth flow which uses your routes. 1) Use "POST oauth/request_token" to g