> What if I have own application that requests data from my own twitter > account.
This must be a common use case. Twitter should provide the needed tokens for each app registered to an account, for use with/by that account only, right on the app settings page. Should be no big deal. I found implementing OAuth to be a cool challenge, but why force this category of user to go through all that, even once? For security reasons this service should be left to Twitter, but a third party could deliver the same tokens if provided with the app's Consumer key and secret. A bit messy though - need to change the requesting app's callback URL - but it's doable. Is someone already doing this? Would that violate ToS? On Apr 26, 7:48 am, Abava <dnam...@gmail.com> wrote: > > Yes. However, if you grab yourself a token, the tokens do not currently > > Exactly. And I am just curious – is there any service that can > generate a token for the account? E.g. account owner can generate by > the own that access token. Because the “classical” OAuth looks strange > in this case – confirm my own password usage to myself > > On Apr 25, 7:25 pm, Cameron Kaiser <spec...@floodgap.com> wrote: > > > > For the upcoming basic auth shutdown: > > > > What if I have own application that requests data from my own twitter > > > account. What is an easiest way for the authentication in this case? > > > It is the only one application that works with this account. And it > > > works with this account only. Is it still OAuth? > > > Yes. However, if you grab yourself a token, the tokens do not currently > > expire, so you may not have to implement the entire workflow (or only do so > > once). > > > -- > > ------------------------------------ > > personal:http://www.cameronkaiser.com/-- > > Cameron Kaiser * Floodgap Systems *www.floodgap.com*ckai...@floodgap.com > > -- You only live twice. > > ------------------------------------------------------- > > > -- > > Subscription > > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
