Yes, we are working on something that will make what you are asking for,
djMax, a working feature. I'm writing the documentation now.

Doug Williams
Twitter API Support
http://twitter.com/dougw


On Wed, Apr 15, 2009 at 2:53 PM, Abraham Williams <[email protected]> wrote:

>      * Feature (OAuth): Added provisional support for "Sign in via
>> Twitter" for OAuth applications. An official annoucement will follow
>> after full support is available.
>>          ยป More on this to come in subsequent mails. I need to get
>> another piece in place first.
>>
>>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5822fbfd5ea857c6
>
>
> On Wed, Apr 15, 2009 at 16:44, Dossy Shiobara <[email protected]> wrote:
>
>>
>> On 4/15/09 5:38 PM, djMax wrote:
>>
>>> I want to use OAuth via Twitter for login to our site.  The first time
>>> I get the flow, user clicks allow.  But is there a method that I use
>>> given the token and secret for the next time, so that if they're
>>> already logged in they see nothing but if they're not they have to
>>> login?
>>>
>>
>> This is why it would be desirable for Twitter to also implement an OpenID
>> provider, so folks could log into our third-party applications with their
>> Twitter account using OpenID.
>>
>> Then, we'd bind their OpenID to their OAuth token and be happy.
>>
>> Sadly, Alex has clearly stated that Twitter as an OpenID provider "won't
>> happen in 2009"[1].
>>
>>  [1]
>> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/98def90952bdab9c
>>
>> --
>> Dossy Shiobara              | [email protected] | http://dossy.org/
>> Panoptic Computer Network   | http://panoptic.com/
>>  "He realized the fastest way to change is to laugh at your own
>>    folly -- then you can let go and quickly move on." (p. 70)
>>
>
>
>
> --
> Abraham Williams | http://the.hackerconundrum.com
> Hacker | http://abrah.am | http://twitter.com/abraham
> Web608 | Community Evangelist | http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
>

Reply via email to