Hi all, I'm new to the whole OAuth/xAuth thing
I'd like t know how long it's gonna take to twitter api team to
authorize a xAuth use request ? any feedback on that ? I guess you got
this question 100 times a day, no ? sorry ;)
thx in advance
--
Twitter developer documentation and resources:
Hi Alex,
We do our best to keep the wait under 72 hours, but there are times it will
take longer.
Taylor
On Fri, Sep 10, 2010 at 4:33 AM, supersonicduck wrote:
> Hi,
>
> I've totally missed the announcement that basic authentication will be
> disabled end of August, so now my iPhone app's twitt
Hi,
I've totally missed the announcement that basic authentication will be
disabled end of August, so now my iPhone app's twitter functionality
is broken. I've submitted a request to get access to xAuth
authentication two days ago and still didn't get a response. What kind
of timeframe are we look
On 04/27/2010 08:00 PM, John Meyer wrote:
> On 4/27/2010 8:29 PM, M. Edward (Ed) Borasky wrote:
>> On 04/27/2010 05:00 PM, John Meyer wrote:
>>> On 4/27/2010 5:53 PM, Julio Biason wrote:
se it's open source it doesn't mean you can't charge for it.
So I'm guessing that's what John Meyer as
On 4/27/2010 8:29 PM, M. Edward (Ed) Borasky wrote:
On 04/27/2010 05:00 PM, John Meyer wrote:
On 4/27/2010 5:53 PM, Julio Biason wrote:
se it's open source it doesn't mean you can't charge for it.
So I'm guessing that's what John Meyer asked what open source have to
with money.
Actually wha
On 04/27/2010 05:00 PM, John Meyer wrote:
> On 4/27/2010 5:53 PM, Julio Biason wrote:
>> se it's open source it doesn't mean you can't charge for it.
>> So I'm guessing that's what John Meyer asked what open source have to
>> with money.
>>
>
>
> Actually what I was asking is what did money have
On 04/27/2010 04:53 PM, Julio Biason wrote:
> On Tue, Apr 27, 2010 at 2:35 PM, M. Edward (Ed) Borasky
> wrote:
>> Charging money is how we pay our expenses and earn enough profit to
>> invest in research and development for the next generation applications. ;-)
>
> Just because it's open source i
On 4/27/2010 5:53 PM, Julio Biason wrote:
se it's open source it doesn't mean you can't charge for it.
So I'm guessing that's what John Meyer asked what open source have to
with money.
Actually what I was asking is what did money have to do with the way
that our applications authenticate the
On Tue, Apr 27, 2010 at 2:35 PM, M. Edward (Ed) Borasky
wrote:
> Charging money is how we pay our expenses and earn enough profit to
> invest in research and development for the next generation applications. ;-)
Just because it's open source it doesn't mean you can't charge for it.
So I'm guessin
On 4/27/2010 11:35 AM, M. Edward (Ed) Borasky wrote:
ours might, but as you know about Open Source, the whole point is that
people can choose and some may choose to use certain calls that require
authentication. And what does charging money have to do with anything?
I presume that we are ta
On 04/27/2010 10:18 AM, John Meyer wrote:
> On 4/27/2010 10:59 AM, M. Edward (Ed) Borasky wrote:
>> On 04/27/2010 04:53 AM, John Meyer wrote:
>>> On 4/26/2010 8:59 PM, M. Edward (Ed) Borasky wrote:
Yeah ... but I *like* having the browser involved.
>>> Which is fine. However, there are other
On 4/27/2010 10:59 AM, M. Edward (Ed) Borasky wrote:
On 04/27/2010 04:53 AM, John Meyer wrote:
On 4/26/2010 8:59 PM, M. Edward (Ed) Borasky wrote:
Yeah ... but I *like* having the browser involved.
Which is fine. However, there are other people who don't like getting
the browser involved (peo
On Apr 26, 2010, at 8:54 PM, Raffi Krikorian wrote:
> >> xAuth is a method for which to exchange usernames and passwords for those
> >> tokens, without send the user through the workflow. this is for two
> >> reasons: 1. mobile/desktop application authors have complained that it
> >> makes
> >>
On 04/27/2010 04:53 AM, John Meyer wrote:
> On 4/26/2010 8:59 PM, M. Edward (Ed) Borasky wrote:
>> Yeah ... but I *like* having the browser involved.
> Which is fine. However, there are other people who don't like getting
> the browser involved (people making command line Linux programs, for
> ins
On 4/26/2010 8:59 PM, M. Edward (Ed) Borasky wrote:
On 04/26/2010 05:16 PM, Cameron Kaiser wrote:
xAuth is a method for which to exchange usernames and passwords for those
tokens, without send the user through the workflow. this is for two
reasons: 1. mobile/desktop application authors have com
> > and 3. Browserless environments. I'm pretty sure that was one of the initial
> > motivators way back when the crud was flying.
>
> Yeah ... but I *like* having the browser involved.
I'm so happy your world is so limited.
--
personal: http://www.cameronka
>
> >> xAuth is a method for which to exchange usernames and passwords for
> those
> >> tokens, without send the user through the workflow. this is for two
> >> reasons: 1. mobile/desktop application authors have complained that it
> makes
> >> their UX fugly when they bring up a web browser (i'll
On 04/26/2010 05:16 PM, Cameron Kaiser wrote:
>> xAuth is a method for which to exchange usernames and passwords for those
>> tokens, without send the user through the workflow. this is for two
>> reasons: 1. mobile/desktop application authors have complained that it makes
>> their UX fugly when t
> xAuth is a method for which to exchange usernames and passwords for those
> tokens, without send the user through the workflow. this is for two
> reasons: 1. mobile/desktop application authors have complained that it makes
> their UX fugly when they bring up a web browser (i'll hold my opinions
On 4/26/2010 4:55 PM, Raffi Krikorian wrote:
let's step back.
oAuth is the general framework that we want everybody to use.
applications no longer have to store usernames and passwords, which is
"a good thing".
normally, to get access tokens, applications send users through the
oAuth workflow
let's step back.
oAuth is the general framework that we want everybody to use. applications
no longer have to store usernames and passwords, which is "a good thing".
normally, to get access tokens, applications send users through the oAuth
workflow -- this means they bring up a webpage on twitte
On 4/26/2010 4:23 PM, Raffi Krikorian wrote:
honestly, i wouldn't plan on it. the "spirit" of oAuth is that the
user's credentials never even pass through a web application.
Now I'm confused. Is xAuth going to be a method unto itself of
authenticating for the long-term, or is this the way th
honestly, i wouldn't plan on it. the "spirit" of oAuth is that the user's
credentials never even pass through a web application.
On Mon, Apr 26, 2010 at 3:02 PM, John Meyer wrote:
> On 4/26/2010 3:46 PM, Raffi Krikorian wrote:
>
>> precisely.
>>
>>
> So is it a possibility that general xAuth wi
On 4/26/2010 3:46 PM, Raffi Krikorian wrote:
precisely.
So is it a possibility that general xAuth will be available before Basic
goes the way of the dodo? I'm not saying it's easier than oAuth but it
would at least let developers use their interface and swap in the xAuth
rather than having
precisely.
On Mon, Apr 26, 2010 at 2:41 PM, John Meyer wrote:
> On 4/26/2010 2:15 PM, Raffi Krikorian wrote:
>
>> just to be clear - what xAuth is used for is to do a username/password
>> exchange for an oauth access token / secret (for a given application).
>> from then on out, that access tok
On 4/26/2010 2:15 PM, Raffi Krikorian wrote:
just to be clear - what xAuth is used for is to do a username/password
exchange for an oauth access token / secret (for a given application).
from then on out, that access token and secret is used to sign all
requests in an oauth manner.
So in other
just to be clear - what xAuth is used for is to do a username/password
exchange for an oauth access token / secret (for a given application). from
then on out, that access token and secret is used to sign all requests in an
oauth manner.
On Mon, Apr 26, 2010 at 12:48 PM, John Meyer wrote:
> On
On 4/26/2010 1:30 PM, Raffi Krikorian wrote:
a bit unsure - we're still working out what the appropriate terms for
xauth should be. we just wanted it out there ASAP because of basic auth
removal.
Is there anything that you can do with xAuth that you can't do with
oAuth? If not I would think
a bit unsure - we're still working out what the appropriate terms for xauth
should be. we just wanted it out there ASAP because of basic auth removal.
I recently submitted a request for xAuth approval for a mobile app. I
>> was wondering if anyone knows roughly how long it takes for approval.
>>
it should be on the order of days (hopefully less - depends on our backlog
and our queue).
On Mon, Apr 26, 2010 at 11:52 AM, Tony wrote:
> I recently submitted a request for xAuth approval for a mobile app. I
> was wondering if anyone knows roughly how long it takes for approval.
> Thanks!
>
>
>
On 4/26/2010 12:52 PM, Tony wrote:
I recently submitted a request for xAuth approval for a mobile app. I
was wondering if anyone knows roughly how long it takes for approval.
Thanks!
On a larger note, is xAuth always going to be something that requires
pre-approval?
--
Subscription settin
I recently submitted a request for xAuth approval for a mobile app. I
was wondering if anyone knows roughly how long it takes for approval.
Thanks!
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
32 matches
Mail list logo
