There is an easy workaround for this problem that doesn't require much recoding. It involves rerouting your updates to Twitter via Identi.ca.
Create equivalent accounts on Identi.ca. Change your scripts to update the status on your Identi.ca accounts (which is just a matter of replacing http://twitter.com/statuses/update.json by http://identi.ca/api/statuses/update.json and the "Twitter API" realm by "Identi.ca API"). Set your identi.ca accounts to auto update your twitter accounts. Otto 7is7.com On Sep 3, 8:23 pm, Yardmaps <balazsb...@gmail.com> wrote: > Hi there, > My website, Yardmaps.org, has its own twitter account - actually > there's a twitter account for each city that yardmaps will be > available in. > > When I was coding the site using basic auth, I had a simple function > that would update the twitter status of a given city whenever a yard > sale is posted. Since I own the website, and the twitter accounts, I > don't need to ask a 3rd person for permission to update their status. > Basic auth was perfect. > > However, now that basic auth is no more, I'm not sure how I'm supposed > to use oAuth to do the same thing? > > My database has the username and password for each twitter account, > and when a yard sale is added, i simply want to tweet it out. Since > oAuth doesn't (in my limited understanding) support asynchronous > calls, I don't know how I can upgrade? > > Please help me. > > Thanks > B -- 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?hl=en