Re: [twitter-dev] Direct message change and the authentication URL

2011-06-15 Thread James Estes
I think this was addressed in the "A new permission level thread. "> You said you were restricting this permission to the OAuth /authorize web flow only. Will /oauth/authenticate (Sign in with Twitter) support the new permission? The R/W/DM permission can only be granted through the /oauth/author

Re: [twitter-dev] Stream throttled

2011-05-31 Thread James Estes
> Is this a known problem or are we getting throttled? You are likely getting rate limited. http://dev.twitter.com/pages/streaming_api_concepts#filter-limiting "Limiter periodicity is aligned with statuses/sample sampling periodicity" Basically, this means that if you're predicates would return MO

Re: [twitter-dev] Re: A new permission level

2011-05-25 Thread James Estes
Arnaud replied recently indicating that the header is now in: "We just started to return the "X-Access-Level" header for authenticated API requests, that tells you what access level the user token has" http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5bf53b81f2d868c/87

Re: [twitter-dev] Re: Streaming API credentials

2011-05-23 Thread James Estes
You're right. The simplest (only?) way would be to create an account specifically for managing your app. I believe there was a recent post on this list talking about that being the norm, but I couldn't find it. I'd love for the app to have it's own credentials, and allow for assigning multiple t

Re: [twitter-dev] Checking whether a user has given permission to Private Messages

2011-05-23 Thread James Estes
I don't think so, but looks like its coming soon. 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 t

Re: [twitter-dev] Re: Authorize vs. Authenticate

2011-05-23 Thread James Estes
gt; complaints, it got too hard to follow. > > From my testing, I am pretty sure authorize supports callback urls. > > Any idea about authenticate and private messages?  Is this permission > not available in the authenticate flow by design, or is this a bug? > > . > On May 23, 3:0

Re: [twitter-dev] Authorize vs. Authenticate

2011-05-23 Thread James Estes
I believe the only difference is that the authenticate route could be used by only web based applications (ie they need to have a callback url) and allows for the force_login param. The authenticate can be used by either desktop or web apps, but do not support the force_login...but this may be cha

Re: [twitter-dev] Streaming API credentials

2011-05-23 Thread James Estes
You would create a twitter app at https://dev.twitter.com/apps After you create it, there is a "My Access Token" button on the details page for your application. I /believe/ that will get you what you want. James On Mon, May 23, 2011 at 3:04 PM, Craig Walls wrote: > > I'd like to use the strea