By Dave Winer on Friday, April 08, 2011 at 10:26 AM.
First let me say it could well be, probably is, something I did wrong that led to my Twitter/OAuth code to stop working overnight.
I first noticed it a few minutes ago when I posted something to my feed that didn't go through. I checked the database to see what went wrong. It said, "Incorrect signature."
So the first question -- is anyone aware of anything that changed in the Twitter API last night?
Second question -- I'm new to using Twitter's OAuth interface. Is it realiable or flaky or somewhere inbetween?
I don't think it could be a terms-of-service thing because my app is doing exactly the same thing as TwitterFeed, and as far as I know they're still legal. I was using TwitterFeed until a couple of weeks ago, but needed an interface with less latency.
Update: When I posted a link to this item to my feed it got through to Twitter. Now I'm truly puzzled!
Update #2: They're seeing the samething at the Chicago Tribune.