It may have corresponded with a spike of activity on Twitter -- our current authentication implementation has some unfortunate side effects when stressed, and one of them is to return spurious 401s.
Are you still seeing the issue? On Sat, Jun 26, 2010 at 11:39 AM, Udi <udi....@gmail.com> wrote: > we recently (24-48 hours ago) started getting "incorrect signature" > errors for some of our users. accessing the twitter api with the same > software and the same auth data from a different location works fine. > for one user there were only issues with home_timeline.json but > user_timeline.json worked fine. > > any ideas? > > thanks, > udi >