Any further news on this? It's been three weeks since you were "hoping to roll [it] out more widely this week". I've got an app registered and am starting to code it up, but would like to use the key_exchange method instead, since there's no way at all to hide the consumer secret in a python script.
Thanks, - Johnson On Jun 28, 8:02 am, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > The answer is soon! :) We hope to roll this out more widely this week. > > On Mon, Jun 28, 2010 at 7:56 AM, Decklin Foster <deck...@red-bean.com>wrote: > > > Taylor Singletary wrote: > > > We're waiting on a few minor bug fixes to be in place before rolling this > > > out to a wider audience. I'll post a new message when things are good to > > go > > > and we're ready to accept applications into the feature. > > > Any update or ETA on this? I have an app that I'm eager to test out. > > (I notice that if you openhttp://dev.twitter.com/apps/key_exchange > > with a valid oauth_consumer_key, instead of a 404 there is a page that > > says "Sorry, key exchange is not permitted for this application." Does > > this mean the answer is "soon"?) > > > -- > > things change. > > deck...@red-bean.com