From 87dddee3a14d7755204d6fc4b321729bad02ce4e Mon Sep 17 00:00:00 2001 From: Wilmer van der Gaast Date: Mon, 1 Aug 2011 10:53:48 +0100 Subject: Doc update, OAuth is available for more than just Twitter now. --- doc/user-guide/commands.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/user-guide') diff --git a/doc/user-guide/commands.xml b/doc/user-guide/commands.xml index 74310d5e..a3b68fa9 100644 --- a/doc/user-guide/commands.xml +++ b/doc/user-guide/commands.xml @@ -1125,15 +1125,15 @@ - This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory. + This enables OAuth authentication for accounts that support it; right now Twitter and Google Talk (if you have 2-factor authentication enabled on your account) support it. - 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. + 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 the service. If this succeeds, you will get 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. + The resulting access token will be saved permanently, so you have to do this only once. If for any reason you want to/have to reauthenticate, you can use account set to reset the account password to something random. -- cgit v1.2.3