Not currently maintained, but PR/issues/questions welcome.
mtwitter cannot currently help with obtaining access tokens from Twitter, you'll have to do this yourself. For testing and simple apps, the keys can be obtained from dev.twitter.com after setting up a new App.
var Twitter = ;
var twitter =consumer_key: 'Twitter'consumer_secret: 'API'access_token_key: 'keys'access_token_secret: 'go here';
var twitter =consumer_key: configkeyconsumer_secret: configsecretapplication_only: true;
The REST interface is managed, which means it transparently handles rate-limiting (it retries requests and doesn't bombard the APIs), and also takes care of fetching and refreshing configuration data as recommended by Twitter.
// Get a user's timelinetwit;// Search for a phrasetwit;// Post a new statusvar content = status: 'Maybe he\'ll finally find his keys. /@peterfalk';twit;
For the moment, only "raw" access is available:
Originally forked from @AvianFlu's inactive repo,
but reworked heavily, taking inspiration from many people
and their attempts at making it better. Old (pre-rewrite)
contributors can be found in
HISTORICAL. Contributors to
the present iteration can be found in the
CONTRIBUTING.md for details
Topical branches and standard PR etiquette is preferred.
You need to formally agree to release your contribution.
Both linting and testing should pass (the Travis build will fail a PR if there are linting errors):
$ npm test$ npm run-script lint