From 3f668e478bbaa062cf6b01e627cb39885200e5ff Mon Sep 17 00:00:00 2001 From: Wilmer van der Gaast Date: Wed, 28 Apr 2010 08:38:25 +0100 Subject: OAuth documentation update. --- doc/user-guide/commands.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'doc/user-guide') diff --git a/doc/user-guide/commands.xml b/doc/user-guide/commands.xml index a8f030b2..9fcc91da 100644 --- a/doc/user-guide/commands.xml +++ b/doc/user-guide/commands.xml @@ -78,6 +78,10 @@ To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option. + + + Since Twitter now requires OAuth authentication, you should not enter your Twitter password into BitlBee. Just type a bogus password. The first time you log in, BitlBee will start OAuth authentication. (See help set oauth.) + @@ -702,6 +706,25 @@ + + true + + + + This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory. + + + + With OAuth enabled, you shouldn't tell BitlBee your Twitter password. Just add your account with a bogus password and type account on. BitlBee will then give you a URL to authenticate with Twitter. If this succeeds, Twitter will return a PIN code which you can give back to BitlBee to finish the process. + + + + The resulting access token will be saved permanently, so you have to do this only once. + + + + + both both, root, user, none -- cgit v1.2.3