- Timestamp:
- 2011-08-01T09:53:48Z (13 years ago)
- Branches:
- master
- Children:
- 6e9ae72
- Parents:
- 7732193
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
r7732193 r87dddee 1126 1126 <description> 1127 1127 <para> 1128 This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.1129 </para> 1130 1131 <para> 1132 With OAuth enabled, you shouldn't tell BitlBee your Twitter password. Just add your account with a bogus password and type <emphasis>account on</emphasis>. BitlBee will then give you a URL to authenticate with Twitter. If this succeeds, Twitter will returna PIN code which you can give back to BitlBee to finish the process.1133 </para> 1134 1135 <para> 1136 The resulting access token will be saved permanently, so you have to do this only once. 1128 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. 1129 </para> 1130 1131 <para> 1132 With OAuth enabled, you shouldn't tell BitlBee your Twitter password. Just add your account with a bogus password and type <emphasis>account on</emphasis>. 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. 1133 </para> 1134 1135 <para> 1136 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 <emphasis>account set</emphasis> to reset the account password to something random. 1137 1137 </para> 1138 1138 </description>
Note: See TracChangeset
for help on using the changeset viewer.