Re: [twitter-dev] Mobile OAuth Summary

2010-04-29 Thread Raffi Krikorian
hi. i'll follow up on this - do you have a notion of what browsers, what phones, etc. your users are coming from On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi wrote: > Hello, > > I migrated my mobile web site to OAuth. > Now, I have a lot of users complaining that the OAuth page of twitter > is

[twitter-dev] Mobile OAuth Summary

2010-04-29 Thread twittme_mobi
Hello, I migrated my mobile web site to OAuth. Now, I have a lot of users complaining that the OAuth page of twitter is not mobile friendly.Some of them are getting just a blank screen or just cannot open it. My honest question is - this is being discussed many times but where are we with this? A

[twitter-dev] Mobile oAuth always says access & update

2010-03-19 Thread Remy Sharp
It appears that mobile oAuth is ignoring the *access only* flag set on the connection permissions. I go out of my way to ensure I'm not writing to people's account, and now it says it anyway, screen shot here: http://img42.yfrog.com/img42/3104/ifrw.jpg Any chance of a fix? Thanks, Remy. To

Re: [twitter-dev] Mobile OAuth fix is LIVE

2010-02-07 Thread Jeff Enderwick
thanks :-) On Wed, Feb 3, 2010 at 3:16 PM, Ryan Sarver wrote: > FINALLY! > > An update has just gone live that fixes rendering of the OAuth screens for > most mobile devices. We also fixed a few small nagging things like the > default action is now "allow" instead of deny if you just hit "go" on

Re: [twitter-dev] Mobile OAuth fix is LIVE

2010-02-03 Thread Ianiv Schweber
Thanks for finally fixing this! One small detail: would be nice if the username field didn't automatically capitalize the first character. Ianiv Schweber ia...@blogaholics.ca Twitter: @ianiv Skype: ianivs Public Key: http://www.blogaholics.ca/ianivpubkey.asc On 2010-02-03, at 3:16 PM, Ryan Sa

[twitter-dev] Mobile oAuth

2009-08-19 Thread Mark Sievers
Hi There, I have a mobile based twitter client in the field and have implemented oAuth for this client. Some of the devices are either very low memory or have primitive browsers that dont support the rendering of the 'allow' / 'deny' access page ( http://twitter.com/oauth/authorize ). I have trie