twitter oauth #idcon7
TRANSCRIPT
Twitter OAuth
@nov
2010年6月25日金曜日
OAuth Echo
2010年6月25日金曜日
echofon
2010年6月25日金曜日
echofon
id & passwdphoto, message
id & passwdphoto, message
Basic Auth
2010年6月25日金曜日
echofon
consumer key & secretaccess token & secret
photo, message
oauth headerphoto, message
OAuth
2010年6月25日金曜日
with OAuth
Simple, but share consumer secret
http://j.mp/with_oauth
2010年6月25日金曜日
OAuth Echo - delegation in identity verificationhttp://j.mp/raffi_echo
2010.02.10
2010年6月25日金曜日
echofon
oauth headerphoto, message
oauth header
OAuth Echo
2010年6月25日金曜日
http://j.mp/with_oauth_echo
2010年6月25日金曜日
Delegated identity verification for uploadAndPost(OAuth Echo for uploadAndPost)
http://j.mp/raffi_echo2
2010.05.24
2010年6月25日金曜日
GET /account/verify_credentialswith given OAuth header
POST /uploadwith OAuth header for GET /account/verify_credentials
2010年6月25日金曜日
POST /satuses/updatewith given OAuth header
POST /uploadAndPostwith OAuth header for POST /statuses/update
2010年6月25日金曜日
POST /satuses/updatewith given OAuth header
POST /uploadAndPostwith OAuth header for POST /statuses/update
401 Unauthorized
2010年6月25日金曜日
However, the Consumer has a problem because it is charged with generating the signature, but it doesn't know the final caption for the signature because it doesn't know the URL. This means Twitter is going to need to do some work.
http://j.mp/raffi_echo2
2010年6月25日金曜日
POST /satuses/updatewith given OAuth header + X-OAuth-Append-Payload
POST /uploadAndPostwith OAuth header for POST /statuses/update
+ X-OAuth-Payload
2010年6月25日金曜日
photo = http://twitpic.com/gogo_jpnmessage = “GO GO #JPN”X-OAuth-Append-Payload = photo
photo = worldcup.pngmessage = “GO GO #JPN”X-OAuth-Payload = message
2010年6月25日金曜日
photo = http://twitpic.com/gogo_jpnmessage = “GO GO #JPN”X-OAuth-Append-Payload = photo
photo = worldcup.pngmessage = “GO GO #JPN”X-OAuth-Payload = message
2010年6月25日金曜日
This is not yet implemented on the Twitter side, but it will hopefully be soon. I'm definitely soliciting feedback. http://j.mp/raffi_echo2
2010年6月25日金曜日
follow @raffi
2010年6月25日金曜日
OAuth for Open Source
2010年6月25日金曜日
Coming soon: a solution for Open Source applications using OAuth with the Twitter API
http://j.mp/twitter_dev_talk
2010年6月25日金曜日
Open Source using Twitter API ... ?
2010年6月25日金曜日
Open Source = Open consumer secret
2010年6月25日金曜日
Coming soon: a solution for Open Source applications using OAuth with the Twitter API
http://j.mp/twitter_dev_talk
2010年6月25日金曜日
1. You store your API Consumer Key in your application distribution (but never your secret!).
2. A user downloads/installs/checks out your open source application and runs it for the first time
3. Your application builds a URL to our key exchange endpoint, using your consumer key.
4. You send the user to that URL in whatever way makes sense in your environment.
5. That user will approve your application's request to replicate itself on the user's behalf.
6. The user is presented with a string that they are asked to paste into your application. The string will contain an API key and secret, in addition to an access token and token secret for the member: everything that's needed to get the user up and running in your application.
7. The user pastes the string into your application, which then consumes and stores it to begin performing API calls using OAuth.
2010年6月25日金曜日
1. You store your API Consumer Key in your application distribution (but never your secret!).
2. A user downloads/installs/checks out your open source application and runs it for the first time
3. Your application builds a URL to our key exchange endpoint, using your consumer key.
4. You send the user to that URL in whatever way makes sense in your environment.
5. That user will approve your application's request to replicate itself on the user's behalf.
6. The user is presented with a string that they are asked to paste into your application. The string will contain an API key and secret, in addition to an access token and token secret for the member: everything that's needed to get the user up and running in your application.
7. The user pastes the string into your application, which then consumes and stores it to begin performing API calls using OAuth.
ck=KIyzzZUM7KvKYOpnst2aOw&cs=4PQk1eH4MadmzzEZ1G1KdrWHIFC1IPxv1kXZg0G3E&at=54221utEhFTv5GZZcc2R4w6thnApKtf1N1eKRedcFJthdeA&ats=FFdeOzzzzEwxOBWPPREd55 dKx7AAaI8NfpK7xnibv4Yls
2010年6月25日金曜日
via Termtter (nov)
2010年6月25日金曜日
We're only allowing open source applications for now. We may consider other use cases in the future.I'll post a new message when things are good to go and we're ready to accept applications into the feature. http://j.mp/twitter_dev_talk
2010年6月25日金曜日
after #worldcup
2010年6月25日金曜日