Hi Bess,
I'm not sure how long the queue is right now, but we're coming back from a
vacation weekend here in San Francisco and it'll probably take a bit for us
to work through the queue this week. That said, we'll work through it as
quickly as we (securely) can. Each request must be researched
On May 31, 2010, at 9:25 AM, Bernd Stramm wrote:
In any case Jann, you have convinced me of something I strongly
suspected - I really should get xauth for my application as well.
If I have convinced one person today, I have done my job. I am used to that --
what with being a Mac user for
The requirement for users to go from app to browser to app is untenable for
many of my users. It is a major change to go from app to Safari and back to
app. Many users actually think that it the app is less secure (rightly or
wrongly) because they have to exit it -- and go to the web -- in
On Sun, 30 May 2010 03:50:21 -0700 (PDT)
Rich rhyl...@gmail.com wrote:
You don't have to go from app to browser, embed a UIWebView and then
in
- (BOOL)webView:(UIWebView *)webView shouldStartLoadWithRequest:
(NSURLRequest *)request navigationType:
(UIWebViewNavigationType)navigationType {
Okay, please tell me you know that I can create an app with a UIWebView that
will take that password you type in faster than anything.
It is NOT secure. This is my problem with oAuth. The work-arounds cause a
false sense of security. oAuth was NEVER supposed to be used this way. If the
On Sun, 30 May 2010 11:14:54 -0700
Abraham Williams 4bra...@gmail.com wrote:
On Sun, May 30, 2010 at 11:01, Bernd Stramm bernd.str...@gmail.com
wrote:
The user does trust the app, otherwise they would not be using it.
The problem with the scheme of using the app *and* a browser is
that
Thanks!
For now I have implemented xAuth (even though it does not work) by using
examples and what I expect. BUT I have hidden the Twitter button on my app
until xAuth is approved and I can fully test.
The one thing Twitter does NOT need right now is app developers leaving them in
the dust
