source: doc/user-guide/commands.xml @ 3f661849

Last change on this file since 3f661849 was 3592b95, checked in by Wilmer van der Gaast <wilmer@…>, at 2012-11-25T20:21:24Z

To address #991, adding a strict commands mode, where one has to use "post"
to post tweets.
  • Property mode set to 100644
File size: 71.6 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 commands 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 infomation 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 infomation 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                       
416                        <description>
417                       
418                                <para>
419                                        Resets the connection with the specified user to cleartext.
420                                </para>
421                               
422                        </description>
423               
424                </bitlbee-command>
425               
426                <bitlbee-command name="reconnect">
427                        <syntax>otr reconnect &lt;nick&gt;</syntax>
428                       
429                        <description>
430                       
431                                <para>
432                                        Breaks and re-establishes the encrypted connection with the specified user. Useful if something got desynced.
433                                </para>
434                               
435                                <para>
436                                        Equivalent to <emphasis>otr disconnect</emphasis> followed by <emphasis>otr connect</emphasis>.
437                                </para>
438                               
439                        </description>
440               
441                </bitlbee-command>
442               
443                <bitlbee-command name="smp">
444                        <syntax>otr smp &lt;nick&gt; &lt;secret&gt;</syntax>
445                       
446                        <description>
447                       
448                                <para>
449                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol.
450                                </para>
451                               
452                                <para>
453                                        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.
454                                </para>
455                               
456                                <para>
457                                        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.
458                                </para>
459                               
460                                <para>
461                                        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.
462                                </para>
463                               
464                        </description>
465               
466                </bitlbee-command>
467               
468                <bitlbee-command name="smpq">
469                        <syntax>otr smpq &lt;nick&gt; &lt;question&gt; &lt;answer&gt;</syntax>
470                       
471                        <description>
472                       
473                                <para>
474                                        Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol, Q&amp;A style.
475                                </para>
476
477                                <para>
478                                        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!
479                                </para>
480                               
481                                <para>
482                                        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.
483                                </para>
484                               
485                        </description>
486               
487                </bitlbee-command>
488               
489                <bitlbee-command name="trust">
490                        <syntax>otr trust &lt;nick&gt; &lt;fp1&gt; &lt;fp2&gt; &lt;fp3&gt; &lt;fp4&gt; &lt;fp5&gt;</syntax>
491                       
492                        <description>
493                       
494                                <para>
495                                        Manually affirms trust in the specified fingerprint, given as five blocks of precisely eight (hexadecimal) digits each.
496                                </para>
497                               
498                        </description>
499               
500                </bitlbee-command>
501               
502                <bitlbee-command name="info">
503                        <syntax>otr info</syntax>
504                        <syntax>otr info &lt;nick&gt;</syntax>
505                       
506                        <description>
507                       
508                                <para>
509                                        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.
510                                </para>
511                               
512                        </description>
513               
514                </bitlbee-command>
515               
516                <bitlbee-command name="keygen">
517                        <syntax>otr keygen &lt;account-no&gt;</syntax>
518                       
519                        <description>
520                       
521                                <para>
522                                        Generates a new OTR private key for the given account.
523                                </para>
524                               
525                        </description>
526               
527                </bitlbee-command>
528               
529                <bitlbee-command name="forget">
530                        <syntax>otr forget &lt;thing&gt; &lt;arguments&gt;</syntax>
531                       
532                        <description>
533                       
534                                <para>
535                                        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.
536                                </para>
537                       
538                        </description>
539                       
540                        <bitlbee-command name="fingerprint">
541                                <syntax>otr forget fingerprint &lt;nick&gt; &lt;fingerprint&gt;</syntax>
542                               
543                                <description>
544                               
545                                        <para>
546                                                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.
547                                        </para>
548                                       
549                                </description>
550                               
551                        </bitlbee-command>
552                               
553                        <bitlbee-command name="context">
554                                <syntax>otr forget context &lt;nick&gt;</syntax>
555                               
556                                <description>
557                               
558                                        <para>
559                                                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.
560                                        </para>
561                                       
562                                </description>
563                               
564                        </bitlbee-command>
565
566                        <bitlbee-command name="key">
567                                <syntax>otr forget key &lt;fingerprint&gt;</syntax>
568                               
569                                <description>
570                               
571                                        <para>
572                                                Forgets an OTR private key matching the specified fingerprint. It is allowed to specify only a (unique) prefix of the fingerprint.
573                                        </para>
574                                       
575                                </description>
576                               
577                        </bitlbee-command>
578               
579                </bitlbee-command>
580               
581        </bitlbee-command>
582
583        <bitlbee-command name="set">
584                <short-description>Miscellaneous settings</short-description>
585                <syntax>set</syntax>
586                <syntax>set &lt;variable&gt;</syntax>
587                <syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
588                <syntax>set -del &lt;variable&gt;</syntax>
589
590                <description>
591
592                        <para>
593                                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.
594                        </para>
595
596                        <para>
597                                To get more help information about a setting, try:
598                        </para>
599
600                </description>
601
602                <ircexample>
603                        <ircline nick="ctrlsoft">help set private</ircline>
604                </ircexample>
605
606        </bitlbee-command>
607
608        <bitlbee-command name="help">
609                <short-description>BitlBee help system</short-description>
610
611                <syntax>help [subject]</syntax>
612
613                <description>
614                        <para>
615                                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.
616                        </para>
617                </description>
618        </bitlbee-command>
619
620        <bitlbee-command name="save">
621                <short-description>Save your account data</short-description>
622                <syntax>save</syntax>
623
624                <description>
625                        <para>
626                                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... ;-)
627                        </para>
628                </description>
629        </bitlbee-command>
630
631        <bitlbee-setting name="account" type="string" scope="channel">
632
633                <description>
634                        <para>
635                                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.
636                        </para>
637                </description>
638        </bitlbee-setting>
639
640        <bitlbee-setting name="allow_takeover" type="boolean" scope="global">
641                <default>true</default>
642
643                <description>
644                        <para>
645                                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.
646                        </para>
647                </description>
648        </bitlbee-setting>
649
650        <bitlbee-setting name="auto_connect" type="boolean" scope="account,global">
651                <default>true</default>
652
653                <description>
654                        <para>
655                                With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
656                        </para>
657                       
658                        <para>
659                                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!)
660                        </para>
661                </description>
662        </bitlbee-setting>
663
664        <bitlbee-setting name="auto_join" type="boolean" scope="channel">
665                <default>false</default>
666
667                <description>
668                        <para>
669                                With this option enabled, BitlBee will automatically join this channel when you log in.
670                        </para>
671                </description>
672        </bitlbee-setting>
673
674        <bitlbee-setting name="auto_reconnect" type="boolean" scope="account,global">
675                <default>true</default>
676
677                <description>
678                        <para>
679                                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.
680                        </para>
681
682                        <para>
683                                See also the <emphasis>auto_reconnect_delay</emphasis> setting.
684                        </para>
685
686                        <para>
687                                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!)
688                        </para>
689                </description>
690        </bitlbee-setting>
691
692        <bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
693                <default>5*3&lt;900</default>
694
695                <description>
696                        <para>
697                                Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
698                        </para>
699
700                        <para>
701                                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.
702                        </para>
703
704                        <para>
705                                See also the <emphasis>auto_reconnect</emphasis> setting.
706                        </para>
707                </description>
708        </bitlbee-setting>
709
710        <bitlbee-setting name="auto_reply_timeout" type="integer" scope="account">
711                <default>10800</default>
712
713                <description>
714                        <para>
715                                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").
716                        </para>
717
718                        <para>
719                                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.
720                        </para>
721
722                        <para>
723                                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).
724                        </para>
725                </description>
726        </bitlbee-setting>
727
728        <bitlbee-setting name="away" type="string" scope="account,global">
729                <description>
730                        <para>
731                                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.
732                        </para>
733
734                        <para>
735                                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.
736                        </para>
737
738                        <para>
739                                Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.
740                        </para>
741                </description>
742        </bitlbee-setting>
743
744        <bitlbee-setting name="away_devoice" type="boolean" scope="global">
745                <default>true</default>
746
747                <description>
748                        <para>
749                                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.
750                        </para>
751                       
752                        <para>
753                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
754                        </para>
755                </description>
756        </bitlbee-setting>
757
758        <bitlbee-setting name="away_reply_timeout" type="integer" scope="global">
759                <default>3600</default>
760
761                <description>
762                        <para>
763                                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.
764                        </para>
765
766                        <para>
767                                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.
768                        </para>
769                </description>
770        </bitlbee-setting>
771
772        <bitlbee-setting name="base_url" type="string" scope="account">
773                <default>http://api.twitter.com/1</default>
774
775                <description>
776                        <para>
777                                There are more services that understand the Twitter API than just Twitter.com. BitlBee can connect to all Twitter API implementations.
778                        </para>
779
780                        <para>
781                                For example, set this setting to <emphasis>http://identi.ca/api</emphasis> to use Identi.ca.
782                        </para>
783
784                        <para>
785                                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.
786                        </para>
787                </description>
788        </bitlbee-setting>
789
790        <bitlbee-setting name="charset" type="string" scope="global">
791                <default>utf-8</default>
792                <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
793
794                <description>
795                        <para>
796                                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.
797                        </para>
798
799                        <para>
800                                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
801                        </para>
802                </description>
803
804        </bitlbee-setting>
805
806        <bitlbee-setting name="color_encrypted" type="boolean" scope="global">
807                <default>true</default>
808
809                <description>
810                        <para>
811                                If set to true, BitlBee will color incoming encrypted messages according to their fingerprint trust level: untrusted=red, trusted=green.
812                        </para>
813                </description>
814        </bitlbee-setting>
815
816        <bitlbee-setting name="chat_type" type="string" scope="channel">
817                <default>groupchat</default>
818                <possible-values>groupchat, room</possible-values>
819
820                <description>
821                        <para>
822                                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.
823                        </para>
824                       
825                        <para>
826                                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.
827                        </para>
828                       
829                        <para>
830                                For setting up named chatrooms, it's currently easier to just use the <emphasis>chat add</emphasis> command.
831                        </para>
832                </description>
833        </bitlbee-setting>
834
835        <bitlbee-setting name="commands" type="boolean" scope="account">
836                <default>true</default>
837                <possible-values>true, false, strict</possible-values>
838
839                <description>
840                        <para>
841                                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:
842                        </para>
843
844                        <variablelist>
845                                <varlistentry><term>undo #[&lt;id&gt;]</term><listitem><para>Delete your last Tweet (or one with the given ID)</para></listitem></varlistentry>
846                                <varlistentry><term>rt &lt;screenname|#id&gt;</term><listitem><para>Retweet someone's last Tweet (or one with the given ID)</para></listitem></varlistentry>
847                                <varlistentry><term>reply &lt;screenname|#id&gt;</term><listitem><para>Reply to a Tweet (with a reply-to reference)</para></listitem></varlistentry>
848                                <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>
849                                <varlistentry><term>follow &lt;screenname&gt;</term><listitem><para>Start following a person</para></listitem></varlistentry>
850                                <varlistentry><term>unfollow &lt;screenname&gt;</term><listitem><para>Stop following a person</para></listitem></varlistentry>
851                                <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>
852                                <varlistentry><term>post &lt;message&gt;</term><listitem><para>Post a tweet</para></listitem></varlistentry>
853                        </variablelist>
854
855                        <para>
856                                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.
857                        </para>
858                </description>
859        </bitlbee-setting>
860
861        <bitlbee-setting name="debug" type="boolean" scope="global">
862                <default>false</default>
863
864                <description>
865                        <para>
866                                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.
867                        </para>
868                       
869                        <para>
870                                This feature is not currently used for anything so don't expect this to generate any output.
871                        </para>
872                </description>
873        </bitlbee-setting>
874
875        <bitlbee-setting name="default_target" type="string" scope="global">
876                <default>root</default>
877                <possible-values>root, last</possible-values>
878
879                <description>
880                        <para>
881                                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>.
882                        </para>
883                </description>
884        </bitlbee-setting>
885
886        <bitlbee-setting name="display_name" type="string" scope="account">
887                <description>
888                        <para>
889                                Currently only available for MSN connections. This setting allows you to read and change your "friendly name" for this connection. Since this is a server-side setting, it can't be changed when the account is off-line.
890                        </para>
891                </description>
892        </bitlbee-setting>
893
894        <bitlbee-setting name="display_namechanges" type="boolean" scope="global">
895                <default>false</default>
896
897                <description>
898                        <para>
899                                With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
900                        </para>
901                </description>
902        </bitlbee-setting>
903
904        <bitlbee-setting name="display_timestamps" type="boolean" scope="global">
905                <default>true</default>
906
907                <description>
908                        <para>
909                                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.
910                        </para>
911                </description>
912        </bitlbee-setting>
913
914        <bitlbee-setting name="fill_by" type="string" scope="channel">
915                <default>all</default>
916                <possible-values>all, group, account, protocol</possible-values>
917
918                <description>
919                        <para>
920                                For control channels only: This setting determines which contacts the channel gets populated with.
921                        </para>
922
923                        <para>
924                                By default, control channels will contain all your contacts. You instead select contacts by buddy group, IM account or IM protocol.
925                        </para>
926                       
927                        <para>
928                                Change this setting and the corresponding <emphasis>account</emphasis>/<emphasis>group</emphasis>/<emphasis>protocol</emphasis> setting to set up this selection.
929                        </para>
930                       
931                        <para>
932                                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>.
933                        </para>
934                </description>
935        </bitlbee-setting>
936
937        <bitlbee-setting name="group" type="string" scope="channel">
938
939                <description>
940                        <para>
941                                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.
942                        </para>
943                </description>
944        </bitlbee-setting>
945
946        <bitlbee-setting name="handle_unknown" type="string" scope="global">
947                <default>add_channel</default>
948                <possible-values>root, add, add_private, add_channel, ignore</possible-values>
949
950                <description>
951                        <para>
952                                By default, messages from people who aren't in your contact list are shown in a control channel instead of as a private message.
953                        </para>
954
955                        <para>
956                                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.
957                        </para>
958
959                        <note>
960                                <para>
961                                        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.
962                                </para>
963                        </note>
964                </description>
965
966        </bitlbee-setting>
967
968        <bitlbee-setting name="ignore_auth_requests" type="boolean" scope="account">
969                <default>false</default>
970
971                <description>
972                        <para>
973                                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.
974                        </para>
975                </description>
976
977        </bitlbee-setting>
978
979        <bitlbee-setting name="lcnicks" type="boolean" scope="global">
980                <default>true</default>
981
982                <description>
983                        <para>
984                                Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
985                        </para>
986                </description>
987
988        </bitlbee-setting>
989
990        <bitlbee-setting name="local_display_name" type="boolean" scope="account">
991                <default>false</default>
992
993                <description>
994                        <para>
995                                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.
996                        </para>
997                </description>
998
999        </bitlbee-setting>
1000
1001        <bitlbee-setting name="mail_notifications" type="boolean" scope="account">
1002                <default>false</default>
1003
1004                <description>
1005                        <para>
1006                                Some protocols (MSN, Yahoo!) can notify via IM about new e-mail. Since most people use their Hotmail/Yahoo! addresses as a spam-box, this is disabled default. If you want these notifications, you can enable this setting.
1007                        </para>
1008                </description>
1009
1010        </bitlbee-setting>
1011
1012        <bitlbee-setting name="message_length" type="integer" scope="account">
1013                <default>140</default>
1014
1015                <description>
1016                        <para>
1017                                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.
1018                        </para>
1019
1020                        <para>
1021                                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.
1022                        </para>
1023                </description>
1024
1025        </bitlbee-setting>
1026
1027        <bitlbee-setting name="stream" type="boolean" scope="account">
1028                <default>true</default>
1029
1030                <description>
1031                        <para>
1032                                For Twitter accounts, this setting enables use of the Streaming API. This automatically gives you incoming DMs as well.
1033                        </para>
1034                       
1035                        <para>
1036                                For other Twitter-like services, this setting is not supported.
1037                        </para>
1038                </description>
1039
1040        </bitlbee-setting>
1041       
1042        <bitlbee-setting name="target_url_length" type="integer" scope="account">
1043                <default>20</default>
1044
1045                <description>
1046                        <para>
1047                                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.
1048                        </para>
1049
1050                        <para>
1051                                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).
1052                        </para>
1053                </description>
1054
1055        </bitlbee-setting>
1056
1057        <bitlbee-setting name="mode" type="string" scope="account">
1058                <possible-values>one, many, chat</possible-values>
1059                <default>chat</default>
1060
1061                <description>
1062                        <para>
1063                                By default, BitlBee will create a separate channel (called #twitter_yourusername) for all your Twitter contacts/messages.
1064                        </para>
1065
1066                        <para>
1067                                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).
1068                        </para>
1069                       
1070                        <para>
1071                                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.
1072                        </para>
1073                       
1074                        <para>
1075                                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.
1076                        </para>
1077                </description>
1078
1079        </bitlbee-setting>
1080
1081        <bitlbee-setting name="mobile_is_away" type="boolean" scope="global">
1082                <default>false</default>
1083
1084                <description>
1085                        <para>
1086                                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.
1087                        </para>
1088                </description>
1089
1090        </bitlbee-setting>
1091
1092        <bitlbee-setting name="nick" type="string" scope="chat">
1093                <description>
1094                        <para>
1095                                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.
1096                        </para>
1097                </description>
1098        </bitlbee-setting>
1099
1100        <bitlbee-setting name="nick_format" type="string" scope="account,global">
1101                <default>%-@nick</default>
1102
1103                <description>
1104                        <para>
1105                                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.
1106                        </para>
1107
1108                        <para>
1109                                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.
1110                        </para>
1111
1112                        <para>
1113                                It's easier to describe this setting using a few examples:
1114                        </para>
1115
1116                        <para>
1117                                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.
1118                        </para>
1119
1120                        <para>
1121                                [%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.
1122                        </para>
1123
1124                        <para>
1125                                See <emphasis>help nick_format</emphasis> for more information.
1126                        </para>
1127                </description>
1128        </bitlbee-setting>
1129
1130        <bitlbee-setting name="nick_source" type="string" scope="account">
1131                <default>handle</default>
1132                <possible-values>handle, full_name, first_name</possible-values>
1133
1134                <description>
1135                        <para>
1136                                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.
1137                        </para>
1138
1139                        <para>
1140                                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.
1141                        </para>
1142                </description>
1143        </bitlbee-setting>
1144
1145        <bitlbee-setting name="oauth" type="boolean" scope="account">
1146                <default>true</default>
1147
1148                <description>
1149                        <para>
1150                                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.
1151                        </para>
1152
1153                        <para>
1154                                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.
1155                        </para>
1156
1157                        <para>
1158                                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.
1159                        </para>
1160                </description>
1161
1162        </bitlbee-setting>
1163
1164        <bitlbee-setting name="ops" type="string" scope="global">
1165                <default>both</default>
1166                <possible-values>both, root, user, none</possible-values>
1167
1168                <description>
1169                        <para>
1170                                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.
1171                        </para>
1172
1173                        <para>
1174                                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.
1175                        </para>
1176                </description>
1177        </bitlbee-setting>
1178
1179        <bitlbee-setting name="otr_policy" type="string" scope="global">
1180                <default>opportunistic</default>
1181                <possible-values>never, opportunistic, manual, always</possible-values>
1182
1183                <description>
1184                        <para>
1185                                This setting controls the policy for establishing Off-the-Record connections.
1186                        </para>
1187                        <para>
1188                                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.
1189                        </para>
1190                </description>
1191        </bitlbee-setting>
1192
1193        <bitlbee-setting name="password" type="string" scope="account,global">
1194                <description>
1195                        <para>
1196                                Use this global setting to change your "NickServ" password.
1197                        </para>
1198                       
1199                        <para>
1200                                This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
1201                        </para>
1202                       
1203                        <para>
1204                                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.
1205                        </para>
1206                </description>
1207        </bitlbee-setting>
1208
1209        <bitlbee-setting name="paste_buffer" type="boolean" scope="global">
1210                <default>false</default>
1211
1212                <description>
1213                        <para>
1214                                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.
1215                        </para>
1216
1217                        <para>
1218                                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.
1219                        </para>
1220
1221                        <para>
1222                                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.
1223                        </para>
1224                </description>
1225        </bitlbee-setting>
1226
1227        <bitlbee-setting name="paste_buffer_delay" type="integer" scope="global">
1228                <default>200</default>
1229
1230                <description>
1231
1232                        <para>
1233                                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.
1234                        </para>
1235
1236                        <para>
1237                                See also the <emphasis>paste_buffer</emphasis> setting.
1238                        </para>
1239                </description>
1240        </bitlbee-setting>
1241       
1242        <bitlbee-setting name="port" type="integer" scope="account">
1243                <description>
1244                        <para>
1245                                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.
1246                        </para>
1247                </description>
1248        </bitlbee-setting>
1249
1250        <bitlbee-setting name="priority" type="integer" scope="account">
1251                <default>0</default>
1252
1253                <description>
1254                        <para>
1255                                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).
1256                        </para>
1257
1258                        <para>
1259                                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).
1260                        </para>
1261                </description>
1262        </bitlbee-setting>
1263
1264        <bitlbee-setting name="private" type="boolean" scope="global">
1265                <default>true</default>
1266
1267                <description>
1268                        <para>
1269                                If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in a control channel.
1270                        </para>
1271
1272                        <para>
1273                                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.
1274                        </para>
1275                </description>
1276        </bitlbee-setting>
1277
1278        <bitlbee-setting name="protocol" type="string" scope="channel">
1279
1280                <description>
1281                        <para>
1282                                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.
1283                        </para>
1284                </description>
1285        </bitlbee-setting>
1286
1287        <bitlbee-setting name="query_order" type="string" scope="global">
1288                <default>lifo</default>
1289                <possible-values>lifo, fifo</possible-values>
1290
1291                <description>
1292                        <para>
1293                                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.
1294                        </para>
1295
1296                        <para>
1297                                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).
1298                        </para>
1299                </description>
1300        </bitlbee-setting>
1301
1302        <bitlbee-setting name="resource" type="string" scope="account">
1303                <default>BitlBee</default>
1304
1305                <description>
1306                        <para>
1307                                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.
1308                        </para>
1309                </description>
1310        </bitlbee-setting>
1311
1312        <bitlbee-setting name="resource_select" type="string" scope="account">
1313                <default>activity</default>
1314                <possible-values>priority, activity</possible-values>
1315
1316                <description>
1317                        <para>
1318                                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.
1319                        </para>
1320
1321                        <para>
1322                                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).
1323                        </para>
1324                </description>
1325        </bitlbee-setting>
1326
1327        <bitlbee-setting name="root_nick" type="string" scope="global">
1328                <default>root</default>
1329
1330                <description>
1331                        <para>
1332                                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.
1333                        </para>
1334                </description>
1335        </bitlbee-setting>
1336
1337        <bitlbee-setting name="save_on_quit" type="boolean" scope="global">
1338                <default>true</default>
1339
1340                <description>
1341                        <para>
1342                                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.
1343                        </para>
1344                </description>
1345        </bitlbee-setting>
1346
1347        <bitlbee-setting name="server" type="string" scope="account">
1348                <description>
1349                        <para>
1350                                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.
1351                        </para>
1352                </description>
1353        </bitlbee-setting>
1354
1355        <bitlbee-setting name="show_ids" type="boolean" scope="account">
1356                <default>true</default>
1357
1358                <description>
1359                        <para>
1360                                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.
1361                        </para>
1362                </description>
1363        </bitlbee-setting>
1364
1365        <bitlbee-setting name="show_offline" type="boolean" scope="global">
1366                <default>false</default>
1367
1368                <description>
1369                        <para>
1370                                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.
1371                        </para>
1372                       
1373                        <para>
1374                                Replaced with the <emphasis>show_users</emphasis> setting. See <emphasis>help show_users</emphasis>.
1375                        </para>
1376                </description>
1377        </bitlbee-setting>
1378
1379        <bitlbee-setting name="show_users" type="string" scope="channel">
1380                <default>online+,away</default>
1381
1382                <description>
1383                        <para>
1384                                Comma-separated list of statuses of users you want in the channel,
1385                                and any modes they should have. The following statuses are currently
1386                                recognised: <emphasis>online</emphasis> (i.e. available, not
1387                                away), <emphasis>away</emphasis>, and <emphasis>offline</emphasis>.
1388                        </para>
1389                       
1390                        <para>
1391                                If a status is followed by a valid channel mode character
1392                                (@, % or +), it will be given to users with that status.
1393                                For example, <emphasis>online@,away+,offline</emphasis> will
1394                                show all users in the channel. Online people will
1395                                have +o, people who are online but away will have +v,
1396                                and others will have no special modes.
1397                        </para>
1398                </description>
1399        </bitlbee-setting>
1400
1401        <bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
1402                <default>true</default>
1403
1404                <description>
1405                        <para>
1406                                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.
1407                        </para>
1408                </description>
1409        </bitlbee-setting>
1410
1411        <bitlbee-setting name="ssl" type="boolean" scope="account">
1412                <default>false</default>
1413
1414                <description>
1415                        <para>
1416                                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).
1417                        </para>
1418
1419                        <para>
1420                                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.
1421                        </para>
1422                </description>
1423        </bitlbee-setting>
1424
1425        <bitlbee-setting name="status" type="string" scope="account,global">
1426                <description>
1427                        <para>
1428                                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.
1429                        </para>
1430
1431                        <para>
1432                                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).
1433                        </para>
1434
1435                        <para>
1436                                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>.
1437                        </para>
1438                </description>
1439        </bitlbee-setting>
1440
1441        <bitlbee-setting name="strip_html" type="boolean" scope="global">
1442                <default>true</default>
1443
1444                <description>
1445                        <para>
1446                                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.
1447                        </para>
1448                        <para>
1449                                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.
1450                        </para>
1451                </description>
1452        </bitlbee-setting>
1453
1454        <bitlbee-setting name="strip_newlines" type="boolean" scope="account">
1455                <default>false</default>
1456
1457                <description>
1458                        <para>
1459                                Turn on this flag to prevent tweets from spanning over multiple lines.
1460                        </para>
1461                </description>
1462        </bitlbee-setting>
1463
1464        <bitlbee-setting name="show_old_mentions" type="integer" scope="account">
1465                <default>20</default>
1466
1467                <description>
1468                        <para>
1469                                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.
1470                        </para>
1471                </description>
1472        </bitlbee-setting>
1473
1474        <bitlbee-setting name="switchboard_keepalives" type="boolean" scope="account">
1475                <default>false</default>
1476
1477                <description>
1478                        <para>
1479                                Turn on this flag if you have difficulties talking to offline/invisible contacts.
1480                        </para>
1481                       
1482                        <para>
1483                                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.
1484                        </para>
1485                       
1486                        <para>
1487                                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.
1488                        </para>
1489                </description>
1490        </bitlbee-setting>
1491
1492        <bitlbee-setting name="tag" type="string" scope="account">
1493                <description>
1494                        <para>
1495                                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.
1496                        </para>
1497
1498                        <para>
1499                                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.
1500                        </para>
1501                </description>
1502        </bitlbee-setting>
1503
1504        <bitlbee-setting name="timezone" type="string" scope="global">
1505                <default>local</default>
1506                <possible-values>local, utc, gmt, timezone-spec</possible-values>
1507
1508                <description>
1509                        <para>
1510                                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.
1511                        </para>
1512
1513                        <para>
1514                                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.
1515                        </para>
1516                </description>
1517        </bitlbee-setting>
1518
1519        <bitlbee-setting name="tls" type="boolean" scope="account">
1520                <default>try</default>
1521
1522                <description>
1523                        <para>
1524                                Newer Jabber servers allow clients to convert a plain-text session to a TLS/SSL-encrypted session. Normally (with this setting set to <emphasis>try</emphasis>) BitlBee will do this, if possible.
1525                        </para>
1526
1527                        <para>
1528                                If you want to force BitlBee to use TLS sessions only (and to give up if that doesn't seem to be possible) you can set this setting to <emphasis>true</emphasis>. Set it to <emphasis>false</emphasis> if you want the session to remain plain-text.
1529                        </para>
1530                </description>
1531        </bitlbee-setting>
1532
1533        <bitlbee-setting name="tls_verify" type="boolean" scope="account">
1534                <default>true</default>
1535
1536                <description>
1537                        <para>
1538                                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.
1539                        </para>
1540
1541                        <para>
1542                                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.
1543                        </para>
1544
1545                        <para>
1546                                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.
1547                        </para>
1548                </description>
1549        </bitlbee-setting>
1550
1551        <bitlbee-setting name="to_char" type="string" scope="global">
1552                <default>": "</default>
1553
1554                <description>
1555                        <para>
1556                                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>.
1557                        </para>
1558
1559                        <para>
1560                                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.
1561                        </para>
1562                </description>
1563        </bitlbee-setting>
1564
1565        <bitlbee-setting name="translate_to_nicks" type="boolean" scope="channel">
1566                <default>true</default>
1567
1568                <description>
1569                        <para>
1570                                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.
1571                        </para>
1572
1573                        <para>
1574                                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.
1575                        </para>
1576                </description>
1577        </bitlbee-setting>
1578
1579        <bitlbee-setting name="type" type="string" scope="channel">
1580                <default>control</default>
1581                <possible-values>control, chat</possible-values>
1582
1583                <description>
1584                        <para>
1585                                BitlBee supports two kinds of channels: control channels (usually with a name starting with a &amp;) and chatroom channels (name usually starts with a #).
1586                        </para>
1587
1588                        <para>
1589                                See <emphasis>help channels</emphasis> for a full description of channel types in BitlBee.
1590                        </para>
1591                </description>
1592        </bitlbee-setting>
1593
1594        <bitlbee-setting name="typing_notice" type="boolean" scope="global">
1595                <default>false</default>
1596
1597                <description>
1598                        <para>
1599                                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.
1600                        </para>
1601                </description>
1602        </bitlbee-setting>
1603
1604        <bitlbee-setting name="user_agent" type="string" scope="account">
1605                <default>BitlBee</default>
1606
1607                <description>
1608                        <para>
1609                                Some Jabber servers are configured to only allow a few (or even just one) kinds of XMPP clients to connect to them.
1610                        </para>
1611                       
1612                        <para>
1613                                You can change this setting to make BitlBee present itself as a different client, so that you can still connect to these servers.
1614                        </para>
1615                </description>
1616        </bitlbee-setting>
1617
1618        <bitlbee-setting name="web_aware" type="string" scope="account">
1619                <default>false</default>
1620
1621                <description>
1622                        <para>
1623                                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.
1624                        </para>
1625
1626                        <para>
1627                                Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
1628                        </para>
1629                </description>
1630        </bitlbee-setting>
1631
1632        <bitlbee-setting name="xmlconsole" type="boolean" scope="account">
1633                <default>false</default>
1634
1635                <description>
1636                        <para>
1637                                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.
1638                        </para>
1639                        <para>
1640                                If you want to enable this XML console permanently (and at login time already), you can set this setting.
1641                        </para>
1642                </description>
1643        </bitlbee-setting>
1644
1645        <bitlbee-command name="rename">
1646                <short-description>Rename (renick) a buddy</short-description>
1647                <syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
1648                <syntax>rename -del &lt;oldnick&gt;</syntax>
1649
1650                <description>
1651                        <para>
1652                                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).
1653                        </para>
1654                       
1655                        <para>
1656                                <emphasis>rename -del</emphasis> can be used to erase your manually set nickname for a contact and reset it to what was automatically generated.
1657                        </para>
1658                </description>
1659
1660                <ircexample>
1661                        <ircline nick="itsme">rename itsme_ you</ircline>
1662                        <ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
1663                </ircexample>
1664
1665        </bitlbee-command>
1666
1667        <bitlbee-command name="yes">
1668                <short-description>Accept a request</short-description>
1669                <syntax>yes [&lt;number&gt;]</syntax>
1670
1671                <description>
1672                        <para>
1673                                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.
1674                        </para>
1675
1676                        <para>
1677                                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.
1678                        </para>
1679                </description>
1680
1681        </bitlbee-command>
1682
1683        <bitlbee-command name="no">
1684                <short-description>Deny a request</short-description>
1685                <syntax>no [&lt;number&gt;]</syntax>
1686
1687                <description>
1688                        <para>
1689                                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.
1690                        </para>
1691
1692                        <para>
1693                                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.
1694                        </para>
1695                </description>
1696        </bitlbee-command>
1697
1698        <bitlbee-command name="qlist">
1699                <short-description>List all the unanswered questions root asked</short-description>
1700                <syntax>qlist</syntax>
1701
1702                <description>
1703                        <para>
1704                                This gives you a list of all the unanswered questions from root.
1705                        </para>
1706                </description>
1707
1708        </bitlbee-command>
1709
1710        <bitlbee-command name="register">
1711                <short-description>Register yourself</short-description>
1712                <syntax>register [&lt;password&gt;]</syntax>
1713
1714                <description>
1715                        <para>
1716                                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.
1717                        </para>
1718
1719                        <para>
1720                                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.. ;-)
1721                        </para>
1722
1723                        <para>
1724                                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.
1725                        </para>
1726
1727                        <para>
1728                                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.
1729                        </para>
1730                </description>
1731
1732        </bitlbee-command>
1733
1734        <bitlbee-command name="identify">
1735                <syntax>identify [-noload|-force] [&lt;password&gt;]</syntax>
1736                <short-description>Identify yourself with your password</short-description>
1737
1738                <description>
1739                        <para>
1740                                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.
1741                        </para>
1742
1743                        <para>
1744                                Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
1745                        </para>
1746
1747                        <para>
1748                                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).
1749                        </para>
1750                       
1751                        <para>
1752                                <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).
1753                        </para>
1754
1755                        <para>
1756                                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.
1757                        </para>
1758                </description>
1759        </bitlbee-command>
1760
1761        <bitlbee-command name="drop">
1762                <syntax>drop &lt;password&gt;</syntax>
1763                <short-description>Drop your account</short-description>
1764
1765                <description>
1766                        <para>
1767                                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.
1768                        </para>
1769                </description>
1770        </bitlbee-command>
1771
1772        <bitlbee-command name="blist">
1773                <syntax>blist [all|online|offline|away]</syntax>
1774                <short-description>List all the buddies in the current channel</short-description>
1775
1776                <description>
1777                        <para>
1778                                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.
1779                        </para>
1780                </description>
1781
1782        </bitlbee-command>
1783
1784        <bitlbee-command name="group">
1785                <short-description>Contact group management</short-description>
1786                <syntax>group list</syntax>
1787
1788                <description>
1789                        <para>
1790                                Only the <emphasis>group list</emphasis> command is supported at the moment, which shows a list of all groups defined so far.
1791                        </para>
1792                       
1793                        <para>
1794                                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.
1795                        </para>
1796                </description>
1797        </bitlbee-command>
1798       
1799        <bitlbee-command name="transfer">
1800                <short-description>Monitor, cancel, or reject file transfers</short-description>
1801                <syntax>transfer [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
1802               
1803                <description>
1804                        <para>
1805                                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.
1806                        </para>
1807
1808                        <ircexample>
1809                                <ircline nick="ulim">transfer</ircline>
1810                        </ircexample>
1811                </description>
1812               
1813                <bitlbee-command name="cancel">
1814                        <short-description>Cancels the file transfer with the given id</short-description>
1815                        <syntax>transfer &lt;cancel&gt; id</syntax>
1816
1817                        <description>
1818                                <para>Cancels the file transfer with the given id</para>
1819                        </description>
1820
1821                        <ircexample>
1822                                <ircline nick="ulim">transfer cancel 1</ircline>
1823                                <ircline nick="root">Canceling file transfer for test</ircline>
1824                        </ircexample>
1825                </bitlbee-command>
1826
1827                <bitlbee-command name="reject">
1828                        <short-description>Rejects all incoming transfers</short-description>
1829                        <syntax>transfer &lt;reject&gt;</syntax>
1830
1831                        <description>
1832                                <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
1833                        </description>
1834
1835                        <ircexample>
1836                                <ircline nick="ulim">transfer reject</ircline>
1837                        </ircexample>
1838                </bitlbee-command>
1839        </bitlbee-command>
1840       
1841</chapter>
Note: See TracBrowser for help on using the repository browser.