This is great and works well too!
On Feb 3, 11:25 pm, Swap <rh.swar...@gmail.com> wrote:
> w000000000t! :D
one small nit: the redirect back to the app seemed to take longer than
it should. not sure what the redirect timeout is, but it might do well
to shorten it up by a second or two... otherwise ppl might start to
get click-happy while nothing is happening.
-Chad
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
> <IMG_0739.png><IMG_0738.png>
> IMG_0739.png
> 93KViewDownload
>
> IMG_0738.png
> 75KViewDownload
On Feb 3, 4:56 pm, Will Fleming <wflemin...@gmail.com> wrote:
> It is working correctly on a G1 running Android, but getting the non mobile
> version on a Nexus One. User-Agent is
>
> *Mozilla/5.0 (Linux; U; Android 2.1; en-us; Nexus One Build/ERD79)
> AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17*
> IMG_0739.png
> 93KViewDownload
>
> IMG_0738.png
> 75KViewDownload
Can provide headers etc if needed.
Thanks for this update - it looks amazing. Should really ramp up
security & usability.
> IMG_0739.png
> 93KViewDownload
>
> IMG_0738.png
> 75KViewDownload
> IMG_0739.png
> 93KViewDownload
>
> IMG_0738.png
> 75KViewDownload
On Feb 5, 10:27 am, Ryan Sarver <rsar...@twitter.com> wrote:
> We've had to roll back the mobile OAuth update as it was consuming an
> abnormally large amount of resources. We'll dig in and figure out what was
> going on.
>
> Almost there, rs
>
Thanks for both the attempted fix and the announcement.
Unfortunately, where the previous version was kind of a crapshoot for
mobile users because the buttons appeared black (see my screenshot in
the bug report at http://code.google.com/p/twitter-api/issues/detail?id=395),
this new version doesn't work at all on many mobile browsers.
Because this breaks mobile Twitter support completely for many (most?
all?) phones using older browsers, can you please revert to the
previous version, and then stage a new version somewhere else that we
can help you test?
-- Charles
> IMG_0739.png
> 93KViewDownload
>
> IMG_0738.png
> 75KViewDownload
-- Charles
On Feb 5, 9:22 am, Michael Steuer <mste...@gmail.com> wrote:
> In fact, I'd recommend that you only show the new version for devices you
> have actually tested against... Mobile browser support is a crap shoot and
> you really can't assume that something that works on one device, works on
> another... You need to test each and every one of them (or at least each
> family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS,
> Motorola V3 series, etc.) I've been in mobile development for 15 years...
> Let me know if you need some pointers off list... Happy to assist.
>
> On 2/5/10 8:40 AM, "CharlesW" <cwilt...@gmail.com> wrote:> Ryan,
>
> > Thanks for both the attempted fix and the announcement.
>
> > Unfortunately, where the previous version was kind of a crapshoot for
> > mobile users because the buttons appeared black (see my screenshot in
> > the bug report athttp://code.google.com/p/twitter-api/issues/detail?id=395),
Don't know if it will fit in with your architecture, but maybe this
service could be of use to you:
On Feb 6, 12:39 am, Ryan Sarver <rsar...@twitter.com> wrote:
> Ill talk with the team and figure out if it's better to roll it back or just
> limit it to the known, working user agents
>
Thanks
T