10 seconds does seem like a long time for this to be paused. I'm checking with the team why this value was chosen.
Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Jan 4, 2011 at 11:59 AM, Bess <bess...@gmail.com> wrote: > Rusell, > > Can you use tricks to alter Android browser meta tag on Android > Emulator? such as reducing the redirect time to see performance > differences? > > What is the main reason why Twitter can't use the same standard 302 > redirect on the mobile browser? > > On Jan 3, 11:18 pm, Bess <bess...@gmail.com> wrote: > > Rusell, > > > > Can you share how you confirm the mobile version use meta tag instead > > of standard 302? > > > > Is this something you could test on web browser? > > > > On Dec 30 2010, 10:25 pm, Russell Davis <russell.da...@gmail.com> > > wrote: > > > > > The regular oauth page does a standard 302 redirect which happens > > > immediately. For some reason, the mobile version instead uses a meta > > > tag to the redirect, and it specifies a delay of 10 seconds. I can't > > > be the only one who thinks this is a horrible user experience. Why the > > > delay? Is there any way to change it? > > > > > Thanks, > > > Russell > > -- > 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
