source: doc/user-guide/commands.xml @ 70d7795

Last change on this file since 70d7795 was 508588a, checked in by Wilmer van der Gaast <wilmer@…>, at 2010-10-07T06:32:06Z

Merging smpq fix from pesco.
  • Property mode set to 100644
File size: 66.1 KB
Line 
1<chapter id="commands">
2        <title>Bitlbee commands</title>
3
4        <command-list/>
5
6        <bitlbee-command name="account">
7                <short-description>IM-account list maintenance</short-description>
8                <syntax>account [&lt;account id&gt;] &lt;action&gt; [&lt;arguments&gt;]</syntax>
9
10                <description>
11
12                        <para>
13                                Available actions: add, del, list, on, off and set. See <emphasis>help account &lt;action&gt;</emphasis> for more information.
14                        </para>
15
16                </description>
17
18                <bitlbee-command name="add">
19                        <syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt;</syntax>
20
21                        <description>
22                                <para>
23                                        Adds an account on the given server with the specified protocol, username and password to the account list. Supported protocols right now are: Jabber, MSN, OSCAR (AIM/ICQ), Yahoo and Twitter. For more information about adding an account, see <emphasis>help account add &lt;protocol&gt;</emphasis>.
24                                </para>
25                        </description>
26                       
27                        <bitlbee-command name="jabber">
28                                <syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
29
30                                <description>
31                                        <para>
32                                                The handle should be a full handle, including the domain name. You can specify a servername if necessary. Normally BitlBee doesn't need this though, since it's able to find out the server by doing DNS SRV lookups.
33                                        </para>
34
35                                        <para>
36                                                In previous versions it was also possible to specify port numbers and/or SSL in the server tag. This is deprecated and should now be done using the <emphasis>account set</emphasis> command. This also applies to specifying a resource in the handle (like <emphasis>wilmer@bitlbee.org/work</emphasis>).
37                                        </para>
38                                </description>
39                        </bitlbee-command>
40
41                        <bitlbee-command name="msn">
42                                <syntax>account add msn &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
43
44                                <description>
45                                        <para>
46                                                For MSN connections there are no special arguments.
47                                        </para>
48                                </description>
49                        </bitlbee-command>
50                       
51                        <bitlbee-command name="oscar">
52                                <syntax>account add oscar &lt;handle&gt; &lt;password&gt;</syntax>
53
54                                <description>
55                                        <para>
56                                                OSCAR is the protocol used to connect to AIM and/or ICQ. The servers will automatically detect if you're using a numeric or non-numeric username so there's no need to tell which network you want to connect to.
57                                        </para>
58                                </description>
59
60                                <ircexample>
61                                        <ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
62                                        <ircline nick="root">Account successfully added</ircline>
63                                </ircexample>
64                        </bitlbee-command>
65                       
66                        <bitlbee-command name="twitter">
67                                <syntax>account add twitter &lt;handle&gt; &lt;password&gt;</syntax>
68
69                                <description>
70                                        <para>
71                                                This module gives you simple access to Twitter. Although it uses the Twitter API, only Twitter itself is supported at the moment.
72                                        </para>
73                                       
74                                        <para>
75                                                By default all your Twitter contacts will appear in a new channel called #twitter_yourusername. You can change this behaviour using the <emphasis>mode</emphasis> setting (see <emphasis>help set mode</emphasis>).
76                                        </para>
77                                       
78                                        <para>
79                                                To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
80                                        </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>
85                                </description>
86                        </bitlbee-command>
87
88                        <bitlbee-command name="yahoo">
89                                <syntax>account add yahoo &lt;handle&gt; &lt;password&gt;</syntax>
90
91                                <description>
92                                        <para>
93                                                For Yahoo! connections there are no special arguments.
94                                        </para>
95                                </description>
96                        </bitlbee-command>
97
98                </bitlbee-command>
99
100                <bitlbee-command name="del">
101                        <syntax>account &lt;account id&gt; del</syntax>
102
103                        <description>
104                                <para>
105                                        This commands deletes an account from your account list. You should signoff the account before deleting it.
106                                </para>
107
108
109                                <para>
110                                        The account ID can be a number/tag (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
111                                </para>
112                        </description>
113                </bitlbee-command>
114
115                <bitlbee-command name="on">
116                        <syntax>account [&lt;account id&gt;] on</syntax>
117
118                        <description>
119                                <para>
120                                        This command will try to log into the specified account. If no account is specified, BitlBee will log into all the accounts that have the auto_connect flag set.
121                                </para>
122
123                                <para>
124                                        The account ID can be a number/tag (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
125                                </para>
126                        </description>
127
128                </bitlbee-command>
129
130                <bitlbee-command name="off">
131                        <syntax>account [&lt;account id&gt;] off</syntax>
132
133                        <description>
134                                <para>
135                                        This command disconnects the connection for the specified account. If no account is specified, BitlBee will deactivate all active accounts and cancel all pending reconnects.
136                                </para>
137
138                                <para>
139                                        The account ID can be a number/tag (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
140                                </para>
141                        </description>
142                </bitlbee-command>
143
144                <bitlbee-command name="list">
145                        <syntax>account list</syntax>
146
147                        <description>
148                                <para>
149                                        This command gives you a list of all the accounts known by BitlBee.
150                                </para>
151                        </description>
152                </bitlbee-command>
153
154                <bitlbee-command name="set">
155                        <syntax>account &lt;account id&gt; set</syntax>
156                        <syntax>account &lt;account id&gt; set &lt;setting&gt;</syntax>
157                        <syntax>account &lt;account id&gt; set &lt;setting&gt; &lt;value&gt;</syntax>
158                        <syntax>account &lt;account id&gt; set -del &lt;setting&gt;</syntax>
159
160                        <description>
161                                <para>
162                                        This command can be used to change various settings for IM accounts. For all protocols, this command can be used to change the handle or the password BitlBee uses to log in and if it should be logged in automatically. Some protocols have additional settings. You can see the settings available for a connection by typing <emphasis>account &lt;account id&gt; set</emphasis>.
163                                </para>
164                               
165                                <para>
166                                        For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
167                                </para>
168                               
169                                <para>
170                                        The account ID can be a number/tag (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
171                                </para>
172                        </description>
173                </bitlbee-command>
174        </bitlbee-command>
175
176        <bitlbee-command name="channel">
177                <short-description>Channel list maintenance</short-description>
178                <syntax>channel [&lt;account id&gt;] &lt;action&gt; [&lt;arguments&gt;]</syntax>
179
180                <description>
181                        <para>
182                                Available actions: del, list, set. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
183                        </para>
184                       
185                        <para>
186                                There is no <emphasis>channel add</emphasis> command. To create a new channel, just use the IRC <emphasis>/join</emphasis> command. See also <emphasis>help channels</emphasis> and <emphasis>help groupchats</emphasis>.
187                        </para>
188                </description>
189
190                <bitlbee-command name="del">
191                        <syntax>channel &lt;channel id&gt; del</syntax>
192
193                        <description>
194                                <para>
195                                        Remove a channel and forget all its settings. You can only remove channels you're not currently in, and can't remove the main control channel. (You can, however, leave it.)
196                                </para>
197                        </description>
198
199                </bitlbee-command>
200
201                <bitlbee-command name="list">
202                        <syntax>channel list</syntax>
203
204                        <description>
205                                <para>
206                                        This command gives you a list of all the channels you configured.
207                                </para>
208                        </description>
209
210                </bitlbee-command>
211
212                <bitlbee-command name="set">
213                        <syntax>channel [&lt;channel id&gt;] set</syntax>
214                        <syntax>channel [&lt;channel id&gt;] set &lt;setting&gt;</syntax>
215                        <syntax>channel [&lt;channel id&gt;] set &lt;setting&gt; &lt;value&gt;</syntax>
216                        <syntax>channel [&lt;channel id&gt;] set -del &lt;setting&gt;</syntax>
217
218                        <description>
219                                <para>
220                                        This command can be used to change various settings for channels. Different channel types support different settings. You can see the settings available for a channel by typing <emphasis>channel &lt;channel id&gt; set</emphasis>.
221                                </para>
222                               
223                                <para>
224                                        For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
225                                </para>
226                               
227                                <para>
228                                        The channel ID can be a number (see <emphasis>channel list</emphasis>), or (part of) its name, as long as it matches only one channel. If you want to change settings of the current channel, you can omit the channel ID.
229                                </para>
230                        </description>
231                </bitlbee-command>
232
233        </bitlbee-command>
234
235        <bitlbee-command name="chat">
236                <short-description>Chatroom list maintenance</short-description>
237                <syntax>chat &lt;action&gt; [&lt;arguments&gt;]</syntax>
238
239                <description>
240
241                        <para>
242                                Available actions: add, with. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
243                        </para>
244
245                </description>
246
247                <bitlbee-command name="add">
248                        <syntax>chat add &lt;account id&gt; &lt;room&gt; [&lt;channel&gt;]</syntax>
249
250                        <description>
251                                <para>
252                                        Add a chatroom to the list of chatrooms you're interested in. BitlBee needs this list to map room names to a proper IRC channel name.
253                                </para>
254
255                                <para>
256                                        After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. (See <emphasis>chat set</emphasis>)
257                                </para>
258
259                                <para>
260                                        Password-protected rooms work exactly like on IRC, by passing the password as an extra argument to /join.
261                                </para>
262                        </description>
263
264                </bitlbee-command>
265
266                <bitlbee-command name="with">
267                        <syntax>chat with &lt;nickname&gt;</syntax>
268
269                        <description>
270                                <para>
271                                        While most <emphasis>chat</emphasis> subcommands are about named chatrooms, this command can be used to open an unnamed groupchat with one or more persons. This command is what <emphasis>/join #nickname</emphasis> used to do in older BitlBee versions.
272                                </para>
273                        </description>
274                </bitlbee-command>
275        </bitlbee-command>
276
277        <bitlbee-command name="add">
278                <short-description>Add a buddy to your contact list</short-description>
279                <syntax>add &lt;account id&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
280                <syntax>add -tmp &lt;account id&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
281
282                <description>
283                        <para>
284                                Adds the given buddy at the specified connection to your buddy list. The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
285                        </para>
286
287                        <para>
288                                If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications.
289                        </para>
290
291                        <para>
292                                If you use this command in a control channel containing people from only one group, the new contact will be added to that group automatically.
293                        </para>
294                </description>
295
296                <ircexample>
297                        <ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
298                        <ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&amp;bitlbee</emphasis></ircaction>
299                </ircexample>
300        </bitlbee-command>
301
302        <bitlbee-command name="info">
303                <short-description>Request user information</short-description>
304                <syntax>info &lt;connection&gt; &lt;handle&gt;</syntax>
305                <syntax>info &lt;nick&gt;</syntax>
306
307                <description>
308                        <para>
309                                Requests IM-network-specific information about the specified user. The amount of information you'll get differs per protocol. For some protocols (ATM Yahoo! and MSN) it'll give you an URL which you can visit with a normal web browser to get the information.
310                        </para>
311                </description>
312
313                <ircexample>
314                        <ircline nick="ctrlsoft">info 0 72696705</ircline>
315                        <ircline nick="root">User info - UIN: 72696705   Nick: Lintux   First/Last name: Wilmer van der Gaast   E-mail: lintux@lintux.cx</ircline>
316                </ircexample>
317
318        </bitlbee-command>
319
320        <bitlbee-command name="remove">
321                <short-description>Remove a buddy from your contact list</short-description>
322                <syntax>remove &lt;nick&gt;</syntax>
323
324                <description>
325                        <para>
326                                Removes the specified nick from your buddy list.
327                        </para>
328                </description>
329
330                <ircexample>
331                        <ircline nick="ctrlsoft">remove gryp</ircline>
332                        <ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
333                </ircexample>
334
335        </bitlbee-command>
336
337        <bitlbee-command name="block">
338                <short-description>Block someone</short-description>
339                <syntax>block &lt;nick&gt;</syntax>
340                <syntax>block &lt;connection&gt; &lt;handle&gt;</syntax>
341                <syntax>block &lt;connection&gt;</syntax>
342
343                <description>
344                        <para>
345                                Puts the specified user on your ignore list. Either specify the user's nick when you have him/her in your contact list or a connection number and a user handle.
346                        </para>
347                       
348                        <para>
349                                When called with only a connection specification as an argument, the command displays the current block list for that connection.
350                        </para>
351                </description>
352        </bitlbee-command>
353
354        <bitlbee-command name="allow">
355                <short-description>Unblock someone</short-description>
356                <syntax>allow &lt;nick&gt;</syntax>
357                <syntax>allow &lt;connection&gt; &lt;handle&gt;</syntax>
358
359                <description>
360                        <para>
361                                Reverse of block. Unignores the specified user or user handle on specified connection.
362                        </para>
363                       
364                        <para>
365                                When called with only a connection specification as an argument, the command displays the current allow list for that connection.
366                        </para>
367                </description>
368        </bitlbee-command>
369       
370        <bitlbee-command name="otr">
371                <short-description>Off-the-Record encryption control</short-description>
372                <syntax>otr &lt;subcommand&gt; [&lt;arguments&gt;]</syntax>
373
374                <description>
375
376                        <para>
377                                Available subcommands: connect, disconnect, smp, smpq, trust, info, keygen, and forget. See <emphasis>help otr &lt;subcommand&gt;</emphasis> for more information.
378                        </para>
379
380                </description>
381               
382                <bitlbee-command name="connect">
383                        <syntax>otr connect &lt;nick&gt;</syntax>
384                       
385                        <description>
386                       
387                                <para>
388                                        Attempts to establish an encrypted connection with the specified user by sending a magic string.
389                                </para>
390                               
391                        </description>
392               
393                </bitlbee-command>
394               
395                <bitlbee-command name="disconnect">
396                        <syntax>otr disconnect &lt;nick&gt;</syntax>
397                       
398                        <description>
399                       
400                                <para>
401                                        Resets the connection with the specified user to cleartext.
402                                </para>
403                               
404                        </description>
405               
406                </bitlbee-command>
407               
408                <bitlbee-command name="smp">
409                        <syntax>otr smp &lt;nick&gt; &lt;secret&gt;</syntax>
410                       
411                        <description>
412                       
413                                <para>
414                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol.
415                                </para>
416                               
417                                <para>
418                                        If an SMP challenge has been received from the given user, responds with the specified secret/answer. Otherwise, sends a challenge for the given secret.
419                                </para>
420                               
421                                <para>
422                                        Note that there are two flavors of SMP challenges: "shared-secret" and "question &amp; answer". This command is used to respond to both of them, or to initiate a shared-secret style exchange. Use the <emphasis>otr smpq</emphasis> command to initiate a "Q&amp;A" session.
423                                </para>
424                               
425                                <para>
426                                        When responding to a "Q&amp;A" challenge, the local trust value is not altered. Only the <emphasis>asking party</emphasis> sets trust in the case of success. Use <emphasis>otr smpq</emphasis> to pose your challenge. In a shared-secret exchange, both parties set their trust according to the outcome.
427                                </para>
428                               
429                        </description>
430               
431                </bitlbee-command>
432               
433                <bitlbee-command name="smpq">
434                        <syntax>otr smpq &lt;nick&gt; &lt;question&gt; &lt;answer&gt;</syntax>
435                       
436                        <description>
437                       
438                                <para>
439                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol, Q&amp;A style.
440                                </para>
441
442                                <para>
443                                        Initiates an SMP session in "question &amp; answer" style. The question is transmitted with the initial SMP packet and used to prompt the other party. You must be confident that only they know the answer. If the protocol succeeds (i.e. they answer correctly), the fingerprint will be trusted. Note that the answer must be entered exactly, case and punctuation count!
444                                </para>
445                               
446                                <para>
447                                        Note that this style of SMP only affects the trust setting on your side. Expect your opponent to send you their own challenge. Alternatively, if you and the other party have a shared secret, use the <emphasis>otr smp</emphasis> command.
448                                </para>
449                               
450                        </description>
451               
452                </bitlbee-command>
453               
454                <bitlbee-command name="trust">
455                        <syntax>otr trust &lt;nick&gt; &lt;fp1&gt; &lt;fp2&gt; &lt;fp3&gt; &lt;fp4&gt; &lt;fp5&gt;</syntax>
456                       
457                        <description>
458                       
459                                <para>
460                                        Manually affirms trust in the specified fingerprint, given as five blocks of precisely eight (hexadecimal) digits each.
461                                </para>
462                               
463                        </description>
464               
465                </bitlbee-command>
466               
467                <bitlbee-command name="info">
468                        <syntax>otr info</syntax>
469                        <syntax>otr info &lt;nick&gt;</syntax>
470                       
471                        <description>
472                       
473                                <para>
474                                        Shows information about the OTR state. The first form lists our private keys and current OTR contexts. The second form displays information about the connection with a given user, including the list of their known fingerprints.
475                                </para>
476                               
477                        </description>
478               
479                </bitlbee-command>
480               
481                <bitlbee-command name="keygen">
482                        <syntax>otr keygen &lt;account-no&gt;</syntax>
483                       
484                        <description>
485                       
486                                <para>
487                                        Generates a new OTR private key for the given account.
488                                </para>
489                               
490                        </description>
491               
492                </bitlbee-command>
493               
494                <bitlbee-command name="forget">
495                        <syntax>otr forget &lt;thing&gt; &lt;arguments&gt;</syntax>
496                       
497                        <description>
498                       
499                                <para>
500                                        Forgets some part of our OTR userstate. Available things: fingerprint, context, and key. See <emphasis>help otr forget &lt;thing&gt;</emphasis> for more information.
501                                </para>
502                       
503                        </description>
504                       
505                        <bitlbee-command name="fingerprint">
506                                <syntax>otr forget fingerprint &lt;nick&gt; &lt;fingerprint&gt;</syntax>
507                               
508                                <description>
509                               
510                                        <para>
511                                                Drops the specified fingerprint from the given user's OTR connection context. It is allowed to specify only a (unique) prefix of the desired fingerprint.
512                                        </para>
513                                       
514                                </description>
515                               
516                        </bitlbee-command>
517                               
518                        <bitlbee-command name="context">
519                                <syntax>otr forget context &lt;nick&gt;</syntax>
520                               
521                                <description>
522                               
523                                        <para>
524                                                Forgets the entire OTR context associated with the given user. This includes current message and protocol states, as well as any fingerprints for that user.
525                                        </para>
526                                       
527                                </description>
528                               
529                        </bitlbee-command>
530
531                        <bitlbee-command name="key">
532                                <syntax>otr forget key &lt;fingerprint&gt;</syntax>
533                               
534                                <description>
535                               
536                                        <para>
537                                                Forgets an OTR private key matching the specified fingerprint. It is allowed to specify only a (unique) prefix of the fingerprint.
538                                        </para>
539                                       
540                                </description>
541                               
542                        </bitlbee-command>
543               
544                </bitlbee-command>
545               
546        </bitlbee-command>
547
548        <bitlbee-command name="set">
549                <short-description>Miscellaneous settings</short-description>
550                <syntax>set</syntax>
551                <syntax>set &lt;variable&gt;</syntax>
552                <syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
553                <syntax>set -del &lt;variable&gt;</syntax>
554
555                <description>
556
557                        <para>
558                                Without any arguments, this command lists all the set variables. You can also specify a single argument, a variable name, to get that variable's value. To change this value, specify the new value as the second argument. With <emphasis>-del</emphasis> you can reset a setting to its default value.
559                        </para>
560
561                        <para>
562                                To get more help information about a setting, try:
563                        </para>
564
565                </description>
566
567                <ircexample>
568                        <ircline nick="ctrlsoft">help set private</ircline>
569                </ircexample>
570
571        </bitlbee-command>
572
573        <bitlbee-command name="help">
574                <short-description>BitlBee help system</short-description>
575
576                <syntax>help [subject]</syntax>
577
578                <description>
579                        <para>
580                                This command gives you the help information you're reading right now. If you don't give any arguments, it'll give a short help index.
581                        </para>
582                </description>
583        </bitlbee-command>
584
585        <bitlbee-command name="save">
586                <short-description>Save your account data</short-description>
587                <syntax>save</syntax>
588
589                <description>
590                        <para>
591                                This command saves all your nicks and accounts immediately. Handy if you have the autosave functionality disabled, or if you don't trust the program's stability... ;-)
592                        </para>
593                </description>
594        </bitlbee-command>
595
596        <bitlbee-setting name="account" type="string" scope="channel">
597
598                <description>
599                        <para>
600                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>account</emphasis>: Set this setting to the account id (numeric, or part of the username) of the account containing the contacts you want to see in this channel.
601                        </para>
602                </description>
603        </bitlbee-setting>
604
605        <bitlbee-setting name="allow_takeover" type="boolean" scope="global">
606                <default>true</default>
607
608                <description>
609                        <para>
610                                When you're already connected to a BitlBee server and you connect (and identify) again, BitlBee will offer to migrate your existing session to the new connection. If for whatever reason you don't want this, you can disable this setting.
611                        </para>
612                </description>
613        </bitlbee-setting>
614
615        <bitlbee-setting name="auto_connect" type="boolean" scope="both">
616                <default>true</default>
617
618                <description>
619                        <para>
620                                With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
621                        </para>
622                       
623                        <para>
624                                This setting can also be changed for specific accounts using the <emphasis>account set</emphasis> command. (However, these values will be ignored if the global <emphasis>auto_connect</emphasis> setting is disabled!)
625                        </para>
626                </description>
627        </bitlbee-setting>
628
629        <bitlbee-setting name="auto_join" type="boolean" scope="channel">
630                <default>false</default>
631
632                <description>
633                        <para>
634                                With this option enabled, BitlBee will automatically join this channel when you log in.
635                        </para>
636                </description>
637        </bitlbee-setting>
638
639        <bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
640                <default>true</default>
641
642                <description>
643                        <para>
644                                If an IM-connections breaks, you're supposed to bring it back up yourself. Having BitlBee do this automatically might not always be a good idea, for several reasons. If you want the connections to be restored automatically, you can enable this setting.
645                        </para>
646
647                        <para>
648                                See also the <emphasis>auto_reconnect_delay</emphasis> setting.
649                        </para>
650
651                        <para>
652                                This setting can also be changed for specific accounts using the <emphasis>account set</emphasis> command. (However, these values will be ignored if the global <emphasis>auto_reconnect</emphasis> setting is disabled!)
653                        </para>
654                </description>
655        </bitlbee-setting>
656
657        <bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
658                <default>5*3&lt;900</default>
659
660                <description>
661                        <para>
662                                Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
663                        </para>
664
665                        <para>
666                                This can be one integer, for a constant delay. One can also set it to something like &quot;10*10&quot;, which means wait for ten seconds on the first reconnect, multiply it by ten on every failure. Once successfully connected, this delay is re-set to the initial value. With &lt; you can give a maximum delay.
667                        </para>
668
669                        <para>
670                                See also the <emphasis>auto_reconnect</emphasis> setting.
671                        </para>
672                </description>
673        </bitlbee-setting>
674
675        <bitlbee-setting name="auto_reply_timeout" type="integer" scope="account">
676                <default>10800</default>
677
678                <description>
679                        <para>
680                                For Twitter accounts: If you respond to Tweets IRC-style (like "nickname: reply"), this will automatically be converted to the usual Twitter format ("@screenname reply").
681                        </para>
682
683                        <para>
684                                By default, BitlBee will then also add a reference to that person's most recent Tweet, unless that message is older than the value of this setting in seconds.
685                        </para>
686
687                        <para>
688                                If you want to disable this feature, just set this to 0. Alternatively, if you want to write a message once that is <emphasis>not</emphasis> a reply, use the Twitter reply syntax (@screenname).
689                        </para>
690                </description>
691        </bitlbee-setting>
692
693        <bitlbee-setting name="away" type="string" scope="both">
694                <description>
695                        <para>
696                                To mark yourself as away, it is recommended to just use <emphasis>/away</emphasis>, like on normal IRC networks. If you want to mark yourself as away on only one IM network, you can use this per-account setting.
697                        </para>
698
699                        <para>
700                                You can set it to any value and BitlBee will try to map it to the most appropriate away state for every open IM connection, or set it as a free-form away message where possible.
701                        </para>
702
703                        <para>
704                                Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.
705                        </para>
706                </description>
707        </bitlbee-setting>
708
709        <bitlbee-setting name="away_devoice" type="boolean" scope="global">
710                <default>true</default>
711
712                <description>
713                        <para>
714                                With this option enabled, the root user devoices people when they go away (just away, not offline) and gives the voice back when they come back. You might dislike the voice-floods you'll get if your contact list is huge, so this option can be disabled.
715                        </para>
716                       
717                        <para>
718                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
719                        </para>
720                </description>
721        </bitlbee-setting>
722
723        <bitlbee-setting name="away_reply_timeout" type="integer" scope="global">
724                <default>3600</default>
725
726                <description>
727                        <para>
728                                Most IRC servers send a user's away message every time s/he gets a private message, to inform the sender that they may not get a response immediately. With this setting set to 0, BitlBee will also behave like this.
729                        </para>
730
731                        <para>
732                                Since not all IRC clients do an excellent job at suppressing these messages, this setting lets BitlBee do it instead. BitlBee will wait this many seconds (or until the away state/message changes) before re-informing you that the person's away.
733                        </para>
734                </description>
735        </bitlbee-setting>
736
737        <bitlbee-setting name="base_url" type="string" scope="account">
738                <default>http://twitter.com</default>
739
740                <description>
741                        <para>
742                                There are more services that understand the Twitter API than just Twitter.com. BitlBee can connect to all Twitter API implementations.
743                        </para>
744
745                        <para>
746                                For example, set this setting to <emphasis>http://identi.ca/api</emphasis> to use Identi.ca.
747                        </para>
748
749                        <para>
750                                Keep two things in mind: When not using Twitter, you <emphasis>must</emphasis> also disable the <emphasis>oauth</emphasis> setting as it currently only works with Twitter. If you're still having issues, make sure there is <emphasis>no</emphasis> slash at the end of the URL you enter here.
751                        </para>
752                </description>
753        </bitlbee-setting>
754
755        <bitlbee-setting name="charset" type="string" scope="global">
756                <default>utf-8</default>
757                <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
758
759                <description>
760                        <para>
761                                This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly.
762                        </para>
763
764                        <para>
765                                Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html
766                        </para>
767                </description>
768
769        </bitlbee-setting>
770
771        <bitlbee-setting name="color_encrypted" type="boolean" scope="global">
772                <default>true</default>
773
774                <description>
775                        <para>
776                                If set to true, BitlBee will color incoming encrypted messages according to their fingerprint trust level: untrusted=red, trusted=green.
777                        </para>
778                </description>
779        </bitlbee-setting>
780
781        <bitlbee-setting name="control_channel" type="string" scope="global">
782                <default>&amp;bitlbee</default>
783
784                <description>
785                        <para>
786                                Normally the control channel where you can see all your contacts is called "&amp;bitlbee". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
787                        </para>
788                </description>
789        </bitlbee-setting>
790
791        <bitlbee-setting name="chat_type" type="string" scope="channel">
792                <default>groupchat</default>
793                <possible-values>groupchat, room</possible-values>
794
795                <description>
796                        <para>
797                                There are two kinds of chat channels: simple groupchats (basically normal IM chats with more than two participants) and names chatrooms, more similar to IRC channels.
798                        </para>
799                       
800                        <para>
801                                BitlBee supports both types. With this setting set to <emphasis>groupchat</emphasis> (the default), you can just invite people into the room and start talking.
802                        </para>
803                       
804                        <para>
805                                For setting up named chatrooms, it's currently easier to just use the <emphasis>chat add</emphasis> command.
806                        </para>
807                </description>
808        </bitlbee-setting>
809
810        <bitlbee-setting name="commands" type="boolean" scope="account">
811                <default>true</default>
812
813                <description>
814                        <para>
815                                With this setting enabled, you can use some commands in your Twitter channel/query. The commands are simple and not documented in too much detail:
816                        </para>
817
818                        <variablelist>
819                                <varlistentry><term>undo [&lt;id&gt;]</term><listitem><para>Delete your last Tweet (or one with the given ID)</para></listitem></varlistentry>
820                                <varlistentry><term>rt &lt;screenname|id&gt;</term><listitem><para>Retweet someone's last Tweet (or one with the given ID)</para></listitem></varlistentry>
821                                <varlistentry><term>follow &lt;screenname&gt;</term><listitem><para>Start following a person</para></listitem></varlistentry>
822                                <varlistentry><term>unfollow &lt;screenname&gt;</term><listitem><para>Stop following a person</para></listitem></varlistentry>
823                                <varlistentry><term>post &lt;message&gt;</term><listitem><para>Post a tweet</para></listitem></varlistentry>
824                        </variablelist>
825
826                        <para>
827                                Anything that doesn't look like a command will be treated as a tweet. Watch out for typos! :-)
828                        </para>
829                </description>
830        </bitlbee-setting>
831
832        <bitlbee-setting name="debug" type="boolean" scope="global">
833                <default>false</default>
834
835                <description>
836                        <para>
837                                Some debugging messages can be sent to the control channel if you wish. They're probably not really useful for you, unless you're doing some development on BitlBee.
838                        </para>
839                </description>
840        </bitlbee-setting>
841
842        <bitlbee-setting name="default_target" type="string" scope="global">
843                <default>root</default>
844                <possible-values>root, last</possible-values>
845
846                <description>
847                        <para>
848                                With this value set to <emphasis>root</emphasis>, lines written in the control channel without any nickname in front of them will be interpreted as commands. If you want BitlBee to send those lines to the last person you addressed in the control channel, set this to <emphasis>last</emphasis>.
849                        </para>
850                </description>
851        </bitlbee-setting>
852
853        <bitlbee-setting name="display_name" type="string" scope="account">
854                <description>
855                        <para>
856                                Currently only available for MSN connections. This setting allows you to read and change your "friendly name" for this connection. Since this is a server-side setting, it can't be changed when the account is off-line.
857                        </para>
858                </description>
859        </bitlbee-setting>
860
861        <bitlbee-setting name="display_namechanges" type="boolean" scope="global">
862                <default>false</default>
863
864                <description>
865                        <para>
866                                With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
867                        </para>
868                </description>
869        </bitlbee-setting>
870
871        <bitlbee-setting name="display_timestamps" type="boolean" scope="global">
872                <default>true</default>
873
874                <description>
875                        <para>
876                                When incoming messages are old (i.e. offline messages and channel backlogs), BitlBee will prepend them with a timestamp. If you find them ugly or useless, you can use this setting to hide them.
877                        </para>
878                </description>
879        </bitlbee-setting>
880
881        <bitlbee-setting name="fill_by" type="string" scope="channel">
882                <default>all</default>
883                <possible-values>all, group, account, protocol</possible-values>
884
885                <description>
886                        <para>
887                                For control channels only: This setting determines which contacts the channel gets populated with.
888                        </para>
889
890                        <para>
891                                By default, control channels will contain all your contacts. You instead select contacts by buddy group, IM account or IM protocol.
892                        </para>
893                       
894                        <para>
895                                Change this setting and the corresponding <emphasis>account</emphasis>/<emphasis>group</emphasis>/<emphasis>protocol</emphasis> setting to set up this selection.
896                        </para>
897                       
898                        <para>
899                                Note that, when creating a new channel, BitlBee will try to preconfigure the channel for you, based on the channel name. See <emphasis>help channels</emphasis>.
900                        </para>
901                </description>
902        </bitlbee-setting>
903
904        <bitlbee-setting name="group" type="string" scope="channel">
905
906                <description>
907                        <para>
908                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>group</emphasis>: Set this setting to the name of the group containing the contacts you want to see in this channel.
909                        </para>
910                </description>
911        </bitlbee-setting>
912
913        <bitlbee-setting name="handle_unknown" type="string" scope="global">
914                <default>add_channel</default>
915                <possible-values>root, add, add_private, add_channel, ignore</possible-values>
916
917                <description>
918                        <para>
919                                Messages from unknown users are echoed like this by default:
920                        </para>
921
922                        <ircexample>
923                                <ircline nick="root">Unknown message from handle 3137137:</ircline>
924                                <ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
925                        </ircexample>
926
927                        <para>
928                                If you want this lame user to be added automatically, you can set this setting to "add". If you prefer to ignore messages from people you don't know, you can set this one to "ignore". "add_private" and "add_channel" are like add, but you can use them to make messages from unknown buddies appear in the channel instead of a query window.
929                        </para>
930
931                        <note>
932                                <para>
933                                        Auto-added users aren't added to your real contact list. This is because you don't want the user to get authorization requests. So when you restart BitlBee, the auto-added user will be gone. If you want to keep the person in your buddy-list, you have to fixate the add using the <emphasis>add</emphasis> command.
934                                </para>
935                        </note>
936                </description>
937
938        </bitlbee-setting>
939
940        <bitlbee-setting name="ignore_auth_requests" type="boolean" scope="account">
941                <default>false</default>
942
943                <description>
944                        <para>
945                                Only supported by OSCAR so far, you can use this setting to ignore ICQ authorization requests, which are hardly used for legitimate (i.e. non-spam) reasons anymore.
946                        </para>
947                </description>
948
949        </bitlbee-setting>
950
951        <bitlbee-setting name="lcnicks" type="boolean" scope="global">
952                <default>true</default>
953
954                <description>
955                        <para>
956                                Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
957                        </para>
958                </description>
959
960        </bitlbee-setting>
961
962        <bitlbee-setting name="local_display_name" type="boolean" scope="account">
963                <default>false</default>
964
965                <description>
966                        <para>
967                                Mostly meant to work around a bug in MSN servers (forgetting the display name set by the user), this setting tells BitlBee to store your display name locally and set this name on the MSN servers when connecting.
968                        </para>
969                </description>
970
971        </bitlbee-setting>
972
973        <bitlbee-setting name="mail_notifications" type="boolean" scope="account">
974                <default>false</default>
975
976                <description>
977                        <para>
978                                Some protocols (MSN, Yahoo!) can notify via IM about new e-mail. Since most people use their Hotmail/Yahoo! addresses as a spam-box, this is disabled default. If you want these notifications, you can enable this setting.
979                        </para>
980                </description>
981
982        </bitlbee-setting>
983
984        <bitlbee-setting name="message_length" type="integer" scope="account">
985                <default>140</default>
986
987                <description>
988                        <para>
989                                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.
990                        </para>
991
992                        <para>
993                                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.
994                        </para>
995                </description>
996
997        </bitlbee-setting>
998
999        <bitlbee-setting name="mode" type="string" scope="account">
1000                <possible-values>one, many, chat</possible-values>
1001                <default>chat</default>
1002
1003                <description>
1004                        <para>
1005                                By default, BitlBee will create a separate channel (called #twitter_yourusername) for all your Twitter contacts/messages.
1006                        </para>
1007
1008                        <para>
1009                                If you don't want an extra channel, you can set this setting to "one" (everything will come from one nick, twitter_yourusername), or to "many" (individual nicks for everyone).
1010                        </para>
1011                       
1012                        <para>
1013                                With modes "chat" and "many", you can send direct messages by /msg'ing your contacts directly. Note, however, that incoming DMs are not fetched yet.
1014                        </para>
1015                       
1016                        <para>
1017                                With modes "many" and "one", you can post tweets by /msg'ing the twitter_yourusername contact. In mode "chat", messages posted in the Twitter channel will also be posted as tweets.
1018                        </para>
1019                </description>
1020
1021        </bitlbee-setting>
1022
1023        <bitlbee-setting name="mobile_is_away" type="boolean" scope="global">
1024                <default>false</default>
1025
1026                <description>
1027                        <para>
1028                                Most IM networks have a mobile version of their client. People who use these may not be paying that much attention to messages coming in. By enabling this setting, people using mobile clients will always be shown as away.
1029                        </para>
1030                </description>
1031
1032        </bitlbee-setting>
1033
1034        <bitlbee-setting name="nick" type="string" scope="chat">
1035                <description>
1036                        <para>
1037                                You can use this option to set your nickname in a chatroom. You won't see this nickname yourself, but other people in the room will. By default, BitlBee will use your username as the chatroom nickname.
1038                        </para>
1039                </description>
1040        </bitlbee-setting>
1041
1042        <bitlbee-setting name="nick_format" type="string" scope="both">
1043                <default>%-@nick</default>
1044
1045                <description>
1046                        <para>
1047                                By default, BitlBee tries to derive sensible nicknames for all your contacts from their IM handles. In some cases, IM modules (ICQ for example) will provide a nickname suggestion, which will then be used instead. This setting lets you change this behaviour.
1048                        </para>
1049
1050                        <para>
1051                                Whenever this setting is set for an account, it will be used for all its contacts. If it's not set, the global value will be used.
1052                        </para>
1053
1054                        <para>
1055                                It's easier to describe this setting using a few examples:
1056                        </para>
1057
1058                        <para>
1059                                FB-%full_name will make all nicknames start with "FB-", followed by the person's full name. For example you can set this format for your Facebook account so all Facebook contacts are clearly marked.
1060                        </para>
1061
1062                        <para>
1063                                [%group]%-@nick will make all nicknames start with the group the contact is in between square brackets, followed by the nickname suggestions from the IM module if available, or otherwise the handle. Because of the "-@" part, everything from the first @ will be stripped.
1064                        </para>
1065
1066                        <para>
1067                                See <emphasis>help nick_format</emphasis> for more information.
1068                        </para>
1069                </description>
1070        </bitlbee-setting>
1071
1072        <bitlbee-setting name="nick_source" type="string" scope="account">
1073                <default>handle</default>
1074                <possible-values>handle, full_name, first_name</possible-values>
1075
1076                <description>
1077                        <para>
1078                                By default, BitlBee generates a nickname for every contact by taking its handle and chopping off everything after the @. In some cases, this gives very inconvenient nicknames. The Facebook XMPP server is a good example, as all Facebook XMPP handles are numeric.
1079                        </para>
1080
1081                        <para>
1082                                With this setting set to <emphasis>full_name</emphasis>, the person's full name is used to generate a nickname. Or if you don't like long nicknames, set this setting to <emphasis>first_name</emphasis> instead and only the first word will be used. Note that the full name can be full of non-ASCII characters which will be stripped off.
1083                        </para>
1084                </description>
1085        </bitlbee-setting>
1086
1087        <bitlbee-setting name="oauth" type="boolean" scope="account">
1088                <default>true</default>
1089
1090                <description>
1091                        <para>
1092                                This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.
1093                        </para>
1094
1095                        <para>
1096                                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.
1097                        </para>
1098
1099                        <para>
1100                                The resulting access token will be saved permanently, so you have to do this only once.
1101                        </para>
1102                </description>
1103
1104        </bitlbee-setting>
1105
1106        <bitlbee-setting name="ops" type="string" scope="global">
1107                <default>both</default>
1108                <possible-values>both, root, user, none</possible-values>
1109
1110                <description>
1111                        <para>
1112                                Some people prefer themself and root to have operator status in &amp;bitlbee, other people don't. You can change these states using this setting.
1113                        </para>
1114
1115                        <para>
1116                                The value "both" means both user and root get ops. "root" means, well, just root. "user" means just the user. "none" means nobody will get operator status.
1117                        </para>
1118                </description>
1119        </bitlbee-setting>
1120
1121        <bitlbee-setting name="otr_policy" type="string" scope="global">
1122                <default>opportunistic</default>
1123                <possible-values>never, opportunistic, manual, always</possible-values>
1124
1125                <description>
1126                        <para>
1127                                This setting controls the policy for establishing Off-the-Record connections.
1128                        </para>
1129                        <para>
1130                                A value of "never" effectively disables the OTR subsystem. In "opportunistic" mode, a magic whitespace pattern will be appended to the first message sent to any user. If the peer is also running opportunistic OTR, an encrypted connection will be set up automatically. On "manual", on the other hand, OTR connections must be established explicitly using <emphasis>otr connect</emphasis>. Finally, the setting "always" enforces encrypted communication by causing BitlBee to refuse to send any cleartext messages at all.
1131                        </para>
1132                </description>
1133        </bitlbee-setting>
1134
1135        <bitlbee-setting name="password" type="string" scope="both">
1136                <description>
1137                        <para>
1138                                Use this global setting to change your "NickServ" password.
1139                        </para>
1140                       
1141                        <para>
1142                                This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
1143                        </para>
1144                       
1145                        <para>
1146                                Note that BitlBee will always say this setting is empty. This doesn't mean there is no password, it just means that, for security reasons, BitlBee stores passwords somewhere else so they can't just be retrieved in plain text.
1147                        </para>
1148                </description>
1149        </bitlbee-setting>
1150
1151        <bitlbee-setting name="paste_buffer" type="boolean" scope="global">
1152                <default>false</default>
1153
1154                <description>
1155                        <para>
1156                                By default, when you send a message to someone, BitlBee forwards this message to the user immediately. When you paste a large number of lines, the lines will be sent in separate messages, which might not be very nice to read. If you enable this setting, BitlBee will buffer your messages and wait for more data.
1157                        </para>
1158
1159                        <para>
1160                                Using the <emphasis>paste_buffer_delay</emphasis> setting you can specify the number of seconds BitlBee should wait for more data before the complete message is sent.
1161                        </para>
1162
1163                        <para>
1164                                Please note that if you remove a buddy from your list (or if the connection to that user drops) and there's still data in the buffer, this data will be lost. BitlBee will not try to send the message to the user in those cases.
1165                        </para>
1166                </description>
1167        </bitlbee-setting>
1168
1169        <bitlbee-setting name="paste_buffer_delay" type="integer" scope="global">
1170                <default>200</default>
1171
1172                <description>
1173
1174                        <para>
1175                                Tell BitlBee after how many (mili)seconds a buffered message should be sent. Values greater than 5 will be interpreted as miliseconds, 5 and lower as seconds.
1176                        </para>
1177
1178                        <para>
1179                                See also the <emphasis>paste_buffer</emphasis> setting.
1180                        </para>
1181                </description>
1182        </bitlbee-setting>
1183       
1184        <bitlbee-setting name="port" type="integer" scope="account">
1185                <description>
1186                        <para>
1187                                Currently only available for Jabber connections. Specifies the port number to connect to. Usually this should be set to 5222, or 5223 for SSL-connections.
1188                        </para>
1189                </description>
1190        </bitlbee-setting>
1191
1192        <bitlbee-setting name="priority" type="integer" scope="account">
1193                <default>0</default>
1194
1195                <description>
1196                        <para>
1197                                Can be set for Jabber connections. When connecting to one account from multiple places, this priority value will help the server to determine where to deliver incoming messages (that aren't addressed to a specific resource already).
1198                        </para>
1199
1200                        <para>
1201                                According to RFC 3921 servers will always deliver messages to the server with the highest priority value. Mmessages will not be delivered to resources with a negative priority setting (and should be saved as an off-line message if all available resources have a negative priority value).
1202                        </para>
1203                </description>
1204        </bitlbee-setting>
1205
1206        <bitlbee-setting name="private" type="boolean" scope="global">
1207                <default>true</default>
1208
1209                <description>
1210                        <para>
1211                                If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
1212                        </para>
1213
1214                        <para>
1215                                This setting is remembered (during one session) per-user, this setting only changes the default state. This option takes effect as soon as you reconnect.
1216                        </para>
1217                </description>
1218        </bitlbee-setting>
1219
1220        <bitlbee-setting name="protocol" type="string" scope="channel">
1221
1222                <description>
1223                        <para>
1224                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>protocol</emphasis>: Set this setting to the name of the IM protocol of all contacts you want to see in this channel.
1225                        </para>
1226                </description>
1227        </bitlbee-setting>
1228
1229        <bitlbee-setting name="query_order" type="string" scope="global">
1230                <default>lifo</default>
1231                <possible-values>lifo, fifo</possible-values>
1232
1233                <description>
1234                        <para>
1235                                This changes the order in which the questions from root (usually authorization requests from buddies) should be answered. When set to <emphasis>lifo</emphasis>, BitlBee immediately displays all new questions and they should be answered in reverse order. When this is set to <emphasis>fifo</emphasis>, BitlBee displays the first question which comes in and caches all the others until you answer the first one.
1236                        </para>
1237
1238                        <para>
1239                                Although the <emphasis>fifo</emphasis> setting might sound more logical (and used to be the default behaviour in older BitlBee versions), it turned out not to be very convenient for many users when they missed the first question (and never received the next ones).
1240                        </para>
1241                </description>
1242        </bitlbee-setting>
1243
1244        <bitlbee-setting name="resource" type="string" scope="account">
1245                <default>BitlBee</default>
1246
1247                <description>
1248                        <para>
1249                                Can be set for Jabber connections. You can use this to connect to your Jabber account from multiple clients at once, with every client using a different resource string.
1250                        </para>
1251                </description>
1252        </bitlbee-setting>
1253
1254        <bitlbee-setting name="resource_select" type="string" scope="account">
1255                <default>activity</default>
1256                <possible-values>priority, activity</possible-values>
1257
1258                <description>
1259                        <para>
1260                                Because the IRC interface makes it pretty hard to specify the resource to talk to (when a buddy is online through different resources), this setting was added.
1261                        </para>
1262
1263                        <para>
1264                                Normally it's set to <emphasis>priority</emphasis> which means messages will always be delivered to the buddy's resource with the highest priority. If the setting is set to <emphasis>activity</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
1265                        </para>
1266                </description>
1267        </bitlbee-setting>
1268
1269        <bitlbee-setting name="root_nick" type="string" scope="global">
1270                <default>root</default>
1271
1272                <description>
1273                        <para>
1274                                Normally the "bot" that takes all your BitlBee commands is called "root". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
1275                        </para>
1276                </description>
1277        </bitlbee-setting>
1278
1279        <bitlbee-setting name="save_on_quit" type="boolean" scope="global">
1280                <default>true</default>
1281
1282                <description>
1283                        <para>
1284                                If enabled causes BitlBee to save all current settings and account details when user disconnects. This is enabled by default, and these days there's not really a reason to have it disabled anymore.
1285                        </para>
1286                </description>
1287        </bitlbee-setting>
1288
1289        <bitlbee-setting name="server" type="string" scope="account">
1290                <description>
1291                        <para>
1292                                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.
1293                        </para>
1294                </description>
1295        </bitlbee-setting>
1296
1297        <bitlbee-setting name="show_offline" type="boolean" scope="global">
1298                <default>false</default>
1299
1300                <description>
1301                        <para>
1302                                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.
1303                        </para>
1304                       
1305                        <para>
1306                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
1307                        </para>
1308                </description>
1309        </bitlbee-setting>
1310
1311        <bitlbee-setting name="show_users" type="string" scope="channel">
1312                <default>online+,away</default>
1313
1314                <description>
1315                        <para>
1316                                Comma-separated list of statuses of users you want in the channel,
1317                                and any modes they should have. The following statuses are currently
1318                                recognised: <emphasis>online</emphasis> (i.e. available, not
1319                                away), <emphasis>away</emphasis>, and <emphasis>offline</emphasis>.
1320                        </para>
1321                       
1322                        <para>
1323                                If a status is followed by a valid channel mode character
1324                                (@, % or +), it will be given to users with that status.
1325                                For example, <emphasis>online@,away+,offline</emphasis> will
1326                                show all users in the channel. Online people will
1327                                have +o, people who are online but away will have +v,
1328                                and others will have no special modes.
1329                        </para>
1330                </description>
1331        </bitlbee-setting>
1332
1333        <bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
1334                <default>true</default>
1335
1336                <description>
1337                        <para>
1338                                Some IRC clients parse quit messages sent by the IRC server to see if someone really left or just disappeared because of a netsplit. By default, BitlBee tries to simulate netsplit-like quit messages to keep the control channel window clean. If you don't like this (or if your IRC client doesn't support this) you can disable this setting.
1339                        </para>
1340                </description>
1341        </bitlbee-setting>
1342
1343        <bitlbee-setting name="ssl" type="boolean" scope="account">
1344                <default>false</default>
1345
1346                <description>
1347                        <para>
1348                                Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
1349                        </para>
1350                </description>
1351        </bitlbee-setting>
1352
1353        <bitlbee-setting name="status" type="string" scope="both">
1354                <description>
1355                        <para>
1356                                Certain protocols (like Jabber/XMPP) support status messages, similar to away messages. They can be used to indicate things like your location or activity, without showing up as away/busy.
1357                        </para>
1358
1359                        <para>
1360                                This setting can be used to set such a message. It will be available as a per-account setting for protocols that support it, and also as a global setting (which will then automatically be used for all protocols that support it).
1361                        </para>
1362
1363                        <para>
1364                                Away states set using <emphasis>/away</emphasis> or the <emphasis>away</emphasis> setting will override this setting. To un-set the setting, use <emphasis>set -del status</emphasis>.
1365                        </para>
1366                </description>
1367        </bitlbee-setting>
1368
1369        <bitlbee-setting name="strip_html" type="boolean" scope="global">
1370                <default>true</default>
1371
1372                <description>
1373                        <para>
1374                                Determines what BitlBee should do with HTML in messages. Normally this is turned on and HTML will be stripped from messages, if BitlBee thinks there is HTML.
1375                        </para>
1376                        <para>
1377                                If BitlBee fails to detect this sometimes (most likely in AIM messages over an ICQ connection), you can set this setting to <emphasis>always</emphasis>, but this might sometimes accidentally strip non-HTML things too.
1378                        </para>
1379                </description>
1380        </bitlbee-setting>
1381
1382        <bitlbee-setting name="switchboard_keepalives" type="boolean" scope="account">
1383                <default>false</default>
1384
1385                <description>
1386                        <para>
1387                                Turn on this flag if you have difficulties talking to offline/invisible contacts.
1388                        </para>
1389                       
1390                        <para>
1391                                With this setting enabled, BitlBee will send keepalives to MSN switchboards with offline/invisible contacts every twenty seconds. This should keep the server and client on the other side from shutting it down.
1392                        </para>
1393                       
1394                        <para>
1395                                This is useful because BitlBee doesn't support MSN offline messages yet and the MSN servers won't let the user reopen switchboards to offline users. Once offline messaging is supported, this flag might be removed.
1396                        </para>
1397                </description>
1398        </bitlbee-setting>
1399
1400        <bitlbee-setting name="tag" type="string" scope="account">
1401                <description>
1402                        <para>
1403                                For every account you have, you can set a tag you can use to uniquely identify that account. This tag can be used instead of the account number (or protocol name, or part of the screenname) when using commands like <emphasis>account</emphasis>, <emphasis>add</emphasis>, etc. You can't have two accounts with one and the same account tag.
1404                        </para>
1405
1406                        <para>
1407                                By default, it will be set to the name of the IM protocol. Once you add a second account on an IM network, a numeric suffix will be added, starting with 2.
1408                        </para>
1409                </description>
1410        </bitlbee-setting>
1411
1412        <bitlbee-setting name="timezone" type="string" scope="global">
1413                <default>local</default>
1414                <possible-values>local, utc, gmt, timezone-spec</possible-values>
1415
1416                <description>
1417                        <para>
1418                                If message timestamps are available for offline messages or chatroom backlogs, BitlBee will display them as part of the message. By default it will use the local timezone. If you're not in the same timezone as the BitlBee server, you can adjust the timestamps using this setting.
1419                        </para>
1420
1421                        <para>
1422                                Values local/utc/gmt should be self-explanatory. timezone-spec is a time offset in hours:minutes, for example: -8 for Pacific Standard Time, +2 for Central European Summer Time, +5:30 for Indian Standard Time.
1423                        </para>
1424                </description>
1425        </bitlbee-setting>
1426
1427        <bitlbee-setting name="tls" type="boolean" scope="account">
1428                <default>try</default>
1429
1430                <description>
1431                        <para>
1432                                Newer Jabber servers allow clients to convert a plain-text session to a TLS/SSL-encrypted session. Normally (with this setting set to <emphasis>try</emphasis>) BitlBee will do this, if possible.
1433                        </para>
1434
1435                        <para>
1436                                If you want to force BitlBee to use TLS sessions only (and to give up if that doesn't seem to be possible) you can set this setting to <emphasis>true</emphasis>. Set it to <emphasis>false</emphasis> if you want the session to remain plain-text.
1437                        </para>
1438                </description>
1439        </bitlbee-setting>
1440
1441        <bitlbee-setting name="to_char" type="string" scope="global">
1442                <default>": "</default>
1443
1444                <description>
1445                        <para>
1446                                It's customary that messages meant for one specific person on an IRC channel are prepended by his/her alias followed by a colon ':'. BitlBee does this by default. If you prefer a different character, you can set it using <emphasis>set to_char</emphasis>.
1447                        </para>
1448
1449                        <para>
1450                                Please note that this setting is only used for incoming messages. For outgoing messages you can use ':' (colon) or ',' to separate the destination nick from the message, and this is not configurable.
1451                        </para>
1452                </description>
1453        </bitlbee-setting>
1454
1455        <bitlbee-setting name="translate_to_nicks" type="boolean" scope="channel">
1456                <default>true</default>
1457
1458                <description>
1459                        <para>
1460                                IRC's nickname namespace is quite limited compared to most IM protocols. Not any non-ASCII characters are allowed, in fact nicknames have to be mostly alpha-numeric. Also, BitlBee has to add underscores sometimes to avoid nickname collisions.
1461                        </para>
1462
1463                        <para>
1464                                While normally the BitlBee user is the only one seeing these names, they may be exposed to other chatroom participants for example when addressing someone in the channel (with or without tab completion). By default BitlBee will translate these stripped nicknames back to the original nick. If you don't want this, disable this setting.
1465                        </para>
1466                </description>
1467        </bitlbee-setting>
1468
1469        <bitlbee-setting name="type" type="string" scope="channel">
1470                <default>control</default>
1471                <possible-values>control, chat</possible-values>
1472
1473                <description>
1474                        <para>
1475                                BitlBee supports two kinds of channels: control channels (usually with a name starting with a &amp;) and chatroom channels (name usually starts with a #).
1476                        </para>
1477
1478                        <para>
1479                                See <emphasis>help channels</emphasis> for a full description of channel types in BitlBee.
1480                        </para>
1481                </description>
1482        </bitlbee-setting>
1483
1484        <bitlbee-setting name="typing_notice" type="boolean" scope="global">
1485                <default>false</default>
1486
1487                <description>
1488                        <para>
1489                                Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way.
1490                        </para>
1491                </description>
1492        </bitlbee-setting>
1493
1494        <bitlbee-setting name="user_agent" type="string" scope="account">
1495                <default>BitlBee</default>
1496
1497                <description>
1498                        <para>
1499                                Some Jabber servers are configured to only allow a few (or even just one) kinds of XMPP clients to connect to them.
1500                        </para>
1501                       
1502                        <para>
1503                                You can change this setting to make BitlBee present itself as a different client, so that you can still connect to these servers.
1504                        </para>
1505                </description>
1506        </bitlbee-setting>
1507
1508        <bitlbee-setting name="web_aware" type="string" scope="account">
1509                <default>false</default>
1510
1511                <description>
1512                        <para>
1513                                ICQ allows people to see if you're on-line via a CGI-script. (http://status.icq.com/online.gif?icq=UIN) This can be nice to put on your website, but it seems that spammers also use it to see if you're online without having to add you to their contact list. So to prevent ICQ spamming, recent versions of BitlBee disable this feature by default.
1514                        </para>
1515
1516                        <para>
1517                                Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
1518                        </para>
1519                </description>
1520        </bitlbee-setting>
1521
1522        <bitlbee-setting name="xmlconsole" type="boolean" scope="account">
1523                <default>false</default>
1524
1525                <description>
1526                        <para>
1527                                The Jabber module allows you to add a buddy <emphasis>xmlconsole</emphasis> to your contact list, which will then show you the raw XMPP stream between you and the server. You can also send XMPP packets to this buddy, which will then be sent to the server.
1528                        </para>
1529                        <para>
1530                                If you want to enable this XML console permanently (and at login time already), you can set this setting.
1531                        </para>
1532                </description>
1533        </bitlbee-setting>
1534
1535        <bitlbee-command name="rename">
1536                <short-description>Rename (renick) a buddy</short-description>
1537                <syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
1538
1539                <description>
1540                        <para>
1541                                Renick a user in your buddy list. Very useful, in fact just very important, if you got a lot of people with stupid account names (or hard ICQ numbers).
1542                        </para>
1543                </description>
1544
1545                <ircexample>
1546                        <ircline nick="itsme">rename itsme_ you</ircline>
1547                        <ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
1548                </ircexample>
1549
1550        </bitlbee-command>
1551
1552        <bitlbee-command name="yes">
1553                <short-description>Accept a request</short-description>
1554                <syntax>yes [&lt;number&gt;]</syntax>
1555
1556                <description>
1557                        <para>
1558                                Sometimes an IM-module might want to ask you a question. (Accept this user as your buddy or not?) To accept a question, use the <emphasis>yes</emphasis> command.
1559                        </para>
1560
1561                        <para>
1562                                By default, this answers the first unanswered question. You can also specify a different question as an argument. You can use the <emphasis>qlist</emphasis> command for a list of questions.
1563                        </para>
1564                </description>
1565
1566        </bitlbee-command>
1567
1568        <bitlbee-command name="no">
1569                <short-description>Deny a request</short-description>
1570                <syntax>no [&lt;number&gt;]</syntax>
1571
1572                <description>
1573                        <para>
1574                                Sometimes an IM-module might want to ask you a question. (Accept this user as your buddy or not?) To reject a question, use the <emphasis>no</emphasis> command.
1575                        </para>
1576
1577                        <para>
1578                                By default, this answers the first unanswered question. You can also specify a different question as an argument. You can use the <emphasis>qlist</emphasis> command for a list of questions.
1579                        </para>
1580                </description>
1581        </bitlbee-command>
1582
1583        <bitlbee-command name="qlist">
1584                <short-description>List all the unanswered questions root asked</short-description>
1585                <syntax>qlist</syntax>
1586
1587                <description>
1588                        <para>
1589                                This gives you a list of all the unanswered questions from root.
1590                        </para>
1591                </description>
1592
1593        </bitlbee-command>
1594
1595        <bitlbee-command name="register">
1596                <short-description>Register yourself</short-description>
1597                <syntax>register &lt;password&gt;</syntax>
1598
1599                <description>
1600                        <para>
1601                                BitlBee can save your settings so you won't have to enter all your IM passwords every time you log in. If you want the Bee to save your settings, use the <emphasis>register</emphasis> command.
1602                        </para>
1603
1604                        <para>
1605                                Please do pick a secure password, don't just use your nick as your password. Please note that IRC is not an encrypted protocol, so the passwords still go over the network in plaintext. Evil people with evil sniffers will read it all. (So don't use your root password.. ;-)
1606                        </para>
1607
1608                        <para>
1609                                To identify yourself in later sessions, you can use the <emphasis>identify</emphasis> command. To change your password later, you can use the <emphasis>set password</emphasis> command.
1610                        </para>
1611                </description>
1612
1613        </bitlbee-command>
1614
1615        <bitlbee-command name="identify">
1616                <syntax>identify [-noload|-force] &lt;password&gt;</syntax>
1617                <short-description>Identify yourself with your password</short-description>
1618
1619                <description>
1620                        <para>
1621                                BitlBee saves all your settings (contacts, accounts, passwords) on-server. To prevent other users from just logging in as you and getting this information, you'll have to identify yourself with your password. You can register this password using the <emphasis>register</emphasis> command.
1622                        </para>
1623
1624                        <para>
1625                                Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
1626                        </para>
1627
1628                        <para>
1629                                The <emphasis>-noload</emphasis> and <emphasis>-force</emphasis> flags can be used to identify when you're logged into some IM accounts already. <emphasis>-force</emphasis> will let you identify yourself and load all saved accounts (and keep the accounts you're logged into already).
1630                        </para>
1631                       
1632                        <para>
1633                                <emphasis>-noload</emphasis> will log you in but not load any accounts and settings saved under your current nickname. These will be overwritten once you save your settings (i.e. when you disconnect).
1634                        </para>
1635                </description>
1636        </bitlbee-command>
1637
1638        <bitlbee-command name="drop">
1639                <syntax>drop &lt;password&gt;</syntax>
1640                <short-description>Drop your account</short-description>
1641
1642                <description>
1643                        <para>
1644                                Drop your BitlBee registration. Your account files will be removed and your password will be forgotten. For obvious security reasons, you have to specify your NickServ password to make this command work.
1645                        </para>
1646                </description>
1647        </bitlbee-command>
1648
1649        <bitlbee-command name="blist">
1650                <syntax>blist [all|online|offline|away]</syntax>
1651                <short-description>List all the buddies in the current channel</short-description>
1652
1653                <description>
1654                        <para>
1655                                You can get a more readable buddy list using the <emphasis>blist</emphasis> command. If you want a complete list (including the offline users) you can use the <emphasis>all</emphasis> argument.
1656                        </para>
1657                </description>
1658
1659        </bitlbee-command>
1660
1661        <bitlbee-command name="group">
1662                <short-description>Contact group management</short-description>
1663                <syntax>group list</syntax>
1664
1665                <description>
1666                        <para>
1667                                Only the <emphasis>group list</emphasis> command is supported at the moment, which shows a list of all groups defined so far.
1668                        </para>
1669                       
1670                        <para>
1671                                If you want to move contacts between groups, you can use the IRC <emphasis>/invite</emphasis> command. Also, if you use the <emphasis>add</emphasis> command in a control channel configured to show just one group, the new contact will automatically be added to that group.
1672                        </para>
1673                </description>
1674        </bitlbee-command>
1675       
1676        <bitlbee-command name="transfer">
1677                <short-description>Monitor, cancel, or reject file transfers</short-description>
1678                <syntax>transfer [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
1679               
1680                <description>
1681                        <para>
1682                                Without parameters the currently pending file transfers and their status will be listed. Available actions are <emphasis>cancel</emphasis> and <emphasis>reject</emphasis>. See <emphasis>help transfer &lt;action&gt;</emphasis> for more information.
1683                        </para>
1684
1685                        <ircexample>
1686                                <ircline nick="ulim">transfer</ircline>
1687                        </ircexample>
1688                </description>
1689               
1690                <bitlbee-command name="cancel">
1691                        <short-description>Cancels the file transfer with the given id</short-description>
1692                        <syntax>transfer &lt;cancel&gt; id</syntax>
1693
1694                        <description>
1695                                <para>Cancels the file transfer with the given id</para>
1696                        </description>
1697
1698                        <ircexample>
1699                                <ircline nick="ulim">transfer cancel 1</ircline>
1700                                <ircline nick="root">Canceling file transfer for test</ircline>
1701                        </ircexample>
1702                </bitlbee-command>
1703
1704                <bitlbee-command name="reject">
1705                        <short-description>Rejects all incoming transfers</short-description>
1706                        <syntax>transfer &lt;reject&gt;</syntax>
1707
1708                        <description>
1709                                <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
1710                        </description>
1711
1712                        <ircexample>
1713                                <ircline nick="ulim">transfer reject</ircline>
1714                        </ircexample>
1715                </bitlbee-command>
1716        </bitlbee-command>
1717       
1718</chapter>
Note: See TracBrowser for help on using the repository browser.