Those are great tips, Shannon. Thanks!
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, May 20, 2010 at 10:28 PM, Shannon Whitley swhit...@whitleymedia.com
wrote:
I've been keeping track of the major oAuth issues that developers report to
me. I've also hit
Hi,
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.
Hi Anna,
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
You're not trying to post the exact same tweet twice, are you? That
will always return a 403 status code.
-Lucius
On May 21, 5:55 am, Anna annatyler1...@gmail.com wrote:
Hi,
I was also facing that 401 issue till today morning, now its throwing
me 403 error on trying to tweet through code.
I'm now starting to get near constant 401's to oAuth echo requests
when it was working perfectly. It intermittently works, but
litterally 1 in every 10 requests works
On May 20, 10:38 pm, Dossy Shiobara do...@panoptic.com wrote:
AHA! I just checked, somehow my system clock is off (slow) by ~3
Just a quick follow-up to the comment from Damon above, because it was
my app he was testing that broke. It was a client bug. I've confirmed
that everything's working great with xAuth after I fixed it.
Thanks Taylor for the tip about dates/clocks, too.
--
Manton Reece
http://www.manton.org/
I've been keeping track of the major oAuth issues that developers report to
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
