[twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control
Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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: New oAuth Authenticate Page
I'm having this problem too. My login browser inside the phone app is now rendered useless, it doesn't even scroll. On Apr 28, 1:41 pm, Shannon Whitley shannon.whit...@gmail.com wrote: I was surprised to see a newly formatted oAuth Authenticate Page. The new page doesn't account for the scores of oAuth implementations that popup a new window. There is an ad-hoc standard for the window height and width that makes for a decent user experience. The new format will cause issues for the user since it results in page scrolling. Can we discuss this new page format and determine if it can be changed or if we can have alternate formats? -- 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] New oAuth Authorization screen is unusable on phone webbrowser control
I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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: New oAuth Authenticate Page
I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:55 AM, Bob12345 wrote: I'm having this problem too. My login browser inside the phone app is now rendered useless, it doesn't even scroll. On Apr 28, 1:41 pm, Shannon Whitleyshannon.whit...@gmail.com wrote: I was surprised to see a newly formatted oAuth Authenticate Page. The new page doesn't account for the scores of oAuth implementations that popup a new window. There is an ad-hoc standard for the window height and width that makes for a decent user experience. The new format will cause issues for the user since it results in page scrolling. Can we discuss this new page format and determine if it can be changed or if we can have alternate formats? -- 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: New oAuth Authorization screen is unusable on phone webbrowser control
Thanks for your response Tom, but I am not sure whether this could be done on a Windows Phone 7. The only way to open a regular browser window from a Silverlight app on the phone(that I know of) is to use Microsoft.Phone.Tasks.WebBrowserTask and that just opens a webpage. Would it be possible to bypass this new screen altogether if I were to use xAuth? Thanks! -Bob On Apr 30, 9:09 am, Tom van der Woerdt i...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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: New oAuth Authorization screen is unusable on phone webbrowser control
Yes. But I don't like xAuth :-) (Not that that should be relevant for you) Anyway, the Microsoft.Phone.Tasks.WebBrowserTask is exactly what I meant. Can you get WM7 to recognize a yourapp:// URL (custom scheme)? You could have the OAuth login flow redirect back to that page with the oauth code (not talking about oob authorization, but the normal flow) and get the token that way. For the user, this would probably be the best way. Tom On 4/30/11 10:33 PM, Bob12345 wrote: Thanks for your response Tom, but I am not sure whether this could be done on a Windows Phone 7. The only way to open a regular browser window from a Silverlight app on the phone(that I know of) is to use Microsoft.Phone.Tasks.WebBrowserTask and that just opens a webpage. Would it be possible to bypass this new screen altogether if I were to use xAuth? Thanks! -Bob On Apr 30, 9:09 am, Tom van der Woerdti...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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: New oAuth Authorization screen is unusable on phone webbrowser control
On Apr 30, 12:09 pm, Tom van der Woerdt i...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. They are not blocked, it's *only* a problem of layout. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. I have the same problem, and I don't see why using a webcontrol is a security problem. Since xauth is the exception, why twitter is making the use of oauth so hard ? Matthieu -- 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] New oAuth Authorization screen is unusable on phone webbrowser control
Why is it safer Tom? Safer for who? Cheers, Dean From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of Tom van der Woerdt Sent: Saturday, April 30, 2011 12:09 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a good thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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] New oAuth Authorization screen is unusable on phone webbrowser control
In an embedded view, the developer can access the content of the website without the user knowing it (read passwords, usernames, etc). On most OSes (definitely iOS, WM7 and Android) this is not possible in the non-embedded (webbrowser) view. Tom On 5/1/11 1:02 AM, Dean Collins wrote: Why is it safer Tom? Safer for who? Cheers, Dean *From:*twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] *On Behalf Of *Tom van der Woerdt *Sent:* Saturday, April 30, 2011 12:09 PM *To:* twitter-development-talk@googlegroups.com *Subject:* Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- 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
Re: [twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On 5/1/11 12:47 AM, Matthieu GD wrote:
On Apr 30, 12:09 pm, Tom van der Woerdti...@tvdw.eu wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
They are not blocked, it's *only* a problem of layout.
Are you sure? A block of CSS saying html { display: none; } doesn't
look like a problem, more like a feature.
The workaround I recommend: launch the actual browser, using a
yourapp:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
I have the same problem, and I don't see why using a webcontrol is a
security problem. Since xauth is the exception, why twitter is making
the use of oauth so hard ?
You should read the article at http://goo.gl/xI0PZ
Tom
--
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: New oAuth Authorization screen is unusable on phone webbrowser control
On Apr 30, 7:13 pm, Tom van der Woerdt i...@tvdw.eu wrote:
On 5/1/11 12:47 AM, Matthieu GD wrote: On Apr 30, 12:09 pm, Tom van der
Woerdti...@tvdw.eu wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
They are not blocked, it's *only* a problem of layout.
Are you sure? A block of CSS saying html { display: none; } doesn't
look like a problem, more like a feature. The workaround I recommend:
launch the actual browser, using a
yourapp:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
I have the same problem, and I don't see why using a webcontrol is a
security problem. Since xauth is the exception, why twitter is making
the use of oauth so hard ?
You should read the article athttp://goo.gl/xI0PZ
Not sure if my previous message get trough.
ok now we know it's insecure. But why removing the page without notice
since it's not easy to deploy a new version of a native application?
We have lived with xAuth (and it's still used by some applications
like full-fledged clients) during several months until oauth was
ready.
Matthieu
--
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: Problema
Poderia ser possível que o que o Twitter Search analisador não trata de bem com diacríticos Portugues? #UniãoDoTwitterSegueEuTeSigoDeVolta The Twitter search component was acquired from Summarize a few years back, and it's been a great piece of tech - but it's alas not very native and it probably won't be long before a more integrated and even more historical search can become part of the API. On Apr 29, 5:42 pm, Rafael Cavalcante Silva rafahu...@hotmail.com wrote: Estou escrevendo pra vocês porque há uns dias não estão aparecendo meus tweets nos temas, aqueles 10 temas que são os mais citados por país e outros temas como #UniãoDoTwitterSegueEuTeSigoDeVolta etc. Não estão aparecendo. Eu escrevo o tema, mas meu tweet não aparece no tema. Por favor, ajudem. Desde já, agradeço. -- 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
