Hi Guys, thanks for the information. I'm sure the authentication is successful. I use the secret_tokens to post that I had generated.
This is running on my own server and no other app/program on that server is accessing Twitter. Someone else mentioned that it might also return a 403 error if the tweet is a duplicate of the last one tweeted. They suggested that I keep a check of the last successful tweet and make sure that the next one does not match that. Fair enough, but I don't think that's the case here... Here are the 3 most recent failed messages I received today: This one came in at 8 AM Random Listing (CRON) Auction ID: 101802 Name: BABY FURITURE Start Bid: 5.00 URL: http://bit.ly/aUsmpn Error Message: Request has been refused. Possible causes: denied due to update limits. The next one came in at 10 AM (exactly 2 hours later, just like it's supposed to) Random Listing (CRON) Auction ID: 101792 Name: Queen-Size Headboard Start Bid: 1.50 URL: http://bit.ly/auj0eV Error Message: Request has been refused. Possible causes: denied due to update limits. And this last one came in at 12 PM (again 2 hours later) Random Listing (CRON) Auction ID: 101839 Name: Steel Butterfly Wall Hanging Start Bid: 2.50 URL: http://bit.ly/cJhdRc Error Message: Request has been refused. Possible causes: denied due to update limits. So as you can see, all 3 are different auctions, and all 3 failed. I'm not yet sure how to get back any other message from Twitter on what the actual cause is. I only get back an error number (in this case 403) and I look that number up in a table that has the corresponding error message tied to it, as found here: http://apiwiki.twitter.com/w/page/22554652/HTTP-Response-Codes-and-Errors If anyone has any idea how to get back the additional response as DaveH recommends above, please let me know. Thanks again. Peter On Nov 2, 6:41 pm, DaveH <d...@idreia.com> wrote: > Yaemog: > > You are right, he does say he is posting to his Twitter Page and that > he is using oAuth. My bad... > > So there is something else going on. > > - Check that authentication was successful. The rate limit should be > higher if he has successfully authenticated. > - Check the return message from Twitter. When I see a 403 Twitter also > sends a response that tells me why the 403 was returned. > - Make sure there is no other program using the same Twitter > Application name; the other application will draw down the rate limit. > > On Nov 2, 10:00 am, yaemog Dodigo <yae...@gmail.com> wrote: > > > > You mention 150/hour so I am guessing that you are not authenticating > > > with Twitter. This means that if there are any other applications > > > sharing the same IP address (shared hosting) then they are also using > > > the same rate limit as your app. If you authenticate you will get the > > > 250/hour ratelimit and it will be all yours to consume. > > > > Dave > > > Hi Dave, > > > When I read Peter's post, I thought of the same thing. However, since he is > > successfully posting, wouldn't that require to be authenticated? > > > --d -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk