There is no secure method to accomplish this purely in Javascript, as you would have to hard code your consumer key & consumer secret as well as an oauth_token and oauth_token_secret for the Twitter account you want to use for all operations. With these pieces of information, anyone would be able to tweet on behalf of your application and account.
In a case like this, you'd want to implement most of this logic server-side, where you can keep the hard-coded credentials securely. You could potentially use Javascript to speak to your own servers to hustle the process along. We offer a feature on dev.twitter.com that allows you to easily obtain an access token for the user who "owns" the application, which would at least help you in that you'd not have to implement the negotiation steps of OAuth. Taylor On Sun, Aug 29, 2010 at 11:13 AM, Matthew Cornell <matthewcorn...@gmail.com>wrote: > I'd like to see this too. > > -- > 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 > -- 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
