Changeset 1999fe5 for doc/user-guide/misc.xml
- Timestamp:
- 2016-12-26T00:18:55Z (7 years ago)
- Branches:
- master
- Children:
- 6908ab7
- Parents:
- 15a8c94
- git-author:
- dequis <dx@…> (25-12-16 22:07:48)
- git-committer:
- dequis <dx@…> (26-12-16 00:18:55)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/misc.xml
r15a8c94 r1999fe5 77 77 78 78 <para> 79 Some protocols (like Jabber) also support named groupchats. BitlBee now supports these too. You can use the <emphasis>chat add</emphasis> command to join them. See <emphasis>help chat add</emphasis> for more information. 80 </para> 81 79 Some protocols (like Jabber) also support named groupchats. BitlBee supports these too. You can use the <emphasis>chat add</emphasis> command to join them. See <emphasis>help chat add</emphasis> for more information. 80 </para> 81 82 <para> 83 If you don't know the name of a named groupchat, you can try the <emphasis>chat list</emphasis> command to get a list of chatrooms from a server. See <emphasis>help chat list</emphasis> for usage instructions. 84 </para> 82 85 </sect1> 83 86 … … 265 268 everything in the handle up to the first @. 266 269 </para> 270 271 </sect1> 272 273 <sect1 id="identify_methods"> 274 <title>Identifying to your BitlBee account</title> 275 276 <para>There are several methods to identify (log in) to your registered BitlBee account. All of these are equivalent:</para> 277 278 <variablelist> 279 <varlistentry> 280 <term>The 'identify' command</term> 281 <listitem><para>sent to &bitlbee or root. See <emphasis>help identify</emphasis> for details.</para></listitem> 282 </varlistentry> 283 <varlistentry> 284 <term>/msg nickserv identify</term> 285 <listitem><para>Same as above, but sent to NickServ. Useful with some auto-identify scripts.</para></listitem> 286 </varlistentry> 287 <varlistentry> 288 <term>/nickserv or /ns</term> 289 <listitem><para>Same as above, but using the command aliases to NickServ.</para></listitem> 290 </varlistentry> 291 <varlistentry> 292 <term>Server password</term> 293 <listitem><para>A field in the server connection settings of your irc client.</para></listitem> 294 </varlistentry> 295 <varlistentry> 296 <term>SASL PLAIN</term> 297 <listitem><para>A newer method, good choice if your client supports it. (Note: "SASL" is <emphasis>not</emphasis> related to "SSL")</para></listitem> 298 </varlistentry> 299 </variablelist> 300 301 <para>To configure your client to auto-identify, the last two methods are recommended. SASL if you have it, but server password is often the easiest.</para> 302 303 <para>Note: If you changed bitlbee.conf to have <emphasis>AuthMode = Closed</emphasis>, server password will be used for that instead. If you have never heard of that setting before, you can ignore it and just use it.</para> 267 304 268 305 </sect1>
Note: See TracChangeset
for help on using the changeset viewer.