From f59e1eb491a6702b70b141775f542e00521906f5 Mon Sep 17 00:00:00 2001 From: =?utf8?q?L=2E=20Alberto=20Gim=C3=A9nez?= Date: Sun, 9 Jan 2011 17:02:04 +0100 Subject: [PATCH 1/1] Document how to configure OAuth. MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: L. Alberto Giménez --- README | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/README b/README index ff709f7..caf348f 100644 --- a/README +++ b/README @@ -17,3 +17,26 @@ bti is developed using git and the tree can be found at: git://github.com/gregkh/bti.git and browsed at: http://github.com/gregkh/bti/ + + +About OAuth configuration + +If you want to use an OAuth-enabled service (like twitter), you should configure bti to use the +consumer key and secret shipped with the source code (check the oath.keys file). + +For example, you should add the following two lines to your ~/.bti configuration +file: + +---8<------------------- +# Consumer key +consumer_key=cZy8DdioswAfu3LJYg6E2w + +# Consumer secret +consumer_secret=fnIGGU0T12mMWKjmThUdSeKN32NLWfmnwapwubVQ +---8<------------------- + +The next time that you run bti, you will be told to visit an URL that will +provide you a PIN number. You should then input that number in the bti prompt, +and you will be given two new configuration values +(access_token_secret and access_token_key) that you need to add to your +bti configuration file to authenticate requests from bti. -- 2.39.5