From 689a6e0b8f91eecfc3add9dae769bfcda5a35b77 Mon Sep 17 00:00:00 2001 From: Wilmer van der Gaast Date: Mon, 21 Nov 2005 12:53:48 +0100 Subject: Changed all documentation references to the control channel from #bitlbee to &bitlbee. --- doc/user-guide/Usage.xml | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) (limited to 'doc/user-guide/Usage.xml') diff --git a/doc/user-guide/Usage.xml b/doc/user-guide/Usage.xml index 5d87e32b..167a74e0 100644 --- a/doc/user-guide/Usage.xml +++ b/doc/user-guide/Usage.xml @@ -13,17 +13,28 @@ it with your favorite irc client. Launch it and connect to localhost port 6667 -The #bitlbee control channel +The &bitlbee control channel Once you are connected to the BitlBee server, you are automatically joined -to #bitlbee on that server. This channel acts like the 'buddy list' you have +to &bitlbee on that server. This channel acts like the 'buddy list' you have on the various other chat networks. -The user 'root' always hangs around in #bitlbee and acts as your interface -to bitlbee. All commands you give on #bitlbee are 'answered' by root. +The user 'root' always hangs around in &bitlbee and acts as your interface +to bitlbee. All commands you give on &bitlbee are 'answered' by root. + + + +You might be slightly confused by the & in the channel name. This is, +however, completely allowed by the IRC standards. Just try it on a regular +IRC server, it should work. The difference between the standard #channels +and &channels is that the #channels are distributed over all the servers +on the IRC network, while &channels are local to one server. Because +the BitlBee control channel is local to one server (and in fact, to one person), +this name seems more suitable. Also, with this name, it's harder to confuse +the control channel with the #bitlbee channel on OFTC. -- cgit v1.2.3