source: doc/user-guide/commands.xml @ 12f041d

Last change on this file since 12f041d was aa3b61e, checked in by dequis <dx@…>, at 2015-08-28T02:05:45Z

user-guide: add help for the jabber 'proxy' setting
  • Property mode set to 100644
File size: 75.2 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
26                                <para>
27                                        You can omit the password and enter it separately using the IRC /OPER command. This lets you enter your password without your IRC client echoing it on screen or recording it in logs.
28                                </para>
29                        </description>
30                       
31                        <bitlbee-command name="jabber">
32                                <syntax>account add jabber &lt;handle@server.tld&gt; [&lt;password&gt;]</syntax>
33
34                                <description>
35                                        <para>
36                                                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.
37                                        </para>
38
39                                        <para>
40                                                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>).
41                                        </para>
42                                </description>
43                        </bitlbee-command>
44
45                        <bitlbee-command name="msn">
46                                <syntax>account add msn &lt;handle@server.tld&gt; [&lt;password&gt;]</syntax>
47
48                                <description>
49                                        <para>
50                                                For MSN connections there are no special arguments.
51                                        </para>
52                                </description>
53                        </bitlbee-command>
54                       
55                        <bitlbee-command name="oscar">
56                                <syntax>account add oscar &lt;handle&gt; [&lt;password&gt;]</syntax>
57
58                                <description>
59                                        <para>
60                                                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.
61                                        </para>
62                                </description>
63
64                                <ircexample>
65                                        <ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
66                                        <ircline nick="root">Account successfully added</ircline>
67                                </ircexample>
68                        </bitlbee-command>
69                       
70                        <bitlbee-command name="twitter">
71                                <syntax>account add twitter &lt;handle&gt;</syntax>
72
73                                <description>
74                                        <para>
75                                                This module gives you simple access to Twitter and Twitter API compatible services.
76                                        </para>
77                                       
78                                        <para>
79                                                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>).
80                                        </para>
81                                       
82                                        <para>
83                                                To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
84                                        </para>
85
86                                        <para>
87                                                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>.)
88                                        </para>
89                                       
90                                        <para>
91                                                To use a non-Twitter service, change the <emphasis>base_url</emphasis> setting. For identi.ca, you can simply use <emphasis>account add identica</emphasis>.
92                                        </para>
93                                </description>
94                        </bitlbee-command>
95                       
96                        <bitlbee-command name="identica">
97                                <syntax>account add identica &lt;handle&gt;</syntax>
98
99                                <description>
100                                        <para>
101                                                Same protocol as <emphasis>twitter</emphasis>, but defaults to a <emphasis>base_url</emphasis> pointing at identi.ca. It also works with OAuth (so don't specify your password).
102                                        </para>
103                                </description>
104                        </bitlbee-command>
105
106                        <bitlbee-command name="yahoo">
107                                <syntax>account add yahoo &lt;handle&gt; [&lt;password&gt;]</syntax>
108
109                                <description>
110                                        <para>
111                                                For Yahoo! connections there are no special arguments.
112                                        </para>
113                                </description>
114                        </bitlbee-command>
115
116                </bitlbee-command>
117
118                <bitlbee-command name="del">
119                        <syntax>account &lt;account id&gt; del</syntax>
120
121                        <description>
122                                <para>
123                                        This command deletes an account from your account list. You should signoff the account before deleting it.
124                                </para>
125
126
127                                <para>
128                                        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.
129                                </para>
130                        </description>
131                </bitlbee-command>
132
133                <bitlbee-command name="on">
134                        <syntax>account [&lt;account id&gt;] on</syntax>
135
136                        <description>
137                                <para>
138                                        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.
139                                </para>
140
141                                <para>
142                                        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.
143                                </para>
144                        </description>
145
146                </bitlbee-command>
147
148                <bitlbee-command name="off">
149                        <syntax>account [&lt;account id&gt;] off</syntax>
150
151                        <description>
152                                <para>
153                                        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.
154                                </para>
155
156                                <para>
157                                        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.
158                                </para>
159                        </description>
160                </bitlbee-command>
161
162                <bitlbee-command name="list">
163                        <syntax>account list</syntax>
164
165                        <description>
166                                <para>
167                                        This command gives you a list of all the accounts known by BitlBee.
168                                </para>
169                        </description>
170                </bitlbee-command>
171
172                <bitlbee-command name="set">
173                        <syntax>account &lt;account id&gt; set</syntax>
174                        <syntax>account &lt;account id&gt; set &lt;setting&gt;</syntax>
175                        <syntax>account &lt;account id&gt; set &lt;setting&gt; &lt;value&gt;</syntax>
176                        <syntax>account &lt;account id&gt; set -del &lt;setting&gt;</syntax>
177
178                        <description>
179                                <para>
180                                        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>.
181                                </para>
182                               
183                                <para>
184                                        For more information about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
185                                </para>
186                               
187                                <para>
188                                        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.
189                                </para>
190                        </description>
191                </bitlbee-command>
192        </bitlbee-command>
193
194        <bitlbee-command name="channel">
195                <short-description>Channel list maintenance</short-description>
196                <syntax>channel [&lt;account id&gt;] &lt;action&gt; [&lt;arguments&gt;]</syntax>
197
198                <description>
199                        <para>
200                                Available actions: del, list, set. See <emphasis>help channel &lt;action&gt;</emphasis> for more information.
201                        </para>
202                       
203                        <para>
204                                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>.
205                        </para>
206                </description>
207
208                <bitlbee-command name="del">
209                        <syntax>channel &lt;channel id&gt; del</syntax>
210
211                        <description>
212                                <para>
213                                        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.)
214                                </para>
215                        </description>
216
217                </bitlbee-command>
218
219                <bitlbee-command name="list">
220                        <syntax>channel list</syntax>
221
222                        <description>
223                                <para>
224                                        This command gives you a list of all the channels you configured.
225                                </para>
226                        </description>
227
228                </bitlbee-command>
229
230                <bitlbee-command name="set">
231                        <syntax>channel [&lt;channel id&gt;] set</syntax>
232                        <syntax>channel [&lt;channel id&gt;] set &lt;setting&gt;</syntax>
233                        <syntax>channel [&lt;channel id&gt;] set &lt;setting&gt; &lt;value&gt;</syntax>
234                        <syntax>channel [&lt;channel id&gt;] set -del &lt;setting&gt;</syntax>
235
236                        <description>
237                                <para>
238                                        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>.
239                                </para>
240                               
241                                <para>
242                                        For more information about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
243                                </para>
244                               
245                                <para>
246                                        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.
247                                </para>
248                        </description>
249                </bitlbee-command>
250
251        </bitlbee-command>
252
253        <bitlbee-command name="chat">
254                <short-description>Chatroom list maintenance</short-description>
255                <syntax>chat &lt;action&gt; [&lt;arguments&gt;]</syntax>
256
257                <description>
258
259                        <para>
260                                Available actions: add, with. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
261                        </para>
262
263                </description>
264
265                <bitlbee-command name="add">
266                        <syntax>chat add &lt;account id&gt; &lt;room&gt; [&lt;channel&gt;]</syntax>
267
268                        <description>
269                                <para>
270                                        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.
271                                </para>
272
273                                <para>
274                                        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>)
275                                </para>
276
277                                <para>
278                                        Password-protected rooms work exactly like on IRC, by passing the password as an extra argument to /join.
279                                </para>
280                        </description>
281
282                </bitlbee-command>
283
284                <bitlbee-command name="with">
285                        <syntax>chat with &lt;nickname&gt;</syntax>
286
287                        <description>
288                                <para>
289                                        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.
290                                </para>
291                        </description>
292                </bitlbee-command>
293        </bitlbee-command>
294
295        <bitlbee-command name="add">
296                <short-description>Add a buddy to your contact list</short-description>
297                <syntax>add &lt;account id&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
298                <syntax>add -tmp &lt;account id&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
299
300                <description>
301                        <para>
302                                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.
303                        </para>
304
305                        <para>
306                                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.
307                        </para>
308
309                        <para>
310                                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.
311                        </para>
312                </description>
313
314                <ircexample>
315                        <ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
316                        <ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&amp;bitlbee</emphasis></ircaction>
317                </ircexample>
318        </bitlbee-command>
319
320        <bitlbee-command name="info">
321                <short-description>Request user information</short-description>
322                <syntax>info &lt;connection&gt; &lt;handle&gt;</syntax>
323                <syntax>info &lt;nick&gt;</syntax>
324
325                <description>
326                        <para>
327                                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.
328                        </para>
329                </description>
330
331                <ircexample>
332                        <ircline nick="ctrlsoft">info 0 72696705</ircline>
333                        <ircline nick="root">User info - UIN: 72696705   Nick: Lintux   First/Last name: Wilmer van der Gaast   E-mail: lintux@lintux.cx</ircline>
334                </ircexample>
335
336        </bitlbee-command>
337
338        <bitlbee-command name="remove">
339                <short-description>Remove a buddy from your contact list</short-description>
340                <syntax>remove &lt;nick&gt;</syntax>
341
342                <description>
343                        <para>
344                                Removes the specified nick from your buddy list.
345                        </para>
346                </description>
347
348                <ircexample>
349                        <ircline nick="ctrlsoft">remove gryp</ircline>
350                        <ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
351                </ircexample>
352
353        </bitlbee-command>
354
355        <bitlbee-command name="block">
356                <short-description>Block someone</short-description>
357                <syntax>block &lt;nick&gt;</syntax>
358                <syntax>block &lt;connection&gt; &lt;handle&gt;</syntax>
359                <syntax>block &lt;connection&gt;</syntax>
360
361                <description>
362                        <para>
363                                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.
364                        </para>
365                       
366                        <para>
367                                When called with only a connection specification as an argument, the command displays the current block list for that connection.
368                        </para>
369                </description>
370        </bitlbee-command>
371
372        <bitlbee-command name="allow">
373                <short-description>Unblock someone</short-description>
374                <syntax>allow &lt;nick&gt;</syntax>
375                <syntax>allow &lt;connection&gt; &lt;handle&gt;</syntax>
376
377                <description>
378                        <para>
379                                Reverse of block. Unignores the specified user or user handle on specified connection.
380                        </para>
381                       
382                        <para>
383                                When called with only a connection specification as an argument, the command displays the current allow list for that connection.
384                        </para>
385                </description>
386        </bitlbee-command>
387       
388        <bitlbee-command name="otr">
389                <short-description>Off-the-Record encryption control</short-description>
390                <syntax>otr &lt;subcommand&gt; [&lt;arguments&gt;]</syntax>
391
392                <description>
393
394                        <para>
395                                Available subcommands: connect, disconnect, reconnect, smp, smpq, trust, info, keygen, and forget. See <emphasis>help otr &lt;subcommand&gt;</emphasis> for more information.
396                        </para>
397
398                </description>
399               
400                <bitlbee-command name="connect">
401                        <syntax>otr connect &lt;nick&gt;</syntax>
402                       
403                        <description>
404                       
405                                <para>
406                                        Attempts to establish an encrypted connection with the specified user by sending a magic string.
407                                </para>
408                               
409                        </description>
410               
411                </bitlbee-command>
412               
413                <bitlbee-command name="disconnect">
414                        <syntax>otr disconnect &lt;nick&gt;</syntax>
415                        <syntax>otr disconnect *</syntax>
416                       
417                        <description>
418                       
419                                <para>
420                                        Resets the connection with the specified user/all users to cleartext.
421                                </para>
422                               
423                        </description>
424               
425                </bitlbee-command>
426               
427                <bitlbee-command name="reconnect">
428                        <syntax>otr reconnect &lt;nick&gt;</syntax>
429                       
430                        <description>
431                       
432                                <para>
433                                        Breaks and re-establishes the encrypted connection with the specified user. Useful if something got desynced.
434                                </para>
435                               
436                                <para>
437                                        Equivalent to <emphasis>otr disconnect</emphasis> followed by <emphasis>otr connect</emphasis>.
438                                </para>
439                               
440                        </description>
441               
442                </bitlbee-command>
443               
444                <bitlbee-command name="smp">
445                        <syntax>otr smp &lt;nick&gt; &lt;secret&gt;</syntax>
446                       
447                        <description>
448                       
449                                <para>
450                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol.
451                                </para>
452                               
453                                <para>
454                                        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.
455                                </para>
456                               
457                                <para>
458                                        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.
459                                </para>
460                               
461                                <para>
462                                        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.
463                                </para>
464                               
465                        </description>
466               
467                </bitlbee-command>
468               
469                <bitlbee-command name="smpq">
470                        <syntax>otr smpq &lt;nick&gt; &lt;question&gt; &lt;answer&gt;</syntax>
471                       
472                        <description>
473                       
474                                <para>
475                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol, Q&amp;A style.
476                                </para>
477
478                                <para>
479                                        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!
480                                </para>
481                               
482                                <para>
483                                        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.
484                                </para>
485                               
486                        </description>
487               
488                </bitlbee-command>
489               
490                <bitlbee-command name="trust">
491                        <syntax>otr trust &lt;nick&gt; &lt;fp1&gt; &lt;fp2&gt; &lt;fp3&gt; &lt;fp4&gt; &lt;fp5&gt;</syntax>
492                       
493                        <description>
494                       
495                                <para>
496                                        Manually affirms trust in the specified fingerprint, given as five blocks of precisely eight (hexadecimal) digits each.
497                                </para>
498                               
499                        </description>
500               
501                </bitlbee-command>
502               
503                <bitlbee-command name="info">
504                        <syntax>otr info</syntax>
505                        <syntax>otr info &lt;nick&gt;</syntax>
506                       
507                        <description>
508                       
509                                <para>
510                                        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.
511                                </para>
512                               
513                        </description>
514               
515                </bitlbee-command>
516               
517                <bitlbee-command name="keygen">
518                        <syntax>otr keygen &lt;account-no&gt;</syntax>
519                       
520                        <description>
521                       
522                                <para>
523                                        Generates a new OTR private key for the given account.
524                                </para>
525                               
526                        </description>
527               
528                </bitlbee-command>
529               
530                <bitlbee-command name="forget">
531                        <syntax>otr forget &lt;thing&gt; &lt;arguments&gt;</syntax>
532                       
533                        <description>
534                       
535                                <para>
536                                        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.
537                                </para>
538                       
539                        </description>
540                       
541                        <bitlbee-command name="fingerprint">
542                                <syntax>otr forget fingerprint &lt;nick&gt; &lt;fingerprint&gt;</syntax>
543                               
544                                <description>
545                               
546                                        <para>
547                                                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.
548                                        </para>
549                                       
550                                </description>
551                               
552                        </bitlbee-command>
553                               
554                        <bitlbee-command name="context">
555                                <syntax>otr forget context &lt;nick&gt;</syntax>
556                               
557                                <description>
558                               
559                                        <para>
560                                                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.
561                                        </para>
562                                       
563                                </description>
564                               
565                        </bitlbee-command>
566
567                        <bitlbee-command name="key">
568                                <syntax>otr forget key &lt;fingerprint&gt;</syntax>
569                               
570                                <description>
571                               
572                                        <para>
573                                                Forgets an OTR private key matching the specified fingerprint. It is allowed to specify only a (unique) prefix of the fingerprint.
574                                        </para>
575                                       
576                                </description>
577                               
578                        </bitlbee-command>
579               
580                </bitlbee-command>
581               
582        </bitlbee-command>
583
584        <bitlbee-command name="set">
585                <short-description>Miscellaneous settings</short-description>
586                <syntax>set</syntax>
587                <syntax>set &lt;variable&gt;</syntax>
588                <syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
589                <syntax>set -del &lt;variable&gt;</syntax>
590
591                <description>
592
593                        <para>
594                                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.
595                        </para>
596
597                        <para>
598                                To get more help information about a setting, try:
599                        </para>
600
601                </description>
602
603                <ircexample>
604                        <ircline nick="ctrlsoft">help set private</ircline>
605                </ircexample>
606
607        </bitlbee-command>
608
609        <bitlbee-command name="help">
610                <short-description>BitlBee help system</short-description>
611
612                <syntax>help [subject]</syntax>
613
614                <description>
615                        <para>
616                                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.
617                        </para>
618                </description>
619        </bitlbee-command>
620
621        <bitlbee-command name="save">
622                <short-description>Save your account data</short-description>
623                <syntax>save</syntax>
624
625                <description>
626                        <para>
627                                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... ;-)
628                        </para>
629                </description>
630        </bitlbee-command>
631
632        <bitlbee-setting name="account" type="string" scope="channel">
633
634                <description>
635                        <para>
636                                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.
637                        </para>
638                </description>
639        </bitlbee-setting>
640
641        <bitlbee-setting name="allow_takeover" type="boolean" scope="global">
642                <default>true</default>
643
644                <description>
645                        <para>
646                                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.
647                        </para>
648                </description>
649        </bitlbee-setting>
650
651        <bitlbee-setting name="auto_connect" type="boolean" scope="account,global">
652                <default>true</default>
653
654                <description>
655                        <para>
656                                With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
657                        </para>
658                       
659                        <para>
660                                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!)
661                        </para>
662                </description>
663        </bitlbee-setting>
664
665        <bitlbee-setting name="auto_join" type="boolean" scope="channel">
666                <default>false</default>
667
668                <description>
669                        <para>
670                                With this option enabled, BitlBee will automatically join this channel when you log in.
671                        </para>
672                </description>
673        </bitlbee-setting>
674
675        <bitlbee-setting name="auto_reconnect" type="boolean" scope="account,global">
676                <default>true</default>
677
678                <description>
679                        <para>
680                                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.
681                        </para>
682
683                        <para>
684                                See also the <emphasis>auto_reconnect_delay</emphasis> setting.
685                        </para>
686
687                        <para>
688                                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!)
689                        </para>
690                </description>
691        </bitlbee-setting>
692
693        <bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
694                <default>5*3&lt;900</default>
695
696                <description>
697                        <para>
698                                Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
699                        </para>
700
701                        <para>
702                                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.
703                        </para>
704
705                        <para>
706                                See also the <emphasis>auto_reconnect</emphasis> setting.
707                        </para>
708                </description>
709        </bitlbee-setting>
710
711        <bitlbee-setting name="auto_reply_timeout" type="integer" scope="account">
712                <default>10800</default>
713
714                <description>
715                        <para>
716                                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").
717                        </para>
718
719                        <para>
720                                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.
721                        </para>
722
723                        <para>
724                                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).
725                        </para>
726                </description>
727        </bitlbee-setting>
728
729        <bitlbee-setting name="away" type="string" scope="account,global">
730                <description>
731                        <para>
732                                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.
733                        </para>
734
735                        <para>
736                                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.
737                        </para>
738
739                        <para>
740                                Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.
741                        </para>
742                </description>
743        </bitlbee-setting>
744
745        <bitlbee-setting name="away_devoice" type="boolean" scope="global">
746                <default>true</default>
747
748                <description>
749                        <para>
750                                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.
751                        </para>
752                       
753                        <para>
754                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
755                        </para>
756                </description>
757        </bitlbee-setting>
758
759        <bitlbee-setting name="away_reply_timeout" type="integer" scope="global">
760                <default>3600</default>
761
762                <description>
763                        <para>
764                                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.
765                        </para>
766
767                        <para>
768                                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.
769                        </para>
770                </description>
771        </bitlbee-setting>
772
773        <bitlbee-setting name="base_url" type="string" scope="account">
774                <default>http://api.twitter.com/1</default>
775
776                <description>
777                        <para>
778                                There are more services that understand the Twitter API than just Twitter.com. BitlBee can connect to all Twitter API implementations.
779                        </para>
780
781                        <para>
782                                For example, set this setting to <emphasis>http://identi.ca/api</emphasis> to use Identi.ca.
783                        </para>
784
785                        <para>
786                                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.
787                        </para>
788                </description>
789        </bitlbee-setting>
790
791        <bitlbee-setting name="charset" type="string" scope="global">
792                <default>utf-8</default>
793                <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
794
795                <description>
796                        <para>
797                                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.
798                        </para>
799
800                        <para>
801                                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
802                        </para>
803                </description>
804
805        </bitlbee-setting>
806
807        <bitlbee-setting name="color_encrypted" type="boolean" scope="global">
808                <default>true</default>
809
810                <description>
811                        <para>
812                                If set to true, BitlBee will color incoming encrypted messages according to their fingerprint trust level: untrusted=red, trusted=green.
813                        </para>
814                </description>
815        </bitlbee-setting>
816
817        <bitlbee-setting name="chat_type" type="string" scope="channel">
818                <default>groupchat</default>
819                <possible-values>groupchat, room</possible-values>
820
821                <description>
822                        <para>
823                                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.
824                        </para>
825                       
826                        <para>
827                                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.
828                        </para>
829                       
830                        <para>
831                                For setting up named chatrooms, it's currently easier to just use the <emphasis>chat add</emphasis> command.
832                        </para>
833                </description>
834        </bitlbee-setting>
835
836        <bitlbee-setting name="commands" type="boolean" scope="account">
837                <default>true</default>
838                <possible-values>true, false, strict</possible-values>
839
840                <description>
841                        <para>
842                                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:
843                        </para>
844
845                        <variablelist>
846                                <varlistentry><term>undo #[&lt;id&gt;]</term><listitem><para>Delete your last Tweet (or one with the given ID)</para></listitem></varlistentry>
847                                <varlistentry><term>rt &lt;screenname|#id&gt;</term><listitem><para>Retweet someone's last Tweet (or one with the given ID)</para></listitem></varlistentry>
848                                <varlistentry><term>reply &lt;screenname|#id&gt;</term><listitem><para>Reply to a Tweet (with a reply-to reference)</para></listitem></varlistentry>
849                                <varlistentry><term>rawreply &lt;screenname|#id&gt;</term><listitem><para>Reply to a Tweet (with no reply-to reference)</para></listitem></varlistentry>
850                                <varlistentry><term>report &lt;screenname|#id&gt;</term><listitem><para>Report the given user (or the user who posted the tweet with the given ID) for sending spam. This will also block them.</para></listitem></varlistentry>
851                                <varlistentry><term>follow &lt;screenname&gt;</term><listitem><para>Start following a person</para></listitem></varlistentry>
852                                <varlistentry><term>unfollow &lt;screenname&gt;</term><listitem><para>Stop following a person</para></listitem></varlistentry>
853                                <varlistentry><term>favourite &lt;screenname|#id&gt;</term><listitem><para>Favo<emphasis>u</emphasis>rite the given user's most recent tweet, or the given tweet ID.</para></listitem></varlistentry>
854                                <varlistentry><term>post &lt;message&gt;</term><listitem><para>Post a tweet</para></listitem></varlistentry>
855                                <varlistentry><term>url &lt;screenname|#id&gt;</term><listitem><para>Show URL for a tweet to open it in a browser (and see context)</para></listitem></varlistentry>
856                        </variablelist>
857
858                        <para>
859                                Anything that doesn't look like a command will be treated as a tweet. Watch out for typos, or to avoid this behaviour, you can set this setting to <emphasis>strict</emphasis>, which causes the <emphasis>post</emphasis> command to become mandatory for posting a tweet.
860                        </para>
861                </description>
862        </bitlbee-setting>
863
864        <bitlbee-setting name="debug" type="boolean" scope="global">
865                <default>false</default>
866
867                <description>
868                        <para>
869                                Some debugging messages can be logged if you wish. They're probably not really useful for you, unless you're doing some development on BitlBee.
870                        </para>
871                       
872                        <para>
873                                This feature is not currently used for anything so don't expect this to generate any output.
874                        </para>
875                </description>
876        </bitlbee-setting>
877
878        <bitlbee-setting name="default_target" type="string" scope="global">
879                <default>root</default>
880                <possible-values>root, last</possible-values>
881
882                <description>
883                        <para>
884                                With this value set to <emphasis>root</emphasis>, lines written in a 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 that control channel, set this to <emphasis>last</emphasis>.
885                        </para>
886                </description>
887        </bitlbee-setting>
888
889        <bitlbee-setting name="display_name" type="string" scope="account">
890                <description>
891                        <para>
892                                Currently only available for MSN connections, and for jabber groupchats.
893                        </para>
894                        <para>
895                                For MSN: 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.
896                        </para>
897                        <para>
898                                For jabber groupchats: this sets the default value of 'nick' for newly created groupchats. There is no way to set an account-wide nick like MSN.
899                        </para>
900                </description>
901        </bitlbee-setting>
902
903        <bitlbee-setting name="display_namechanges" type="boolean" scope="global">
904                <default>false</default>
905
906                <description>
907                        <para>
908                                With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
909                        </para>
910                </description>
911        </bitlbee-setting>
912
913        <bitlbee-setting name="display_timestamps" type="boolean" scope="global">
914                <default>true</default>
915
916                <description>
917                        <para>
918                                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.
919                        </para>
920                </description>
921        </bitlbee-setting>
922
923        <bitlbee-setting name="fill_by" type="string" scope="channel">
924                <default>all</default>
925                <possible-values>all, group, account, protocol</possible-values>
926
927                <description>
928                        <para>
929                                For control channels only: This setting determines which contacts the channel gets populated with.
930                        </para>
931
932                        <para>
933                                By default, control channels will contain all your contacts. You instead select contacts by buddy group, IM account or IM protocol.
934                        </para>
935                       
936                        <para>
937                                Change this setting and the corresponding <emphasis>account</emphasis>/<emphasis>group</emphasis>/<emphasis>protocol</emphasis> setting to set up this selection.
938                        </para>
939                       
940                        <para>
941                                With a ! prefix an inverted channel can be created, for example with this setting set to <emphasis>!group</emphasis> you can create a channel with all users <emphasis>not</emphasis> in that group.
942                        </para>
943                       
944                        <para>
945                                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>.
946                        </para>
947                </description>
948        </bitlbee-setting>
949
950        <bitlbee-setting name="group" type="string" scope="channel">
951
952                <description>
953                        <para>
954                                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.
955                        </para>
956                </description>
957        </bitlbee-setting>
958
959        <bitlbee-setting name="handle_unknown" type="string" scope="global">
960                <default>add_channel</default>
961                <possible-values>root, add, add_private, add_channel, ignore</possible-values>
962
963                <description>
964                        <para>
965                                By default, messages from people who aren't in your contact list are shown in a control channel instead of as a private message.
966                        </para>
967
968                        <para>
969                                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.
970                        </para>
971
972                        <note>
973                                <para>
974                                        Although these users will appear in your control channel, they aren't added to your real contact list. When you restart BitlBee, these auto-added users will be gone. If you want to keep someone in your list, you have to fixate the add using the <emphasis>add</emphasis> command.
975                                </para>
976                        </note>
977                </description>
978
979        </bitlbee-setting>
980
981        <bitlbee-setting name="ignore_auth_requests" type="boolean" scope="account">
982                <default>false</default>
983
984                <description>
985                        <para>
986                                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.
987                        </para>
988                </description>
989
990        </bitlbee-setting>
991
992        <bitlbee-setting name="lcnicks" type="boolean" scope="global">
993                <default>true</default>
994
995                <description>
996                        <para>
997                                Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
998                        </para>
999                </description>
1000
1001        </bitlbee-setting>
1002
1003        <bitlbee-setting name="local_display_name" type="boolean" scope="account">
1004                <default>false</default>
1005
1006                <description>
1007                        <para>
1008                                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.
1009                        </para>
1010                </description>
1011
1012        </bitlbee-setting>
1013
1014        <bitlbee-setting name="mail_notifications" type="boolean" scope="account">
1015                <default>false</default>
1016
1017                <description>
1018                        <para>
1019                                Some protocols (MSN, Yahoo!, GTalk) 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.
1020                        </para>
1021                </description>
1022
1023        </bitlbee-setting>
1024
1025        <bitlbee-setting name="mail_notifications_handle" type="string" scope="account">
1026                <default>empty</default>
1027
1028                <description>
1029                        <para>
1030                                This setting is available for protocols with e-mail notification functionality. If set to empty all e-mail notifications will go to control channel, if set to some string - this will be the name of a contact who will PRIVMSG you on every new notification.
1031                        </para>
1032                </description>
1033
1034        </bitlbee-setting>
1035
1036        <bitlbee-setting name="message_length" type="integer" scope="account">
1037                <default>140</default>
1038
1039                <description>
1040                        <para>
1041                                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.
1042                        </para>
1043
1044                        <para>
1045                                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.
1046                        </para>
1047                </description>
1048
1049        </bitlbee-setting>
1050
1051        <bitlbee-setting name="stream" type="boolean" scope="account">
1052                <default>true</default>
1053
1054                <description>
1055                        <para>
1056                                For Twitter accounts, this setting enables use of the Streaming API. This automatically gives you incoming DMs as well.
1057                        </para>
1058                       
1059                        <para>
1060                                For other Twitter-like services, this setting is not supported.
1061                        </para>
1062                </description>
1063
1064        </bitlbee-setting>
1065       
1066        <bitlbee-setting name="target_url_length" type="integer" scope="account">
1067                <default>20</default>
1068
1069                <description>
1070                        <para>
1071                                Twitter replaces every URL with fixed-length t.co URLs. BitlBee is able to take t.co urls into account when calculating <emphasis>message_length</emphasis> replacing the actual URL length with target_url_length. Setting target_url_length to 0 disables this feature.
1072                        </para>
1073
1074                        <para>
1075                                This setting is disabled for identica accounts by default and will not affect anything other than message safety checks (i.e. Twitter will still replace your URLs with t.co links, even if that makes them longer).
1076                        </para>
1077                </description>
1078
1079        </bitlbee-setting>
1080
1081        <bitlbee-setting name="mode" type="string" scope="account">
1082                <possible-values>one, many, chat</possible-values>
1083                <default>chat</default>
1084
1085                <description>
1086                        <para>
1087                                By default, BitlBee will create a separate channel (called #twitter_yourusername) for all your Twitter contacts/messages.
1088                        </para>
1089
1090                        <para>
1091                                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).
1092                        </para>
1093                       
1094                        <para>
1095                                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.
1096                        </para>
1097                       
1098                        <para>
1099                                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.
1100                        </para>
1101                </description>
1102
1103        </bitlbee-setting>
1104
1105        <bitlbee-setting name="mobile_is_away" type="boolean" scope="global">
1106                <default>false</default>
1107
1108                <description>
1109                        <para>
1110                                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.
1111                        </para>
1112                </description>
1113
1114        </bitlbee-setting>
1115
1116        <bitlbee-setting name="nick" type="string" scope="chat">
1117                <description>
1118                        <para>
1119                                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.
1120                        </para>
1121                </description>
1122        </bitlbee-setting>
1123
1124        <bitlbee-setting name="nick_format" type="string" scope="account,global">
1125                <default>%-@nick</default>
1126
1127                <description>
1128                        <para>
1129                                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.
1130                        </para>
1131
1132                        <para>
1133                                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.
1134                        </para>
1135
1136                        <para>
1137                                It's easier to describe this setting using a few examples:
1138                        </para>
1139
1140                        <para>
1141                                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.
1142                        </para>
1143
1144                        <para>
1145                                [%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.
1146                        </para>
1147
1148                        <para>
1149                                See <emphasis>help nick_format</emphasis> for more information.
1150                        </para>
1151                </description>
1152        </bitlbee-setting>
1153
1154        <bitlbee-setting name="nick_source" type="string" scope="account">
1155                <default>handle</default>
1156                <possible-values>handle, full_name, first_name</possible-values>
1157
1158                <description>
1159                        <para>
1160                                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.
1161                        </para>
1162
1163                        <para>
1164                                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.
1165                        </para>
1166                </description>
1167        </bitlbee-setting>
1168
1169        <bitlbee-setting name="oauth" type="boolean" scope="account">
1170                <default>true</default>
1171
1172                <description>
1173                        <para>
1174                                This enables OAuth authentication for an IM account; right now the Twitter (working for Twitter only) and Jabber (for Google Talk, Facebook and MSN Messenger) module support it.
1175                        </para>
1176
1177                        <para>
1178                                With OAuth enabled, you shouldn't tell BitlBee your account 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 the service. If this succeeds, you will get a PIN code which you can give back to BitlBee to finish the process.
1179                        </para>
1180
1181                        <para>
1182                                The resulting access token will be saved permanently, so you have to do this only once. If for any reason you want to/have to reauthenticate, you can use <emphasis>account set</emphasis> to reset the account password to something random.
1183                        </para>
1184                </description>
1185
1186        </bitlbee-setting>
1187
1188        <bitlbee-setting name="anonymous" type="boolean" scope="account">
1189                <default>false</default>
1190
1191                <description>
1192                        <para>
1193                                This enables SASL ANONYMOUS login for jabber accounts, as specified by XEP-0175.
1194                        </para>
1195
1196                        <para>
1197                                With this setting enabled, if the server allows this method, a password isn't required and the username part of the JID is ignored (you can use anonymous@jabber.example.com). Servers will usually assign you a random numeric username instead.
1198                        </para>
1199                </description>
1200
1201        </bitlbee-setting>
1202
1203        <bitlbee-setting name="ops" type="string" scope="global">
1204                <default>both</default>
1205                <possible-values>both, root, user, none</possible-values>
1206
1207                <description>
1208                        <para>
1209                                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.
1210                        </para>
1211
1212                        <para>
1213                                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.
1214                        </para>
1215                </description>
1216        </bitlbee-setting>
1217
1218        <bitlbee-setting name="otr_policy" type="string" scope="global">
1219                <default>opportunistic</default>
1220                <possible-values>never, opportunistic, manual, always</possible-values>
1221
1222                <description>
1223                        <para>
1224                                This setting controls the policy for establishing Off-the-Record connections.
1225                        </para>
1226                        <para>
1227                                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.
1228                        </para>
1229                </description>
1230        </bitlbee-setting>
1231
1232        <bitlbee-setting name="password" type="string" scope="account,global">
1233                <description>
1234                        <para>
1235                                Use this global setting to change your "NickServ" password.
1236                        </para>
1237                       
1238                        <para>
1239                                This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
1240                        </para>
1241                       
1242                        <para>
1243                                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.
1244                        </para>
1245                </description>
1246        </bitlbee-setting>
1247
1248        <bitlbee-setting name="paste_buffer" type="boolean" scope="global">
1249                <default>false</default>
1250
1251                <description>
1252                        <para>
1253                                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.
1254                        </para>
1255
1256                        <para>
1257                                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.
1258                        </para>
1259
1260                        <para>
1261                                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.
1262                        </para>
1263                </description>
1264        </bitlbee-setting>
1265
1266        <bitlbee-setting name="paste_buffer_delay" type="integer" scope="global">
1267                <default>200</default>
1268
1269                <description>
1270
1271                        <para>
1272                                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.
1273                        </para>
1274
1275                        <para>
1276                                See also the <emphasis>paste_buffer</emphasis> setting.
1277                        </para>
1278                </description>
1279        </bitlbee-setting>
1280       
1281        <bitlbee-setting name="port" type="integer" scope="account">
1282                <description>
1283                        <para>
1284                                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.
1285                        </para>
1286                </description>
1287        </bitlbee-setting>
1288
1289        <bitlbee-setting name="priority" type="integer" scope="account">
1290                <default>0</default>
1291
1292                <description>
1293                        <para>
1294                                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).
1295                        </para>
1296
1297                        <para>
1298                                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).
1299                        </para>
1300                </description>
1301        </bitlbee-setting>
1302
1303        <bitlbee-setting name="private" type="boolean" scope="global">
1304                <default>true</default>
1305
1306                <description>
1307                        <para>
1308                                If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in a control channel.
1309                        </para>
1310
1311                        <para>
1312                                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.
1313                        </para>
1314                </description>
1315        </bitlbee-setting>
1316
1317        <bitlbee-setting name="protocol" type="string" scope="channel">
1318
1319                <description>
1320                        <para>
1321                                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.
1322                        </para>
1323                </description>
1324        </bitlbee-setting>
1325
1326        <bitlbee-setting name="proxy" type="string" scope="account">
1327                <default>&lt;local&gt;&lt;auto&gt;</default>
1328
1329                <description>
1330                        <para>
1331                                A list of <emphasis>file transfer proxies</emphasis> for jabber. This isn't the connection proxy. Sorry, look in bitlbee.conf for those.
1332                        </para>
1333
1334                        <para>
1335                                It's a semicolon-separated list of items that can be either <emphasis>JID,HOST,PORT</emphasis> or two special values, <emphasis>&lt;local&gt;</emphasis> (to try a direct connection first) and <emphasis>&lt;auto&gt;</emphasis> (to try to discover a proxy). For example, "&lt;local&gt;;proxy.somewhere.org,123.123.123.123,7777".
1336                        </para>
1337                        <para>
1338                                The address should point to a SOCKS5 bytestreams server, usually provided by jabber servers. This is only used for sending files. Note that the host address might not match what DNS tells you, and the port isn't always the same.
1339                        </para>
1340                        <para>
1341                                The correct way to get a socks proxy host/port is a mystery, and the file transfer might fail anyway. Maybe just try using dropbox instead.
1342                        </para>
1343                </description>
1344        </bitlbee-setting>
1345
1346        <bitlbee-setting name="query_order" type="string" scope="global">
1347                <default>lifo</default>
1348                <possible-values>lifo, fifo</possible-values>
1349
1350                <description>
1351                        <para>
1352                                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.
1353                        </para>
1354
1355                        <para>
1356                                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).
1357                        </para>
1358                </description>
1359        </bitlbee-setting>
1360
1361        <bitlbee-setting name="resource" type="string" scope="account">
1362                <default>BitlBee</default>
1363
1364                <description>
1365                        <para>
1366                                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.
1367                        </para>
1368                </description>
1369        </bitlbee-setting>
1370
1371        <bitlbee-setting name="resource_select" type="string" scope="account">
1372                <default>activity</default>
1373                <possible-values>priority, activity</possible-values>
1374
1375                <description>
1376                        <para>
1377                                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.
1378                        </para>
1379
1380                        <para>
1381                                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).
1382                        </para>
1383                </description>
1384        </bitlbee-setting>
1385
1386        <bitlbee-setting name="root_nick" type="string" scope="global">
1387                <default>root</default>
1388
1389                <description>
1390                        <para>
1391                                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.
1392                        </para>
1393                </description>
1394        </bitlbee-setting>
1395
1396        <bitlbee-setting name="save_on_quit" type="boolean" scope="global">
1397                <default>true</default>
1398
1399                <description>
1400                        <para>
1401                                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.
1402                        </para>
1403                </description>
1404        </bitlbee-setting>
1405
1406        <bitlbee-setting name="server" type="string" scope="account">
1407                <description>
1408                        <para>
1409                                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.
1410                        </para>
1411                </description>
1412        </bitlbee-setting>
1413
1414        <bitlbee-setting name="show_ids" type="boolean" scope="account">
1415                <default>true</default>
1416
1417                <description>
1418                        <para>
1419                                Enable this setting on a Twitter account to have BitlBee include a two-digit "id" in front of every message. This id can then be used for replies and retweets.
1420                        </para>
1421                </description>
1422        </bitlbee-setting>
1423
1424        <bitlbee-setting name="show_offline" type="boolean" scope="global">
1425                <default>false</default>
1426
1427                <description>
1428                        <para>
1429                                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.
1430                        </para>
1431                       
1432                        <para>
1433                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
1434                        </para>
1435                </description>
1436        </bitlbee-setting>
1437
1438        <bitlbee-setting name="show_users" type="string" scope="channel">
1439                <default>online+,away</default>
1440
1441                <description>
1442                        <para>
1443                                Comma-separated list of statuses of users you want in the channel,
1444                                and any modes they should have. The following statuses are currently
1445                                recognised: <emphasis>online</emphasis> (i.e. available, not
1446                                away), <emphasis>away</emphasis>, and <emphasis>offline</emphasis>.
1447                        </para>
1448                       
1449                        <para>
1450                                If a status is followed by a valid channel mode character
1451                                (@, % or +), it will be given to users with that status.
1452                                For example, <emphasis>online@,away+,offline</emphasis> will
1453                                show all users in the channel. Online people will
1454                                have +o, people who are online but away will have +v,
1455                                and others will have no special modes.
1456                        </para>
1457                </description>
1458        </bitlbee-setting>
1459
1460        <bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
1461                <default>true</default>
1462
1463                <description>
1464                        <para>
1465                                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 channels window clean. If you don't like this (or if your IRC client doesn't support this) you can disable this setting.
1466                        </para>
1467                </description>
1468        </bitlbee-setting>
1469
1470        <bitlbee-setting name="ssl" type="boolean" scope="account">
1471                <default>false</default>
1472
1473                <description>
1474                        <para>
1475                                Currently only available for Jabber connections. Set this to true if you want to connect to the server on an SSL-enabled port (usually 5223).
1476                        </para>
1477
1478                        <para>
1479                                Please note that this method of establishing a secure connection to the server has long been deprecated. You are encouraged to look at the <emphasis>tls</emphasis> setting instead.
1480                        </para>
1481                </description>
1482        </bitlbee-setting>
1483
1484        <bitlbee-setting name="status" type="string" scope="account,global">
1485                <description>
1486                        <para>
1487                                Most IM protocols 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.
1488                        </para>
1489
1490                        <para>
1491                                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).
1492                        </para>
1493
1494                        <para>
1495                                Away states set using <emphasis>/away</emphasis> or the <emphasis>away</emphasis> setting will override this setting. To clear the setting, use <emphasis>set -del status</emphasis>.
1496                        </para>
1497                </description>
1498        </bitlbee-setting>
1499
1500        <bitlbee-setting name="strip_html" type="boolean" scope="global">
1501                <default>true</default>
1502
1503                <description>
1504                        <para>
1505                                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.
1506                        </para>
1507                        <para>
1508                                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.
1509                        </para>
1510                </description>
1511        </bitlbee-setting>
1512
1513        <bitlbee-setting name="strip_newlines" type="boolean" scope="account">
1514                <default>false</default>
1515
1516                <description>
1517                        <para>
1518                                Turn on this flag to prevent tweets from spanning over multiple lines.
1519                        </para>
1520                </description>
1521        </bitlbee-setting>
1522
1523        <bitlbee-setting name="show_old_mentions" type="integer" scope="account">
1524                <default>20</default>
1525
1526                <description>
1527                        <para>
1528                                This setting specifies the number of old mentions to fetch on connection. Must be less or equal to 200. Setting it to 0 disables this feature.
1529                        </para>
1530                </description>
1531        </bitlbee-setting>
1532
1533        <bitlbee-setting name="switchboard_keepalives" type="boolean" scope="account">
1534                <default>false</default>
1535
1536                <description>
1537                        <para>
1538                                Turn on this flag if you have difficulties talking to offline/invisible contacts.
1539                        </para>
1540                       
1541                        <para>
1542                                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.
1543                        </para>
1544                       
1545                        <para>
1546                                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.
1547                        </para>
1548                </description>
1549        </bitlbee-setting>
1550
1551        <bitlbee-setting name="tag" type="string" scope="account">
1552                <description>
1553                        <para>
1554                                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.
1555                        </para>
1556
1557                        <para>
1558                                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.
1559                        </para>
1560                </description>
1561        </bitlbee-setting>
1562
1563        <bitlbee-setting name="timezone" type="string" scope="global">
1564                <default>local</default>
1565                <possible-values>local, utc, gmt, timezone-spec</possible-values>
1566
1567                <description>
1568                        <para>
1569                                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.
1570                        </para>
1571
1572                        <para>
1573                                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.
1574                        </para>
1575                </description>
1576        </bitlbee-setting>
1577
1578        <bitlbee-setting name="tls" type="boolean" scope="account">
1579                <default>true</default>
1580
1581                <description>
1582                        <para>
1583                                By default (with this setting enabled), BitlBee will require Jabber servers to offer encryption via StartTLS and refuse to connect if they don't.
1584                        </para>
1585
1586                        <para>
1587                                If you set this to "try", BitlBee will use StartTLS only if it's offered. With the setting disabled, StartTLS support will be ignored and avoided entirely.
1588                        </para>
1589                </description>
1590        </bitlbee-setting>
1591
1592        <bitlbee-setting name="tls_verify" type="boolean" scope="account">
1593                <default>true</default>
1594
1595                <description>
1596                        <para>
1597                                Currently only available for Jabber connections in combination with the <emphasis>tls</emphasis> setting. Set this to <emphasis>true</emphasis> if you want BitlBee to strictly verify the server's certificate against a list of trusted certificate authorities.
1598                        </para>
1599
1600                        <para>
1601                                The hostname used in the certificate verification is the value of the <emphasis>server</emphasis> setting if the latter is nonempty and the domain of the username else. If you get a hostname related error when connecting to Google Talk with a username from the gmail.com or googlemail.com domain, please try to empty the <emphasis>server</emphasis> setting.
1602                        </para>
1603
1604                        <para>
1605                                Please note that no certificate verification is performed when the <emphasis>ssl</emphasis> setting is used, or when the <emphasis>CAfile</emphasis> setting in <emphasis>bitlbee.conf</emphasis> is not set.
1606                        </para>
1607                </description>
1608        </bitlbee-setting>
1609
1610        <bitlbee-setting name="to_char" type="string" scope="global">
1611                <default>": "</default>
1612
1613                <description>
1614                        <para>
1615                                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>.
1616                        </para>
1617
1618                        <para>
1619                                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.
1620                        </para>
1621                </description>
1622        </bitlbee-setting>
1623
1624        <bitlbee-setting name="translate_to_nicks" type="boolean" scope="channel">
1625                <default>true</default>
1626
1627                <description>
1628                        <para>
1629                                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.
1630                        </para>
1631
1632                        <para>
1633                                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.
1634                        </para>
1635                </description>
1636        </bitlbee-setting>
1637
1638        <bitlbee-setting name="type" type="string" scope="channel">
1639                <default>control</default>
1640                <possible-values>control, chat</possible-values>
1641
1642                <description>
1643                        <para>
1644                                BitlBee supports two kinds of channels: control channels (usually with a name starting with a &amp;) and chatroom channels (name usually starts with a #).
1645                        </para>
1646
1647                        <para>
1648                                See <emphasis>help channels</emphasis> for a full description of channel types in BitlBee.
1649                        </para>
1650                </description>
1651        </bitlbee-setting>
1652
1653        <bitlbee-setting name="typing_notice" type="boolean" scope="global">
1654                <default>false</default>
1655
1656                <description>
1657                        <para>
1658                                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.
1659                        </para>
1660                </description>
1661        </bitlbee-setting>
1662
1663        <bitlbee-setting name="user_agent" type="string" scope="account">
1664                <default>BitlBee</default>
1665
1666                <description>
1667                        <para>
1668                                Some Jabber servers are configured to only allow a few (or even just one) kinds of XMPP clients to connect to them.
1669                        </para>
1670                       
1671                        <para>
1672                                You can change this setting to make BitlBee present itself as a different client, so that you can still connect to these servers.
1673                        </para>
1674                </description>
1675        </bitlbee-setting>
1676
1677        <bitlbee-setting name="utf8_nicks" type="boolean" scope="global">
1678                <default>false</default>
1679
1680                <description>
1681                        <para>
1682                                Officially, IRC nicknames are restricted to ASCII. Recently some clients and servers started supporting Unicode nicknames though. To enable UTF-8 nickname support (contacts only) in BitlBee, enable this setting.
1683                        </para>
1684                       
1685                        <para>
1686                                To avoid confusing old clients, this setting is disabled by default. Be careful when you try it, and be prepared to be locked out of your BitlBee in case your client interacts poorly with UTF-8 nicknames.
1687                        </para>
1688                </description>
1689        </bitlbee-setting>
1690
1691        <bitlbee-setting name="web_aware" type="string" scope="account">
1692                <default>false</default>
1693
1694                <description>
1695                        <para>
1696                                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.
1697                        </para>
1698
1699                        <para>
1700                                Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
1701                        </para>
1702                </description>
1703        </bitlbee-setting>
1704
1705        <bitlbee-setting name="xmlconsole" type="boolean" scope="account">
1706                <default>false</default>
1707
1708                <description>
1709                        <para>
1710                                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.
1711                        </para>
1712                        <para>
1713                                If you want to enable this XML console permanently (and at login time already), you can set this setting.
1714                        </para>
1715                </description>
1716        </bitlbee-setting>
1717
1718        <bitlbee-command name="rename">
1719                <short-description>Rename (renick) a buddy</short-description>
1720                <syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
1721                <syntax>rename -del &lt;oldnick&gt;</syntax>
1722
1723                <description>
1724                        <para>
1725                                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).
1726                        </para>
1727                       
1728                        <para>
1729                                <emphasis>rename -del</emphasis> can be used to erase your manually set nickname for a contact and reset it to what was automatically generated.
1730                        </para>
1731                </description>
1732
1733                <ircexample>
1734                        <ircline nick="itsme">rename itsme_ you</ircline>
1735                        <ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
1736                </ircexample>
1737
1738        </bitlbee-command>
1739
1740        <bitlbee-command name="yes">
1741                <short-description>Accept a request</short-description>
1742                <syntax>yes [&lt;number&gt;]</syntax>
1743
1744                <description>
1745                        <para>
1746                                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.
1747                        </para>
1748
1749                        <para>
1750                                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.
1751                        </para>
1752                </description>
1753
1754        </bitlbee-command>
1755
1756        <bitlbee-command name="no">
1757                <short-description>Deny a request</short-description>
1758                <syntax>no [&lt;number&gt;]</syntax>
1759
1760                <description>
1761                        <para>
1762                                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.
1763                        </para>
1764
1765                        <para>
1766                                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.
1767                        </para>
1768                </description>
1769        </bitlbee-command>
1770
1771        <bitlbee-command name="qlist">
1772                <short-description>List all the unanswered questions root asked</short-description>
1773                <syntax>qlist</syntax>
1774
1775                <description>
1776                        <para>
1777                                This gives you a list of all the unanswered questions from root.
1778                        </para>
1779                </description>
1780
1781        </bitlbee-command>
1782
1783        <bitlbee-command name="register">
1784                <short-description>Register yourself</short-description>
1785                <syntax>register [&lt;password&gt;]</syntax>
1786
1787                <description>
1788                        <para>
1789                                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.
1790                        </para>
1791
1792                        <para>
1793                                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.. ;-)
1794                        </para>
1795
1796                        <para>
1797                                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.
1798                        </para>
1799
1800                        <para>
1801                                You can omit the password and enter it separately using the IRC /OPER command. This lets you enter your password without your IRC client echoing it on screen or recording it in logs.
1802                        </para>
1803                </description>
1804
1805        </bitlbee-command>
1806
1807        <bitlbee-command name="identify">
1808                <syntax>identify [-noload|-force] [&lt;password&gt;]</syntax>
1809                <short-description>Identify yourself with your password</short-description>
1810
1811                <description>
1812                        <para>
1813                                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.
1814                        </para>
1815
1816                        <para>
1817                                Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
1818                        </para>
1819
1820                        <para>
1821                                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).
1822                        </para>
1823                       
1824                        <para>
1825                                <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).
1826                        </para>
1827
1828                        <para>
1829                                You can omit the password and enter it separately using the IRC /OPER command. This lets you enter your password without your IRC client echoing it on screen or recording it in logs.
1830                        </para>
1831                </description>
1832        </bitlbee-command>
1833
1834        <bitlbee-command name="drop">
1835                <syntax>drop &lt;password&gt;</syntax>
1836                <short-description>Drop your account</short-description>
1837
1838                <description>
1839                        <para>
1840                                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.
1841                        </para>
1842                </description>
1843        </bitlbee-command>
1844
1845        <bitlbee-command name="blist">
1846                <syntax>blist [all|online|offline|away] [&lt;pattern&gt;]</syntax>
1847                <short-description>List all the buddies in the current channel</short-description>
1848
1849                <description>
1850                        <para>
1851                                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.
1852                        </para>
1853
1854                        <para>
1855                                A perl-compatible regular expression can be supplied as <emphasis>pattern</emphasis> to filter the results (case-insensitive).
1856                        </para>
1857                </description>
1858
1859        </bitlbee-command>
1860
1861        <bitlbee-command name="group">
1862                <short-description>Contact group management</short-description>
1863                <syntax>group [ list | info &lt;group&gt; ]</syntax>
1864
1865                <description>
1866                        <para>
1867                                The <emphasis>group list</emphasis> command shows a list of all groups defined so far.
1868                        </para>
1869                       
1870                        <para>
1871                                The <emphasis>group info</emphasis> command shows a list of all members of a the group &lt;group&gt;.
1872                        </para>
1873                       
1874                        <para>
1875                                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.
1876                        </para>
1877                </description>
1878        </bitlbee-command>
1879       
1880        <bitlbee-command name="transfer">
1881                <short-description>Monitor, cancel, or reject file transfers</short-description>
1882                <syntax>transfer [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
1883               
1884                <description>
1885                        <para>
1886                                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.
1887                        </para>
1888
1889                        <ircexample>
1890                                <ircline nick="ulim">transfer</ircline>
1891                        </ircexample>
1892                </description>
1893               
1894                <bitlbee-command name="cancel">
1895                        <short-description>Cancels the file transfer with the given id</short-description>
1896                        <syntax>transfer &lt;cancel&gt; id</syntax>
1897
1898                        <description>
1899                                <para>Cancels the file transfer with the given id</para>
1900                        </description>
1901
1902                        <ircexample>
1903                                <ircline nick="ulim">transfer cancel 1</ircline>
1904                                <ircline nick="root">Canceling file transfer for test</ircline>
1905                        </ircexample>
1906                </bitlbee-command>
1907
1908                <bitlbee-command name="reject">
1909                        <short-description>Rejects all incoming transfers</short-description>
1910                        <syntax>transfer &lt;reject&gt;</syntax>
1911
1912                        <description>
1913                                <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is necessary. Or is it?</para>
1914                        </description>
1915
1916                        <ircexample>
1917                                <ircline nick="ulim">transfer reject</ircline>
1918                        </ircexample>
1919                </bitlbee-command>
1920        </bitlbee-command>
1921       
1922</chapter>
Note: See TracBrowser for help on using the repository browser.