Changeset 3f668e47


Ignore:
Timestamp:
2010-04-28T07:38:25Z (15 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
23784065
Parents:
0bff877
Message:

OAuth documentation update.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • doc/user-guide/commands.xml

    r0bff877 r3f668e47  
    7979                                                To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
    8080                                        </para>
     81
     82                                        <para>
     83                                                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 <emphasis>help set oauth</emphasis>.)
     84                                        </para>
    8185                                </description>
    8286                        </bitlbee-command>
    … …  
    703707        </bitlbee-setting>
    704708
     709        <bitlbee-setting name="oauth" type="boolean" scope="account">
     710                <default>true</default>
     711
     712                <description>
     713                        <para>
     714                                This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.
     715                        </para>
     716
     717                        <para>
     718                                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 return a PIN code which you can give back to BitlBee to finish the process.
     719                        </para>
     720
     721                        <para>
     722                                The resulting access token will be saved permanently, so you have to do this only once.
     723                        </para>
     724                </description>
     725
     726        </bitlbee-setting>
     727
    705728        <bitlbee-setting name="ops" type="string" scope="global">
    706729                <default>both</default>
Note: See TracChangeset for help on using the changeset viewer.