+ FIXME It's fun. Try it.
+<hr width="100%" size="2">
+<center>
+<h2><a name="Building_or_joining_a_Citadel_network"></a>Building or joining
+a Citadel network</h2>
+</center>
+
+<h3><a name="Overview__"></a>Overview</h3>
+
+<p>If you are running Citadel as a BBS or other forum type of application,
+one way to 'keep the conversation going' is to share rooms with other Citadel
+systems. In a shared room, a message posted to the room is automatically
+propagated to every system on the network. It's kind of like a UseNet newsgroup,
+but without the spam.</p>
+
+<p>If you are using Citadel as the e-mail and groupware platform for a large
+organization, you can use its networking features to build a large network
+of Citadel servers which share content (think of rooms as public folders),
+redistribute e-mail throughout the organization, and integrate the global
+address book. It might make sense, for example, in a large corporation
+to give each department or location its own Citadel server. Thanks
+to Citadel's global address book features, you could still have all of the
+users share a single e-mail domain.</p>
+
+<p>Obviously, the first thing you have to do is find another Citadel to share
+rooms with, and make arrangements with them. The following Citadels are
+a good place to start:</p>
+
+<ul>
+ <li>UNCENSORED! - <a href="http://uncensored.citadel.org">uncensored.citadel.org</a>
+ </li>
+ <li>The Dog Pound II - <a href="http://dogpound2.citadel.org">dogpound2.citadel.org</a>
+ </li>
+ <li>PixelBBS - <a href="http://pixel.citadel.org">pixel.citadel.org</a>
+ </li>
+</ul>
+
+<p>You don't have to be a part of the citadel.org domain to participate in
+the public Citadel network, but the DNS service is provided free of charge
+by the Citadel community if you wish to do this.</p>
+
+<h3><a name="Conventions_and_etiquette_when"></a>Conventions and etiquette
+when connecting to the public Citadel network</h3>
+
+<p>Before we get into the technical nitty gritty, there are two points of
+etiquette to keep in mind. The first thing to keep in mind is that the operator
+of any particular Citadel may not be willing to share some of his/her rooms.
+ Some sites are proud to offer exclusive content in certain areas. Chances
+are, if a room is already being shared on the network, it's available for
+anyone to share; if not, it can't hurt to ask -- but take care not to demand
+it of them. Ask if you may share the room instead of telling them that you
+wish to share the room. When looking at a <tt><b>K</b></tt>nown rooms list,
+network rooms are the ones ending in parentheses instead of angle brackets.
+ For example, <tt>Gateway)</tt> would be a network room, <tt>Lobby></tt>
+would not.</p>
+
+<p>The other point of etiquette to remember is that you should be making
+the arrangements in advance, and then set it up. It is extremely rude to
+simply begin networking with another Citadel, or unilaterally start sharing
+a new room, without first obtaining permission from its operator. Always
+ask first. Most Citadel operators are more than happy to network with you.
+ Also, if later on you decide to take your system down, please take the time
+to notify the operators of any other Citadels you network with, so they can
+unconfigure their end.</p>
+
+<h3><a name="Getting_ready_to_join_the_network"></a>Getting ready to join
+the network</h3>
+
+<p>Ok, first things first. On a Citadel room sharing network, the first
+thing you need to know is your own system's node name. Presumably you set
+this up during installation, but if you want to change it you can do so using
+the <tt><b>.A</b>ide <b>S</b>ysconfig <b>G</b>eneral</tt> command:</p>
+
+<pre>Lobby> . Aide System configuration General<br>Node name [uncnsrd]:<br>Fully qualified domain name [uncensored.citadel.org]:<br>Human readable node name [Uncensored]:<br></pre>
+
+<p>The "node name" is important, it's how the network identifies messages
+coming from your system. The "human readable node name" is simply a label;
+it shows up in messages coming from your system. "Fully qualified domain
+name" is your DNS name; it's used for routing messages on the Internet. In
+the above example, the node name is "uncnsrd".</p>
+
+<h3><a name="Defining_neighbor_nodes"></a>Defining neighbor nodes</h3>
+
+<p>The next thing you need to do is configure your neighbor node(s). You
+need to do this for each node you network with. Let's say you wanted to
+talk to a Citadel system called "frobozz". Use the <tt><b>.A</b>ide <b>S</b>ysconfig
+<b>N</b>etwork</tt> command:</p>
+
+<pre>Lobby> . Aide System configuration Network<br>### Node Secret Host or IP Port#<br>--- ---------------- ---------------- -------------------------------- -----<br><A>dd <D>elete <S>ave <Q>uit -> Add<br><br>Enter node name : frobozz<br>Enter shared secret: frotz<br>Enter host or IP : frobozz.magick.org<br>Enter port number : [504]: 504<br><br>### Node Secret Host or IP Port#<br>--- ---------------- ---------------- -------------------------------- -----<br> 1 frobozz frotz frobozz.magick.org 504<br><A>dd <D>elete <S>ave <Q>uit -> Save<br><br>Lobby><br></pre>
+
+<p>As you can see in the above example, you have to enter the Citadel node
+name, the DNS name or IP address of the server, and the port number the Citadel
+service is running on. The "shared secret" is a password to allow the two
+Citadel nodes to connect to each other to exchange network data. The password
+must be <i>identical</i> on both ends of the connection -- when the operator
+of the other Citadel node sets up the connection with your system, he/she
+must use the same password.</p>
+
+<h3><a name="Sharing_rooms"></a>Sharing rooms</h3>
+
+<p>Now you're ready to share rooms. You have to do this for each room you
+want to share, and you have to do it from BOTH ENDS -- again, when you share
+a room with another Citadel, they must share it with you as well. Let's
+say you have a room called "Quiche Recipes>" and you want to share it
+with the node you set up above. First, edit the room and flag it as a network
+room:</p>
+
+<pre>Quiche Recipes> . Aide Edit this room<br>Room name [Quiche Recipes]:<br>Private room [No]: No<br>Preferred users only [No]: No<br>Read-only room [No]: No<br>Directory room [No]: No<br>Permanent room [No]: No<br>Network shared room [No]: Yes<br>Automatically make all messages anonymous [No]: No<br>Ask users whether to make messages anonymous [No]: No<br>Listing order [64]:<br>Room aide (or 'none') [none]:<br>Message expire policy (? for list) [0]:<br>Save changes (y/n)? Yes<br>Ok<br><br>Quiche Recipes)<br></pre>
+
+<p>Notice how the prompt changed? It was > before, but it's ) now. That
+means it's a network room. Now you can tell Citadel that you want to share
+the room with frobozz. Enter this command:</p>
+
+<pre>Quiche Recipes) . Aide Network room sharing<br></pre>
+
+<p>Your text editor will pop up (you <i>did</i> configure Citadel to use
+your favorite text editor, right?) with a screen that looks like this:</p>
+
+<pre># Configuration for room: Quiche Recipes<br># Nodes with which we share this room<br># Specify one per line.<br></pre>
+
+<p>All you have to do is enter the name of the other Citadel node (i.e. "frobozz"
+in our example) on a line by itself. As usual, lines starting with a "#"
+are comments. Just go to the end of the file, type "frobozz" (without the
+quotes), save the file... and you're done!</p>
+
+<p>At this point, you just sit back and enjoy. Your Citadel and the other
+one will begin polling each other at regular intervals (once per hour by
+default) and sharing messages.</p>
+
+<h3><a name="Sending_mail"></a>Sending mail</h3>
+
+<p>You can send mail to any user on any node of your Citadel network. It
+may take a little while for your system to learn the entire node list, though,
+as this is done by watching incoming messages on the network and learning
+which nodes are out there.</p>
+
+<p>To send a private message, just enter <tt>user @ host</tt> as the recipient:</p>
+
+<pre>Mail> Enter message <br>Enter recipient: Some other user @ frobozz<br> Feb 11 2003 11:36pm from I. M. Me to Some other user @ frobozz<br>type message here...<br><br>Entry command (? for options) -><br></pre>
+
+<h3><a name="Changing_the_polling_interval"></a>Changing the polling interval</h3>
+
+<p>As previously mentioned, Citadel will poll other Citadel nodes for messages
+once per hour. If this is not an acceptable interval, you can change it using
+the <tt><b>.A</b>ide <b>S</b>ystem configuration <b>G</b>eneral</tt> command.
+ Enter this command and look for the option:</p>
+
+<pre>How often to run network jobs (in seconds) [3600]:<br></pre>
+
+<p>Change it to whatever you like. For example, 15 minutes is 900 seconds.
+ So if you changed the default value to 900, network polling would occur
+every 15 minutes.</p>
+
+<hr> </div>
+ <br>