Changeset cfcc587 for doc/user-guide/Usage.xml
- Timestamp:
- 2005-11-28T01:14:35Z (18 years ago)
- Branches:
- master
- Children:
- ed165fe
- Parents:
- cf13671 (diff), b20b32f (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/Usage.xml
rcf13671 rcfcc587 14 14 15 15 <sect1> 16 <title>The #bitlbee control channel</title>16 <title>The &bitlbee control channel</title> 17 17 18 18 <para> 19 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 have20 to &bitlbee on that server. This channel acts like the 'buddy list' you have 21 21 on the various other chat networks. 22 22 </para> 23 23 24 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. 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. 27 38 </para> 28 39
Note: See TracChangeset
for help on using the changeset viewer.