Re: [twitter-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
Any update on this? It should be really easy to change that 10 to a 0. Meanwhile, hoards of users are needlessly waiting for 10 seconds every time they log in. :) 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-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
I tested it in the Android emulator. I used HTTP Analyzer to capture the content of the page, where I saw the meta tag. -- 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-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
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
Re: [twitter-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
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
[twitter-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
Hi Matt, Could you also check why the standard 302 redirect not being used on mobile browser? I am guessing the 10 sec is just a rough guideline most web browser vendors use to redirect if there is an error in displaying content. Usu the workaround hack mobile developers use is to continue to check status using a timer until Oauth is completed. This hack is on device app, not server-side. On Jan 4, 2:25 pm, Matt Harris thematthar...@twitter.com wrote: 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, Twitterhttp://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
Re: [twitter-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
302 is a redirect of a URL. We're not redirecting the URL https://api.twitter.com/oauth/authorize, we're redirecting from https://api.twitter.com/oauth/authorize to the callback URL. Using the 302 code would mean we are telling browsers that https://api.twitter.com/oauth/authorize is actually callback URL - which is not correct. Hope that answers your question, Matt On Tue, Jan 4, 2011 at 3:50 PM, Bess bess...@gmail.com wrote: Hi Matt, Could you also check why the standard 302 redirect not being used on mobile browser? I am guessing the 10 sec is just a rough guideline most web browser vendors use to redirect if there is an error in displaying content. Usu the workaround hack mobile developers use is to continue to check status using a timer until Oauth is completed. This hack is on device app, not server-side. On Jan 4, 2:25 pm, Matt Harris thematthar...@twitter.com wrote: 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, Twitterhttp://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 -- 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-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
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-dev] Re: Twitter's mobile oauth page waits 10 seconds before redirecting
I completely agree - it's a horrible user experience. When the rest of the app is super fast a sudden 10 second delay feels like the app has crashed. On Dec 30, 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