[twitter-dev] Re: oAuth Echo Enabled Providers
yFrog supports OAuth echo, but with a different technique than Raffi proposed on his blog: http://code.google.com/p/imageshackapi/wiki/TwitterAuthentication I also know that img.ly is working on the echo endpoint. -ch On May 20, 10:38 pm, Rich wrote: > This are the providers I currently user that don't seem to have > switched to oAuth Echo yet > > - yFrog - Raffi mentioned they have been working with them, but I > don't see the end point yet > - TweetPhoto - they have an implementation where you send your > consumer secret key but I'm not going to do that! > - TwitrPix > - img.ly > > These I know work > - TwitPic > - Twitgoo > - MobyPicture > > This one claims to have oAuth Echo support but just always responds > that you haven't defined a username and/or password > - Pikchur > > Any others anyone knows about? > > On May 21, 1:32 am, gotosleep wrote: > > > > > Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, > > my attempts have been a complete failure. No matter what I try, I get > > a 401 back with the error message "Authentication needed". > > > On May 20, 6:29 pm, Greg wrote: > > > > Does anyone have an example of a PHP Library to interact with these > > > libraries via Oauth Echo? I would be interested or to see some sample > > > code. > > > > On May 20, 6:44 pm, Rich wrote: > > > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > > > change the realm, provider and signing request > > > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp... > > > > through > > > > > On May 20, 11:23 pm, Rich wrote: > > > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > > > constantly return a 401, and on the very odd occasion one does make it > > > > > through Twitter itself returns a 500 status error (even though it > > > > > actually posts the message) > > > > > > On May 20, 11:00 pm, Rich wrote: > > > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > > > confirm? > > > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > > > I am the lead dev on Twitgoo and I just built full echo support > > > > > > > > for > > > > > > > > 'upload' there. Its on the beta site right now, so if you want > > > > > > > > to > > > > > > > > test, please contact me for the info, otherwise it should be > > > > > > > > out by > > > > > > > > the end of the week. It will have full support of header, query > > > > > > > > string and multipart body parameters. > > > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > > > list of > > > > > > > > > media providers and external services that have already made > > > > > > > > > the > > > > > > > > > switch to oAuth Echo. > > > > > > > > > > So far I've found and tested > > > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this > > > > > > > > > month. > > > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Hi Rich, TwitrPix is in the process of converting to oAuth and we'll be finalizing our oAuth Echo APIs very shortly. It was my understanding that there would be some type of oAuth Echo console so we could test our implementation, but I haven't received final word back yet from Twitter. I think its super important that from a developer standpoint that all service provides (TwitrPix, Twitpic, Tweetphoto,etc) all use a very standarized way of dealing with oAuth Echo implementations in their API endpoints. This will certainly reduce any confusion and possible burden of having developers deal with multiple variations. Same way the services used a common endpoint for upload and uploadAndPost, this should be no different. Best, Jerry On May 21, 1:38 am, Rich wrote: > This are the providers I currently user that don't seem to have > switched to oAuth Echo yet > > - yFrog - Raffi mentioned they have been working with them, but I > don't see the end point yet > - TweetPhoto - they have an implementation where you send your > consumer secret key but I'm not going to do that! > - TwitrPix > - img.ly > > These I know work > - TwitPic > - Twitgoo > - MobyPicture > > This one claims to have oAuth Echo support but just always responds > that you haven't defined a username and/or password > - Pikchur > > Any others anyone knows about? > > On May 21, 1:32 am, gotosleep wrote: > > > > > Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, > > my attempts have been a complete failure. No matter what I try, I get > > a 401 back with the error message "Authentication needed". > > > On May 20, 6:29 pm, Greg wrote: > > > > Does anyone have an example of a PHP Library to interact with these > > > libraries via Oauth Echo? I would be interested or to see some sample > > > code. > > > > On May 20, 6:44 pm, Rich wrote: > > > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > > > change the realm, provider and signing request > > > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp... > > > > through > > > > > On May 20, 11:23 pm, Rich wrote: > > > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > > > constantly return a 401, and on the very odd occasion one does make it > > > > > through Twitter itself returns a 500 status error (even though it > > > > > actually posts the message) > > > > > > On May 20, 11:00 pm, Rich wrote: > > > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > > > confirm? > > > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > > > I am the lead dev on Twitgoo and I just built full echo support > > > > > > > > for > > > > > > > > 'upload' there. Its on the beta site right now, so if you want > > > > > > > > to > > > > > > > > test, please contact me for the info, otherwise it should be > > > > > > > > out by > > > > > > > > the end of the week. It will have full support of header, query > > > > > > > > string and multipart body parameters. > > > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > > > list of > > > > > > > > > media providers and external services that have already made > > > > > > > > > the > > > > > > > > > switch to oAuth Echo. > > > > > > > > > > So far I've found and tested > > > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this > > > > > > > > > month. > > > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
This are the providers I currently user that don't seem to have switched to oAuth Echo yet - yFrog - Raffi mentioned they have been working with them, but I don't see the end point yet - TweetPhoto - they have an implementation where you send your consumer secret key but I'm not going to do that! - TwitrPix - img.ly These I know work - TwitPic - Twitgoo - MobyPicture This one claims to have oAuth Echo support but just always responds that you haven't defined a username and/or password - Pikchur Any others anyone knows about? On May 21, 1:32 am, gotosleep wrote: > Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, > my attempts have been a complete failure. No matter what I try, I get > a 401 back with the error message "Authentication needed". > > On May 20, 6:29 pm, Greg wrote: > > > > > Does anyone have an example of a PHP Library to interact with these > > libraries via Oauth Echo? I would be interested or to see some sample > > code. > > > On May 20, 6:44 pm, Rich wrote: > > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > > change the realm, provider and signing request > > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp...go > > > through > > > > On May 20, 11:23 pm, Rich wrote: > > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > > constantly return a 401, and on the very odd occasion one does make it > > > > through Twitter itself returns a 500 status error (even though it > > > > actually posts the message) > > > > > On May 20, 11:00 pm, Rich wrote: > > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > > confirm? > > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > > I am the lead dev on Twitgoo and I just built full echo support > > > > > > > for > > > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > > > test, please contact me for the info, otherwise it should be out > > > > > > > by > > > > > > > the end of the week. It will have full support of header, query > > > > > > > string and multipart body parameters. > > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > > list of > > > > > > > > media providers and external services that have already made the > > > > > > > > switch to oAuth Echo. > > > > > > > > > So far I've found and tested > > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Yeah they work fine, remember you don't oAuth sign the ACTUAL request to Twitpic or Twitgoo, you make a fake called to Twitter's verify_credentials page, take that header and add it to the one your send to Twitpic with a different name On May 21, 1:32 am, gotosleep wrote: > Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, > my attempts have been a complete failure. No matter what I try, I get > a 401 back with the error message "Authentication needed". > > On May 20, 6:29 pm, Greg wrote: > > > > > Does anyone have an example of a PHP Library to interact with these > > libraries via Oauth Echo? I would be interested or to see some sample > > code. > > > On May 20, 6:44 pm, Rich wrote: > > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > > change the realm, provider and signing request > > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp...go > > > through > > > > On May 20, 11:23 pm, Rich wrote: > > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > > constantly return a 401, and on the very odd occasion one does make it > > > > through Twitter itself returns a 500 status error (even though it > > > > actually posts the message) > > > > > On May 20, 11:00 pm, Rich wrote: > > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > > confirm? > > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > > I am the lead dev on Twitgoo and I just built full echo support > > > > > > > for > > > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > > > test, please contact me for the info, otherwise it should be out > > > > > > > by > > > > > > > the end of the week. It will have full support of header, query > > > > > > > string and multipart body parameters. > > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > > list of > > > > > > > > media providers and external services that have already made the > > > > > > > > switch to oAuth Echo. > > > > > > > > > So far I've found and tested > > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, my attempts have been a complete failure. No matter what I try, I get a 401 back with the error message "Authentication needed". On May 20, 6:29 pm, Greg wrote: > Does anyone have an example of a PHP Library to interact with these > libraries via Oauth Echo? I would be interested or to see some sample > code. > > On May 20, 6:44 pm, Rich wrote: > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > change the realm, provider and signing request > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttps://api.twitter.com/1/account/verify_credentials.jsonandit'll > > go > > through > > > On May 20, 11:23 pm, Rich wrote: > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > constantly return a 401, and on the very odd occasion one does make it > > > through Twitter itself returns a 500 status error (even though it > > > actually posts the message) > > > > On May 20, 11:00 pm, Rich wrote: > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > confirm? > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > > test, please contact me for the info, otherwise it should be out by > > > > > > the end of the week. It will have full support of header, query > > > > > > string and multipart body parameters. > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > list of > > > > > > > media providers and external services that have already made the > > > > > > > switch to oAuth Echo. > > > > > > > > So far I've found and tested > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
It's working great now. Many thanks Steve On May 21, 4:22 am, Steve C wrote: > Hi Rich- > > Nice catch! During one of our deployments today, we mistakingly > switched the OAuth Echo API to use Twitter's Non-SSL Endpoint. I just > pushed a fix for it- can you let me know if everything works correctly > for you again? > > (Coincidently, the deployment that turned off SSL for the API was > turning SSL on for another part of the website. :P) > > Thanks! > > Steve Corona > Twitpic > > On May 20, 6:44 pm, Rich wrote: > > > > > A bit more debugging and oAuth Echo only seems to be broken over SSL, > > change the realm, provider and signing request > > tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttps://api.twitter.com/1/account/verify_credentials.jsonandit'll > > go > > through > > > On May 20, 11:23 pm, Rich wrote: > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > > constantly return a 401, and on the very odd occasion one does make it > > > through Twitter itself returns a 500 status error (even though it > > > actually posts the message) > > > > On May 20, 11:00 pm, Rich wrote: > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > > confirm? > > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > > This is now active on Twitgoo. You can see the documentation > > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > > test, please contact me for the info, otherwise it should be out by > > > > > > the end of the week. It will have full support of header, query > > > > > > string and multipart body parameters. > > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > > With the impending switch off of Basic Auth, should we keep a > > > > > > > list of > > > > > > > media providers and external services that have already made the > > > > > > > switch to oAuth Echo. > > > > > > > > So far I've found and tested > > > > > > > > TwitPic - full oAuth Echo support > > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Hi Rich- Nice catch! During one of our deployments today, we mistakingly switched the OAuth Echo API to use Twitter's Non-SSL Endpoint. I just pushed a fix for it- can you let me know if everything works correctly for you again? (Coincidently, the deployment that turned off SSL for the API was turning SSL on for another part of the website. :P) Thanks! Steve Corona Twitpic On May 20, 6:44 pm, Rich wrote: > A bit more debugging and oAuth Echo only seems to be broken over SSL, > change the realm, provider and signing request > tohttp://api.twitter.com/1/account/verify_credentials.jsoninstead > ofhttps://api.twitter.com/1/account/verify_credentials.jsonand it'll go > through > > On May 20, 11:23 pm, Rich wrote: > > > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > constantly return a 401, and on the very odd occasion one does make it > > through Twitter itself returns a 500 status error (even though it > > actually posts the message) > > > On May 20, 11:00 pm, Rich wrote: > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > confirm? > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > This is now active on Twitgoo. You can see the documentation > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > test, please contact me for the info, otherwise it should be out by > > > > > the end of the week. It will have full support of header, query > > > > > string and multipart body parameters. > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > With the impending switch off of Basic Auth, should we keep a list > > > > > > of > > > > > > media providers and external services that have already made the > > > > > > switch to oAuth Echo. > > > > > > > So far I've found and tested > > > > > > > TwitPic - full oAuth Echo support > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Does anyone have an example of a PHP Library to interact with these libraries via Oauth Echo? I would be interested or to see some sample code. On May 20, 6:44 pm, Rich wrote: > A bit more debugging and oAuth Echo only seems to be broken over SSL, > change the realm, provider and signing request > tohttp://api.twitter.com/1/account/verify_credentials.jsoninstead > ofhttps://api.twitter.com/1/account/verify_credentials.jsonand it'll go > through > > On May 20, 11:23 pm, Rich wrote: > > > Scrap that, looks like oAuth echo is almost totally broken right now, > > only Twitgoo seems to be working, both MobyPicture and TwitPic > > constantly return a 401, and on the very odd occasion one does make it > > through Twitter itself returns a 500 status error (even though it > > actually posts the message) > > > On May 20, 11:00 pm, Rich wrote: > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > > confirm? > > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > This is now active on Twitgoo. You can see the documentation > > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > > test, please contact me for the info, otherwise it should be out by > > > > > the end of the week. It will have full support of header, query > > > > > string and multipart body parameters. > > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > > With the impending switch off of Basic Auth, should we keep a list > > > > > > of > > > > > > media providers and external services that have already made the > > > > > > switch to oAuth Echo. > > > > > > > So far I've found and tested > > > > > > > TwitPic - full oAuth Echo support > > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request to http://api.twitter.com/1/account/verify_credentials.json instead of https://api.twitter.com/1/account/verify_credentials.json and it'll go through On May 20, 11:23 pm, Rich wrote: > Scrap that, looks like oAuth echo is almost totally broken right now, > only Twitgoo seems to be working, both MobyPicture and TwitPic > constantly return a 401, and on the very odd occasion one does make it > through Twitter itself returns a 500 status error (even though it > actually posts the message) > > On May 20, 11:00 pm, Rich wrote: > > > > > Look's like TwitPic's oAuth Echo has broken again, can anyone else > > confirm? > > > On May 20, 9:49 pm, Justin Hart wrote: > > > > This is now active on Twitgoo. You can see the documentation > > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > > On May 19, 9:05 am, Justin Hart wrote: > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > > 'upload' there. Its on the beta site right now, so if you want to > > > > test, please contact me for the info, otherwise it should be out by > > > > the end of the week. It will have full support of header, query > > > > string and multipart body parameters. > > > > > On May 17, 2:47 pm, Rich wrote: > > > > > > With the impending switch off of Basic Auth, should we keep a list of > > > > > media providers and external services that have already made the > > > > > switch to oAuth Echo. > > > > > > So far I've found and tested > > > > > > TwitPic - full oAuth Echo support > > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich wrote: > Look's like TwitPic's oAuth Echo has broken again, can anyone else > confirm? > > On May 20, 9:49 pm, Justin Hart wrote: > > > > > This is now active on Twitgoo. You can see the documentation > > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > > On May 19, 9:05 am, Justin Hart wrote: > > > > I am the lead dev on Twitgoo and I just built full echo support for > > > 'upload' there. Its on the beta site right now, so if you want to > > > test, please contact me for the info, otherwise it should be out by > > > the end of the week. It will have full support of header, query > > > string and multipart body parameters. > > > > On May 17, 2:47 pm, Rich wrote: > > > > > With the impending switch off of Basic Auth, should we keep a list of > > > > media providers and external services that have already made the > > > > switch to oAuth Echo. > > > > > So far I've found and tested > > > > > TwitPic - full oAuth Echo support > > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart wrote: > This is now active on Twitgoo. You can see the documentation > here:http://twitgoo.com/docs/Content/Developer/upload.htm > > On May 19, 9:05 am, Justin Hart wrote: > > > > > I am the lead dev on Twitgoo and I just built full echo support for > > 'upload' there. Its on the beta site right now, so if you want to > > test, please contact me for the info, otherwise it should be out by > > the end of the week. It will have full support of header, query > > string and multipart body parameters. > > > On May 17, 2:47 pm, Rich wrote: > > > > With the impending switch off of Basic Auth, should we keep a list of > > > media providers and external services that have already made the > > > switch to oAuth Echo. > > > > So far I've found and tested > > > > TwitPic - full oAuth Echo support > > > TwitVid - oAuth Echo by sending as a URL parameter > > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
This is now active on Twitgoo. You can see the documentation here: http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart wrote: > I am the lead dev on Twitgoo and I just built full echo support for > 'upload' there. Its on the beta site right now, so if you want to > test, please contact me for the info, otherwise it should be out by > the end of the week. It will have full support of header, query > string and multipart body parameters. > > On May 17, 2:47 pm, Rich wrote: > > > > > With the impending switch off of Basic Auth, should we keep a list of > > media providers and external services that have already made the > > switch to oAuth Echo. > > > So far I've found and tested > > > TwitPic - full oAuth Echo support > > TwitVid - oAuth Echo by sending as a URL parameter > > > I know MobyPicture intend to have oAuth Echo enabled this month. > > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich wrote: > With the impending switch off of Basic Auth, should we keep a list of > media providers and external services that have already made the > switch to oAuth Echo. > > So far I've found and tested > > TwitPic - full oAuth Echo support > TwitVid - oAuth Echo by sending as a URL parameter > > I know MobyPicture intend to have oAuth Echo enabled this month. > > Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
You don't sign the request to TwitPic at all. You make a fake signature as if you calling the verify_credentials end point and add that to the http header On May 18, 10:23 pm, uprise78 wrote: > On May 18, 2:08 pm, Rich wrote: > > > I don't use curl but send it with multipart form data and it's been > > working with TwitPic since sunday. And it works great to be honest > > once you've got the oAuth Echo logic in place. I hope the other > > providers get their acts in order and give us enough time to get > > through the Apple Approval process > > Are you signing the entire multipart body or just signing the request > without the body then tacking it on later?
[twitter-dev] Re: oAuth Echo Enabled Providers
On May 18, 2:08 pm, Rich wrote: > I don't use curl but send it with multipart form data and it's been > working with TwitPic since sunday. And it works great to be honest > once you've got the oAuth Echo logic in place. I hope the other > providers get their acts in order and give us enough time to get > through the Apple Approval process Are you signing the entire multipart body or just signing the request without the body then tacking it on later?
[twitter-dev] Re: oAuth Echo Enabled Providers
I don't use curl but send it with multipart form data and it's been working with TwitPic since sunday. And it works great to be honest once you've got the oAuth Echo logic in place. I hope the other providers get their acts in order and give us enough time to get through the Apple Approval process On May 18, 8:00 pm, uprise78 wrote: > I *just now* got a response from Twitpic and they updated the docs so > maybe it will work nowI'll test in a few hours.
[twitter-dev] Re: oAuth Echo Enabled Providers
I *just now* got a response from Twitpic and they updated the docs so maybe it will work nowI'll test in a few hours.
[twitter-dev] Re: oAuth Echo Enabled Providers
Does TwitPic's oauth echo work? The example on the api.twitpic.com site fails due to the header in the curl call being totally wrong (they put key=value instead of key:value). Changing that to the correct header still fails for me. Has anyone gotten this to work? If so, do you mind posting a quick code example?
