Ignore:
Timestamp:
2005-11-21T11:53:48Z (16 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
34c0e90, 513a323
Parents:
57db63b
Message:

Changed all documentation references to the control channel from #bitlbee to &bitlbee.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/user-guide/Usage.xml

    r57db63b r689a6e0  
    1414
    1515<sect1>
    16 <title>The #bitlbee control channel</title>
     16<title>The &amp;bitlbee control channel</title>
    1717
    1818<para>
    1919Once 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
     20to &amp;bitlbee on that server. This channel acts like the 'buddy list' you have
    2121on the various other chat networks.
    2222</para>
    2323
    2424<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.
     25The user 'root' always hangs around in &amp;bitlbee and acts as your interface
     26to bitlbee. All commands you give on &amp;bitlbee are 'answered' by root.
     27</para>
     28
     29<para>
     30You might be slightly confused by the &amp; in the channel name. This is,
     31however, completely allowed by the IRC standards. Just try it on a regular
     32IRC server, it should work. The difference between the standard #channels
     33and &amp;channels is that the #channels are distributed over all the servers
     34on the IRC network, while &amp;channels are local to one server. Because
     35the BitlBee control channel is local to one server (and in fact, to one person),
     36this name seems more suitable. Also, with this name, it's harder to confuse
     37the control channel with the #bitlbee channel on OFTC.
    2738</para>
    2839
Note: See TracChangeset for help on using the changeset viewer.