aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user-guide/misc.xml
diff options
context:
space:
mode:
authordequis <dx@dxzone.com.ar>2016-12-25 19:07:48 -0300
committerdequis <dx@dxzone.com.ar>2016-12-25 21:18:55 -0300
commit1999fe5eadc7c7575e33542da42b0e21b10366d9 (patch)
tree2a99dc97fa68a9f407cc00f6e052f4419a043aba /doc/user-guide/misc.xml
parent15a8c94f4e559bf7b9f201bd1b93e816948a5d43 (diff)
Misc documentation updates
- Remove a bunch of mentions of yahoo - Remove 'smileys' topic from help index - Add 'identify_methods' help topic - Mention new commands like 'chat list' or 'plugins'
Diffstat (limited to 'doc/user-guide/misc.xml')
-rw-r--r--doc/user-guide/misc.xml39
1 files changed, 38 insertions, 1 deletions
diff --git a/doc/user-guide/misc.xml b/doc/user-guide/misc.xml
index 36720914..a95c5442 100644
--- a/doc/user-guide/misc.xml
+++ b/doc/user-guide/misc.xml
@@ -76,9 +76,12 @@ Then, just use the ordinary IRC <emphasis>/invite</emphasis> command to invite m
</para>
<para>
-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.
+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.
</para>
+<para>
+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.
+</para>
</sect1>
<sect1 id="away">
@@ -267,6 +270,40 @@ everything in the handle up to the first @.
</sect1>
+<sect1 id="identify_methods">
+<title>Identifying to your BitlBee account</title>
+
+<para>There are several methods to identify (log in) to your registered BitlBee account. All of these are equivalent:</para>
+
+<variablelist>
+ <varlistentry>
+ <term>The 'identify' command</term>
+ <listitem><para>sent to &amp;bitlbee or root. See <emphasis>help identify</emphasis> for details.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>/msg nickserv identify</term>
+ <listitem><para>Same as above, but sent to NickServ. Useful with some auto-identify scripts.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>/nickserv or /ns</term>
+ <listitem><para>Same as above, but using the command aliases to NickServ.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Server password</term>
+ <listitem><para>A field in the server connection settings of your irc client.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>SASL PLAIN</term>
+ <listitem><para>A newer method, good choice if your client supports it. (Note: "SASL" is <emphasis>not</emphasis> related to "SSL")</para></listitem>
+ </varlistentry>
+</variablelist>
+
+<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>
+
+<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>
+
+</sect1>
+
<sect1 id="whatsnew010206">
<title>New stuff in BitlBee 1.2.6</title>