Ah, ok.
i think i understand it now... ;-) thanks!
On 10 Feb., 16:12, ryan alford ryanalford...@gmail.com wrote:
The user doesn't actually create their OAuth tokens manually. The tokens
are created automatically by Twitter and given to you through responses
after the user has given your
And where get the users there own keys to use the application with
there own twitter account? (e.g tweet deck)
On 9 Feb., 18:29, John Meyer john.l.me...@gmail.com wrote:
On 2/9/2010 10:03 AM, ryan alford wrote:
So you are saying that the user of a third party application must
register a
The user doesn't actually create their OAuth tokens manually. The tokens
are created automatically by Twitter and given to you through responses
after the user has given your application permission to their account.
Ryan
On Wed, Feb 10, 2010 at 8:27 AM, _Bensn benjaminroh...@t-online.de wrote:
Hm... that's bad, very bad! why is it not possible, the users download
our application, login with there twitter account, and it works?
(with.. from my app parameter).
is it possible, to get a explicit source parameter?
On 8 Feb., 18:55, John Meyer john.l.me...@gmail.com wrote:
On 2/8/2010 7:25
Where can they create there own keys? here - https://twitter.com/apps/new
?
On 8 Feb., 18:55, John Meyer john.l.me...@gmail.com wrote:
On 2/8/2010 7:25 AM, _Bensn wrote:
Hi there,
is it possible to develope a twitter application which uses oauth and
it can be used by more different users
Your users should not be required to get their own consumer key and consumer
secret.
Ryan
Sent from my DROID
On Feb 9, 2010 10:04 AM, _Bensn benjaminroh...@t-online.de wrote:
Where can they create there own keys? here - https://twitter.com/apps/new
?
On 8 Feb., 18:55, John Meyer
On 2/9/2010 9:20 AM, ryan alford wrote:
Your users should not be required to get their own consumer key and
consumer secret.
Ryan
Sent from my DROID
On Feb 9, 2010 10:04 AM, _Bensn benjaminroh...@t-online.de
mailto:benjaminroh...@t-online.de wrote:
Where can they create there own keys? here
Yes it does seem backwards. I made my statement because the link he gave
was for application consumer keys, not the OAuth tokens.
Ryan
Sent from my DROID
On Feb 9, 2010 11:27 AM, John Meyer john.l.me...@gmail.com wrote:
On 2/9/2010 9:20 AM, ryan alford wrote:
Your users should not be
On 2/9/2010 8:09 AM, _Bensn wrote:
@ John Meyer - thanks for editing my post with the url.
Is it right, every user who wants to use our application must at first
register the application?
Yeah. It might be construed as more effort than a basic authentication,
but I don't believe it is that
in fact, it shouldn't be that much more effort - just use an appropriate
library for your platform.
On Tue, Feb 9, 2010 at 8:53 AM, John Meyer john.l.me...@gmail.com wrote:
On 2/9/2010 8:09 AM, _Bensn wrote:
@ John Meyer - thanks for editing my post with the url.
Is it right, every user who
So you are saying that the user of a third party application must register a
completely new consumer key and consumer secret?
So when TweetDeck goes to OAuth, every user will create their own consumer
key and consumer secret, therefore, having 10s of thousands of TweetDeck
applications
On 2/9/2010 10:03 AM, ryan alford wrote:
So you are saying that the user of a third party application must
register a completely new consumer key and consumer secret?
Again, you have your terminology wrong. They get a completely new set
of oAuth tokens. Same as the fact that every user of
12 matches
Mail list logo
