I won't recommend using oAuth for desktop clients. This requires you to store your client secret in the app, rendering your users' Twitter accounts vulnerable.
Adriaan Pelzer RAAK putting you in touch with your crowds http://www.wewillraakyou.com twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Mon, Oct 25, 2010 at 9:33 PM, Tom van der Woerdt <i...@tvdw.eu> wrote: > xAuth is an extension to OAuth. OAuth is for both desktop and web > clients, while xAuth is only for desktop clients. > > Tom > > > On 10/25/10 10:29 PM, Adriaan Pelzer wrote: > > Agreed, xAuth is mainly for desktop clients. oAuth mainly for web > clients. > > > > And you don't use HTML with oAuth. You choose between XML or JSON. It > > gets served via HTTP (RESTful API), but no HTML involved. > > > > This is a perfect problem for C/C++ > > > > Adriaan Pelzer > > RAAK > > putting you in touch with your crowds > > http://www.wewillraakyou.com > > twitter: http://www.twitter.com/adriaan_pelzer > > linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ > > skype: adriaan_pelzer > > +4478 7978 1743 > > > > > > > > On Mon, Oct 25, 2010 at 9:14 PM, Jim Cortez <j...@jimcortez.com > > <mailto:j...@jimcortez.com>> wrote: > > > > Use xAuth: http://dev.twitter.com/pages/xauth > > No web server required. > > Jim > > > > > > On 10/25/10 12:28 PM, Keiya Bachhuber wrote: > > > > Is the next version of twitter going to be written in C++ and > > use GTK+ > > for rendering? Because that's what you're asking desktop > > developers to > > do by forcing OAuth. I have to include a web server in my app to > > work > > with twitter? What the hell! It's probably simpler just to > > pretend to > > be Chrome or Firefox. Seriously. Working through the mess that > > is HTML > > (any HTML, not just yours) is easier than getting the nice clean > > feeds. > > > > Good job. You made me hate you. > > Keiya. > > > > > > -- > > 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 > > -- > 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
