[twitter-dev] Re: Which one are you using in your mobile app? xAuth or oAuth?

[James Abley]

On Jul 9, 8:01 am, Bess bess...@gmail.com wrote:
 So far I only learn of one Twitter-based app is using OAuth - Twitter
 official app (not sure it is out in app store yet).

 I personally like to learn the best practice on OAuth and best OAuth
 library used in iPhone, Android, Nokia and Blackberry.

+1

We have some existing apps (iPhone / iPad and Android) that use Basic
Auth and are migrating to OAuth. I'm guessing that Twitter for iPhone
uses xAuth - I didn't have to enter a PIN or allow the app via a web
UI.

Some additional examples would be nice.

Cheers,

James


 On Jul 7, 10:19 am, Oscar Cortes ocort...@gmail.com wrote:



   Thanks for the feedback Rich.  I didn't know that the embedded web
  browser could be used for this. Can someone point me out to an iPhone
  or iPad app that uses oAuth with the embedded web browser? I would
  like to try it out.

  Oscar

  On Jul 6, 6:28 pm, Rich rhyl...@gmail.com wrote:

   We are using oAuth on the iPhone. It works great and I don't see why
  xAuthshould be allowed on iPhone as the embedded web browser is more
   than capable

   On Jul 6, 8:55 pm, Oscar Cortes ocort...@gmail.com wrote:

We are about to integrate Twitter support in our iOS library and we
are seeing that some devs preferxAuthover oAuth? Which one are you
using and why? Does Twitter push for one of them more?

Thanks

[twitter-dev] Re: Posting a status update to the Mobile version of Twitter

[James Abley]

Just to confirm my understanding, is clickjacking not an issue when
using http://twitter.com/ but it potentially is when using http://m.twitter.com/
?

Can you suggest what the preferred way to provide this type of easy-
linking functionality might be for mobile?

Cheers,

James

On Mar 3, 11:15 pm, Alex Payne a...@twitter.com wrote:
 In order to prevent clickjacking attacks, we had to disable this 
 functionality.



 On Tue, Mar 3, 2009 at 13:44, aschobel ascho...@gmail.com wrote:

  To clarify, we only want to prepopulate the status field.

  This works on the standard version, doesn't work on the mobile
  version.

  It used to work on mobile version according to this thread:

 http://groups.google.com/group/twitter-development-talk/browse_thread...

  Cheers,
  Andreas

  Follow us on Twitter @3banana
 http://twitter.com/3banana

  On Mar 3, 1:00 pm, aschobel ascho...@gmail.com wrote:
  We are having problems posting status updates to the mobile version of
  Twitter, it looks like the status input field for the mobile version
  comes with a default value of .

  input type=text name=status id=status maxlength=140 class=i
  value=/

  For the standard version of Twitter, we can pre-populate the status
  field by doing opening the following page:

 http://twitter.com/home?status=Hello%20world

  Our app for Android lets folks share their notes to Twitter, and this
  was working fine until Twitter started detecting the user agent for
  Android and giving people the mobile version instead of the standard
  version.

  Is there a way to force the Standard version? Passing in ui_type=s
  doesn't do anything.

  We support Twidroid, but not everybody has that installed.

  Cheers,
  Andreas

  Follow us on Twitter @3bananahttp://twitter.com/3banana

 --
 Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x