Changes in doc/user-guide/commands.xml [9997691:0f84234]

File:

• doc/user-guide/commands.xml (modified) (4 diffs)

doc/user-guide/commands.xml

@@ -79 +79 @@
                                                 To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
                                         </para>
-
-                                        <para>
-                                                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>.)
-                                        </para>
                                 </description>
                         </bitlbee-command>
@@ -663 +659 @@
         </bitlbee-setting>
 
-        <bitlbee-setting name="message_length" type="integer" scope="account">
-                <default>140</default>
-
-                <description>
-                        <para>
-                                Since Twitter rejects messages longer than 140 characters, BitlBee can count message length and emit a warning instead of waiting for Twitter to reject it.
-                        </para>
-
-                        <para>
-                                You can change this limit here but this won't disable length checks on Twitter's side. You can also set it to 0 to disable the check in case you believe BitlBee doesn't count the characters correctly.
-                        </para>
-                </description>
-
-        </bitlbee-setting>
-
         <bitlbee-setting name="mode" type="string" scope="account">
                 <possible-values>one, many, chat</possible-values>
@@ -722 +703 @@
         </bitlbee-setting>
 
-        <bitlbee-setting name="oauth" type="boolean" scope="account">
-                <default>true</default>
-
-                <description>
-                        <para>
-                                This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.
-                        </para>
-
-                        <para>
-                                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.
-                        </para>
-
-                        <para>
-                                The resulting access token will be saved permanently, so you have to do this only once.
-                        </para>
-                </description>
-
-        </bitlbee-setting>
-
         <bitlbee-setting name="ops" type="string" scope="global">
                 <default>both</default>
@@ -872 +834 @@
                         <para>
                                 Can be set for Jabber- and OSCAR-connections. For Jabber, you might have to set this if the servername isn't equal to the part after the @ in the Jabber handle. For OSCAR this shouldn't be necessary anymore in recent BitlBee versions.
-                        </para>
-                </description>
-        </bitlbee-setting>
-
-        <bitlbee-setting name="show_offline" type="boolean" scope="global">
-                <default>false</default>
-
-                <description>
-                        <para>
-                                If enabled causes BitlBee to also show offline users in Channel. Online-users will get op, away-users voice and offline users none of both. This option takes effect as soon as you reconnect.
                         </para>
                 </description>