Thanks for the reply. Yes, I did see your earlier post. I was hoping someone from Twitter would have greater insight into which media hosting services they were working with (assuming Twitter would most likely be involved at a corporate level with these other companies), and what features may be lost in the conversion. As I mentioned, I have already tested TwitPic and yFrog. But both no longer support "Upload & Post". Do the others you mentioned also lose that functionality? Img.ly is supposedly in the works. Is anything going on with Posterous? Is the loss of "Upload & Post" a systemic OAuth issue for the time being?
It's not easy for some of us to submit app revisions in rapid succession, and not including functionality in the first place is always better than taking it away later. Any help anyone can provide to help us get it (more right) the first time would be deeply appreciated by all. On May 31, 4:54 am, Rich <rhyl...@gmail.com> wrote: > I posted such a list a week or so back > > I have successfully integrated: > Twitpic > Yfrog (they only allow the XML version of verify_credentials rather > than json) > Twitgoo > Mobypicture > Twitvid > > I believe pikchur also supports it but I haven't had the chance to > test it yet > > On May 31, 1:30 am, Ron <meerkat...@gmail.com> wrote: > > > > > With the clock ticking on Basic Authpocalypse (T-30 days and > > counting), what is the state of media hosting providers with regards > > to OAuth Echo compliance? Those of us developing mobile client apps > > need about two weeks to get our revised apps through the relevant > > approval processes, so we're down to about two weeks left before > > needing to submit something or risk our apps not working anymore. > > > I have successfully tested with TwitPic and yFrog, but both seem to > > have lost Upload & Post functionality when moving to OAuth Echo. > > Img.ly said they're still working on their implementation. Posterous > > is still a ? > > > Can anyone share a list of providers ready to begin testing their new > > OAuth Echo functionality, along with a heads-up about any lost > > functionality resulting from the move? It's becoming increasingly > > important to find out who's going to be on the playing field with what > > functionality so we can revise our apps accordingly in advance of the > > approaching deadline.
