The large points of load are just about to hit. 401s and 403s where they
aren't appropriate is an unfortunate side effect of the way certain kinds of
load are expressing themselves in the system right now. We have a
multi-tiered effort to get this back to an acceptable state.
The best advice I have for now is to, if possible, not aggressively retry
when a failure occurs. If you get an invalid nonce error while posting a
status, and you're otherwise certain the nonce is unique, ignore the
exception and assume the tweet was posted. Other areas where the problems
express themselves: home_timeline and mentions aren't updating as frequently
as you may be used to.
Thanks for your patience!
Developer Advocate, Twitter
On Fri, May 21, 2010 at 2:55 AM, Anna <annatyler1...@gmail.com> wrote:
> I was also facing that 401 issue till today morning, now its throwing
> me 403 error on trying to tweet through code. However other
> functionalities are working fine.
> The application is granted with both "read and write" access. I havent
> done any code changes or modified any application settings.
> Any suggestions ?
> On May 21, 10:28 am, Shannon Whitley <swhit...@whitleymedia.com>
> > I've been keeping track of the major oAuth issues that developers report
> > me. I've also hit these a few times myself.
> > 1. The date/time on your machine must be accurate. Make sure you’ve
> > performed a recent sync with a known time source.
> > 2. If you’re trying to call a Twitter API method that will update
> > the oAuth setup must be Read/Write on Twitter.com/oAuth.
> > 3. Recheck all of your querystring variables for proper encoding. The
> > method that you use for encoding querystring variables may not be
> > compliant.