Hi,
The doc says, “read-write-directmessages” (Read, Write, Direct Message)
But actually I get read-write-privatemessages as you mentioned.
It's a doc bug, right?
Best,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on :
Hi Yusuke,
We are standardizing the phrasing to match the API requests so in this case the
docs are correct.
We have a fix to correct messages to 'direct' instead of 'private' on it's way.
@themattharris
On Jun 5, 2011, at 23:41, Yusuke Yamamoto yus...@mac.com wrote:
Hi,
The doc says,
The FAQ onhttp://dev.twitter.com/pages/application-permission-model-faqwill
be udpated in a minute :)
Here's the URL
http://dev.twitter.com/pages/application-permission-model-faq
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter:
I think I found the answer from themattharris:
How do we know what the access level of a user token is?
This is a great idea and one the team has discussed. What we are
going
to do is add a new header to authentication requests that will tell
you the access level of the token you authenticated
We just started to return the X-Access-Level header for authenticated API
requests, that tells you what access level the user token has:
- read (Read-only)
- read-write (Read Write)
- read-write-privatemessages (Read, Write, Private Message)
The FAQ on
Hey again,
For more consistency, the X-Access-Level header value for the Read, Write
Direct Message scope is going to be read-write-directmessages (rather
than read-write-privatemessages). We'll also update the Client Application
management pages (using Direct Messages and not Private Messages)
