Great question. Our UI makes this choice very confusing, and we're actively thinking of ways to improve it.
The answer depends on the type of authorization you're using on iOS. If you're doing a standard redirect-with-OAuth flow, where you're perhaps redirecting to a custom URI scheme like yourapp://, then you should choose the "web" type and enter a placeholder callback URL -- likely just a link to your site. This placeholder must be there, because the form itself won't accept a custom URI scheme. No matter what kind of OAuth you're doing, you should always provide an explicit oauth_callback on the request token step. If you're doing an out-of-band/PIN code flow, then you'll want to select the "app" mode. This allows you to send oauth_callback=oob on the request token step, and our system will reject any other oauth_callback value. This is a lock-down mode. If you're doing xAuth but using a key that may be also using standard OAuth, you'll want to select web and provide a placeholder callback URL. If you're doing xAuth and are sure there's no other way you'll be authenticating users, select "app" mode to lock down. Thanks, Taylor On Mon, Jan 24, 2011 at 6:34 AM, Rob Wilson <netp...@gmail.com> wrote: > Hi, > > When I registered my application with Twitter, I was asked whether it was > an application, or website. The latter required a URL callback. > > I tried to select website with 'oob' as the callback URL (as seen in the > documentation notes), but the registration form rejected oob as an invalid > callback URL (seems fair enough - it's not a URL). > > I'm left wondering, are iPhones apps to be registered as application or > web? If the latter, what URL should be used? > > Cheers, > Rob. > > > -- > > > Please visit... > > SpikyOrange.co.uk <http://spikyorange.co.uk/> A portal for anything I > create, including... > > BitBanter.com <http://bitbanter.com/> A technical podcast 50% Tech + 50% > software development = 100% Entertaining! > > > > <http://spikyorange.co.uk/> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
