Hi Taylor,

Thank you for the quick reply.

Is there a good reason for that limitation?   Or is there some hope
that in the future request_token will be enhanced to enable
explicit request of a RWD token?

In the mean time, I'll figure out the best way to get by.

Thanks again.

Jeff



On Fri, Jul 01, 2011 at 11:59:11AM -0700, Taylor Singletary wrote:
> Hi Jeff,
> 
> There's no way to specify a RWD option on this method -- if your application
> requires the use of direct messages in any context, you must set that at the
> application level.
> 
> This parameter will only influence the creation of RO or RW tokens.
> 
> @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor
> Singletary
> 
> 
> On Fri, Jul 1, 2011 at 11:42 AM, Jeff Dairiki <dair...@dairiki.org> wrote:
> 
> > To restate my question of yesterday:
> >
> > It has been (and is still) possible to set the "default access type"
> > for ones app to "Read-only", yet still get read/write tokens by passing
> > "x_auth_access_type=write" to /oauth/request_token.
> >
> > Is there a corresponding value for x_auth_access_type which will
> > yield a read/write/direct-message token?
> >
> > (The docs at http://dev.twitter.com/doc/post/oauth/request_token list
> > only the choices 'read' and 'write'.  If there really is no third
> > value to be used to request a r/w/dm token, this would seem to me ---
> > in light of the recent permission model changes --- to be an
> > oversight.)
> >
> > I've just filed a ticket on this:
> >
> >  http://code.google.com/p/twitter-api/issues/detail?id=2258
> >
> > Thanks for any help!
> >
> > Jeff
> >

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to