[twitter-dev] Re: Rate limiting questions

2011-07-06 Thread YupiqDZ 
Hi there,

My application gives Read, Write and Direct Message permissions.
Additionally, I was able to retrieve direct messages using the
appropriate access tokens earlier in the day, now none of it works.

Is there some specific thing I need to do in order to have the
permission level of these tokens set beyond the normal OAuth process?

Thanks for the help.

On Jul 5, 7:46 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Hi there,

 This is actually a different error than your library may be leading you to
 believe -- the library is suggesting that the 403 may be due to rate
 limiting, but in this case it's actually due to a recent permission model
 change.

 The permission model gas change whereas requesting a user's direct messages
 now requires a re-authorization at the appropriate access request level
 (RWD). You can read more about the new permission model and what to do next
 here:http://dev.twitter.com/pages/application-permission-model..

 @episod http://twitter.com/intent/user?screen_name=episod - Taylor
 Singletary







 On Tue, Jul 5, 2011 at 1:35 PM, YupiqDZ mrclea...@gmail.com wrote:
  Hi,

  I'm currently in the process of writing an application which
  periodically gets directed messages from a user (once every 120
  seconds checks if the user has new messages).

  The API I am using is the Twitter4j library in Java. Here's the error
  I get:

  403:The request is understood, but it has been refused.  An
  accompanying error message will explain why.
  TwitterException{exceptionCode=[ece01d6a-01eb72d6], statusCode=403,
  retryAfter=0,
  rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=326,
  hourlyLimit=350, resetTimeInSeconds=1309899, secondsUntilReset=1629,
  resetTime=Tue Jul 05 13:58:10 PDT 2011}, version=2.1.10}

  I am confused as to how my remainingHIts is still 326 yet I am rate
  limited? Additionally, even if I wait until the reset time indicated
  before hitting the service again, I receive the rate limit exception
  again with the reset time pushed back by an hour.

  I am fairly confident that this service does not poll Twitter more
  than 350 times a second, is there something else that could be causing
  me to be rate limited?

  Thanks

  --
  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

-- 
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

[twitter-dev] Re: Rate limiting questions

2011-07-06 Thread YupiqDZ 
I figured out what was happening.

It looks like I was using the AuthenticationURL instead of the
AuthorizationURL and this was causing me to not obtain the proper
permissions.

Thank for your help!

On Jul 6, 9:40 am, YupiqDZ mrclea...@gmail.com wrote:
 Hi there,

 My application gives Read, Write and Direct Message permissions.
 Additionally, I was able to retrieve direct messages using the
 appropriate access tokens earlier in the day, now none of it works.

 Is there some specific thing I need to do in order to have the
 permission level of these tokens set beyond the normal OAuth process?

 Thanks for the help.

 On Jul 5, 7:46 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:







  Hi there,

  This is actually a different error than your library may be leading you to
  believe -- the library is suggesting that the 403 may be due to rate
  limiting, but in this case it's actually due to a recent permission model
  change.

  The permission model gas change whereas requesting a user's direct messages
  now requires a re-authorization at the appropriate access request level
  (RWD). You can read more about the new permission model and what to do next
  here:http://dev.twitter.com/pages/application-permission-model..

  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary

  On Tue, Jul 5, 2011 at 1:35 PM, YupiqDZ mrclea...@gmail.com wrote:
   Hi,

   I'm currently in the process of writing an application which
   periodically gets directed messages from a user (once every 120
   seconds checks if the user has new messages).

   The API I am using is the Twitter4j library in Java. Here's the error
   I get:

   403:The request is understood, but it has been refused.  An
   accompanying error message will explain why.
   TwitterException{exceptionCode=[ece01d6a-01eb72d6], statusCode=403,
   retryAfter=0,
   rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=326,
   hourlyLimit=350, resetTimeInSeconds=1309899, secondsUntilReset=1629,
   resetTime=Tue Jul 05 13:58:10 PDT 2011}, version=2.1.10}

   I am confused as to how my remainingHIts is still 326 yet I am rate
   limited? Additionally, even if I wait until the reset time indicated
   before hitting the service again, I receive the rate limit exception
   again with the reset time pushed back by an hour.

   I am fairly confident that this service does not poll Twitter more
   than 350 times a second, is there something else that could be causing
   me to be rate limited?

   Thanks

   --
   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

-- 
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

[twitter-dev] Rate limiting questions

2011-07-05 Thread YupiqDZ 
Hi,

I'm currently in the process of writing an application which
periodically gets directed messages from a user (once every 120
seconds checks if the user has new messages).

The API I am using is the Twitter4j library in Java. Here's the error
I get:

403:The request is understood, but it has been refused.  An
accompanying error message will explain why.
TwitterException{exceptionCode=[ece01d6a-01eb72d6], statusCode=403,
retryAfter=0,
rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=326,
hourlyLimit=350, resetTimeInSeconds=1309899, secondsUntilReset=1629,
resetTime=Tue Jul 05 13:58:10 PDT 2011}, version=2.1.10}

I am confused as to how my remainingHIts is still 326 yet I am rate
limited? Additionally, even if I wait until the reset time indicated
before hitting the service again, I receive the rate limit exception
again with the reset time pushed back by an hour.

I am fairly confident that this service does not poll Twitter more
than 350 times a second, is there something else that could be causing
me to be rate limited?

Thanks

-- 
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