1 | <chapter id="Usage"> |
---|
2 | |
---|
3 | <title>Usage</title> |
---|
4 | |
---|
5 | <sect1> |
---|
6 | <title>Connecting to the server</title> |
---|
7 | <para> |
---|
8 | Since BitlBee acts just like any other irc daemon, you can connect to |
---|
9 | it with your favorite irc client. Launch it and connect to localhost port 6667 |
---|
10 | (or whatever host/port you are running bitlbee on). |
---|
11 | </para> |
---|
12 | |
---|
13 | </sect1> |
---|
14 | |
---|
15 | <sect1> |
---|
16 | <title>The &bitlbee control channel</title> |
---|
17 | |
---|
18 | <para> |
---|
19 | Once you are connected to the BitlBee server, you are automatically joined |
---|
20 | to &bitlbee on that server. This channel acts like the 'buddy list' you have |
---|
21 | on the various other chat networks. |
---|
22 | </para> |
---|
23 | |
---|
24 | <para> |
---|
25 | The user 'root' always hangs around in &bitlbee and acts as your interface |
---|
26 | to bitlbee. All commands you give on &bitlbee are 'answered' by root. |
---|
27 | </para> |
---|
28 | |
---|
29 | <para> |
---|
30 | You might be slightly confused by the & in the channel name. This is, |
---|
31 | however, completely allowed by the IRC standards. Just try it on a regular |
---|
32 | IRC server, it should work. The difference between the standard #channels |
---|
33 | and &channels is that the #channels are distributed over all the servers |
---|
34 | on the IRC network, while &channels are local to one server. Because |
---|
35 | the BitlBee control channel is local to one server (and in fact, to one person), |
---|
36 | this name seems more suitable. Also, with this name, it's harder to confuse |
---|
37 | the control channel with the #bitlbee channel on OFTC. |
---|
38 | </para> |
---|
39 | |
---|
40 | </sect1> |
---|
41 | |
---|
42 | <sect1> |
---|
43 | <title>Talking to people</title> |
---|
44 | |
---|
45 | <para> |
---|
46 | You can talk to by starting a query with them. In most irc clients, |
---|
47 | this can be done with either <command>/msg <nick> <text></command> |
---|
48 | or <command>/query <nick></command>. |
---|
49 | </para> |
---|
50 | |
---|
51 | <para> |
---|
52 | To keep the number of open query windows limited, you can also talk to people |
---|
53 | in the control channel, like <command><nick>: <text></command>. |
---|
54 | </para> |
---|
55 | |
---|
56 | </sect1> |
---|
57 | |
---|
58 | </chapter> |
---|