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 <rhyl...@gmail.com> wrote: > Look's like TwitPic's oAuth Echo has broken again, can anyone else > confirm? > > On May 20, 9:49 pm, Justin Hart <onyxra...@gmail.com> 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 <onyxra...@gmail.com> 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 <rhyl...@gmail.com> 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?