From aac9499315ab5600646cafb436bc832fa8895d47 Mon Sep 17 00:00:00 2001 From: Michael Gubik Date: Tue, 16 Feb 2021 18:39:10 +0000 Subject: [PATCH] Token names consistent with Twitter doc The placeholders and comments were a bit confusing in my opinion. I made them consistent with the Twitter documentation and added comments to make it absolutely clear to which tokens in the Twitter Developer Portal these correspond. --- Readme.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Readme.md b/Readme.md index bfbb8058..60eaa22d 100644 --- a/Readme.md +++ b/Readme.md @@ -32,16 +32,15 @@ describe('OAuth1.0',function(){ var oauth = new OAuth.OAuth( 'https://api.twitter.com/oauth/request_token', 'https://api.twitter.com/oauth/access_token', - 'your application consumer key', - 'your application secret', - '1.0A', + 'your consumer_key', // API key from section "Consumer Keys" in the Twitter Developer Portal + 'your consumer_secret', // secret null, 'HMAC-SHA1' ); oauth.get( 'https://api.twitter.com/1.1/trends/place.json?id=23424977', - 'your user token for this app', //test user token - 'your user secret for this app', //test user secret + 'your access_token', // Access token from section "Authentication Tokens" in the Twitter Developer Portal + 'your token_secret', // secret function (e, data, res){ if (e) console.error(e); console.log(require('util').inspect(data));