Getting Familiar With Networks
by Sandra Greenwood
AuthorsNet[tm] Administrator 1:110/700
Copyright 1994; All Rights Reserved!

Part I   - Picking Up A Network

Browsing through echoes like Othernets, you are bound to come 
across networks that might be fitting for your BBS theme. There 
are some things you might want to consider before committing your 
time, your phone bill, and likewise the administrators' time and 
effort that is required to get your system set up.

Techniques that can save you time & disappointment:

- Call the network administrators' board and see if you like the
  feel of the network, the quantity of messages, the quality of
  the networks content and/or the attitudes of the participants.
  You may wish to leave the administrator a private local 
  message, stating your interest in their net, so that 
  appropriate access can be granted. The reply you receive 
  should give you a feel for how the network administrator 
  operates.

- If the network appears suitable, begin the application process.
  When you return the application, let the administrator know 
  what YOU expect/need out of your joint relationship. This 
  gives the administrator the chance to let you know if their 
  net will adjust to fit your particular needs, or cannot/will 
  not fulfill your requirements. If you are a novice at networks, 
  don't hesitate to let the administrator know. This can save 
  both time and grief during your learning process.

- Give the new network time to take hold on your system. Many
  systems bring in a new network and don't give their callers a
  chance to get involved. If you as the SysOp aren't 
  particularly interested in the network (for your own use) and 
  don't plan to give it at least a 6 month trial period, don't 
  bother setting it up. It's just not worth the hassle, on 
  either end, to set up a network/system only to have the system 
  quit after a couple weeks.

- When you setup a new network on your system, make sure your
  callers can tell what the conference topics are. You might 
  also want to check your short names in the QWK mail door so 
  that they don't all look similar. (This can happen if you put 
  the network name before the topic, as some programs only give 
  10 spaces for the area description tag.)

- Be responsible when giving echo access to your callers. If you
  have a troublesome caller, don't inflict them on a network.
  Remember most network administrators reserve the right to pull
  your feed if you cannot/will not take responsibility for your
  caller's behavior.

- Most networks are of a volunteer nature and the only cost to 
  you will be the long distance phone bill and the time you 
  spend setting it up. Your monthly cost will depend on the 
  number of conferences you carry, and the quantity of traffic. 
  Be prepared to spend at least $5 per month for each long 
  distance network you carry.


Part II  - Participating In A Network

The SysOps that poll for the nets are usually the first ones 
from their systems to participate. To avoid early misunder-
standings care must be taken during the introduction period. 
Most networks have a general message type area appropriate 
for introductions, so it's not necessary to announce your 
boards participation in each and every conference. To stay 
out of trouble in some nets, you may want to make your 
introduction post read like a "look we're here" post, rather 
than an ad for your bulletin board.

Here are some basic guidelines that will make for a better 
network experience:

- Make sure all participants know the differences between 
  echoed network conferences and local conferences.

~ Local -- originated and often hosted by the system they 
  appear on. May or may not allow private e-mail. May or may 
  not be topic specific. May allow ANSI or High ASCII graphics. 
  Ask your SysOp for details.

~ Local Echo - usually shared conferences between local boards
  within the same city and/or calling area, *see also network
  echo.

~ Network Echo - shared conferences between boards all over the
  country and/or world. *Almost never allow private e-mail in 
  the echoes, or ANSI/High ASCII graphics. Most are topic 
  specific and are likely to have a host or moderator 
  responsible for each separate conference within the given 
  network.

- Before you post in an echo, look for the rules. If you can't
  find the rules post, ask the host/moderator for further
  instructions.

- Don't reply to obvious off-topic posts, even if others seem 
  to be doing so. Most moderators will try to handle the 
  situation privately, so don't add to the problem by thinking 
  nothing is being done.

- Turn off your caps-lock key as you will be chastised for 
  shouting, if you don't.

- Resist the urge to jump in as a newcomer and tell participants
  how they are doing everything wrong. Each network/echo has its 
  own flavour and you won't score any points by comparing it to 
  other echoes and/or networks. If you don't like what you see, 
  hit the enter key, or change networks.

- Let the host/moderator do their job.
~ A conference host is usually setup to help new echo dwellers
  feel welcome and answer questions.
~ A moderator, on the other hand, functions more like a 
  conference cop. If someone enters an off-topic post or 
  breaks other rules, it is the moderators' job to inform 
  the participant of the infraction, and it's highly frowned 
  upon for other participants to intercede or publicly argue 
  with decisions passed down by a moderator.

- Agreeing to disagree -- There will be times when something 
  another participant says hits a sore spot with you. The 
  first thing you may want to consider is whether your 
  comment/opinion is on-topic, and second if your 
  contribution will lead to constructive debate. 
~ Flames (insults) are not welcome in most echoes, while 
  meaningful debate is sometimes allowed. If you're having 
  a bad hair day, hit the enter key, or save your comment 
  for a time when you are more in control.
~ With the absence of facial expressions, tone of voice, etc.,
  it is often hard to discern exactly the point a participant 
  is trying to make. To keep yourself away from this problem,
  proof-read your posts, before sending, for anything you 
  might have included that would be likely to be interpreted 
  in another way.
~ If you see a dual meaning in a post, ask for clarification,
  before you comment.

- Above all, participate. A network can only be as good as the
  information shared by the people who participate in it.


Part III - Starting Your Own Net

There are over 300 alternative networks with new ones popping up
every week. Before you start your own network, you might want to 
look and see if there is already one that offers what you are 
trying to accomplish. If there is nothing currently available, 
here are some thoughts you may wish to consider:

- First you need to ask yourself whether you have what it
  takes to become a successful network administrator.
  Ask yourself the following questions:

~ Do I have the skill, time and financial capabilities to run a
  network?  If you answer NO to any of the following questions,
  you may want to reconsider running your own network.

* skill - Can I successfully operate the required software?
* time  - Can I setup nodes quickly and efficiently?
  Do I have the time to keep the conferences in motion
  until the network becomes well established?
* financial - Can I afford to keep the host system
  running for an extended period of time? (Replace
  crashed hard drives, faulty modems, etc.)

~ Do I have the personality traits needed to run a network?
  If you answer NO to any of the following questions, you're
  likely to be in for a rough time.

* I work well in a tier structured group environment?
* I am an extrovert and work well with people?
* I can keep my own opinions from clouding my judgement, where
  the network as a whole might be concerned?
* I have an even temper, or can hold it well?
* I have an interest in the networks subject matter?
* I love to work hard for little or no personal gain?

~ Now that you've had time to consider what you are getting 
  into, are you ready to accomplish the following: (If you 
  answer YES to all of the questions below, you're on your way!)

* I have a theme for my network in mind?

* I have a name for my network that is not in use by another
  network? (see NETSALL.ART for names and Zone numbers.)

* I have made my decision about my network's Zone number?
- Some nets use the FidoNet zone numbers and nodelist. If you
  do, be sure not to duplicate any area tags that are used by
  FidoNet. You'll have to be a member of FidoNet to do this.
- If you decide on an alternative zone number, try to find
  one that is not in use as duplication makes it impossible
  for a single system to compile two different nodelists
  using the same zone number. Remember, your net won't be the
  only one out there!

* I know how to make my nodelist, or have support people that
  will perform this function for the network?

* I have decided on the structure for my network?
- A successful tier structure should look more like a
  cone, rather than a T. Check your software's (mailer)
  documentation for more information on the correct
  procedures/formats for viable network structures.

* I have decided on the backbone conferences for my network?
- One common mistake I've seen with new networks is that
  they have too many conferences, with little or no support.
  Your best bet would be to start out with no more than 10
  conferences, then let the systems that take part in your
  net suggest new conference topics as needed.

* I have composed my conference rules and any seed messages
  required to get my network started?
- If you are taking local conferences and planing to make
  them part of your network, be sure to let those
  participants know as they may not want their posts
  available on other systems. This will also give everyone
  time to remove any private messages they do not want made
  public.

* I have created my network information package?
- This should include any rules/instructions, the network
  application, the area tag names, how to turn areas on,
  area descriptions, and the nodelist, if necessary.
- You may want to look at several packages from other
  successful networks. If you plan to use anything you find
  in them, get permission from the copyright holder(s).

* I have secured a means of advertising my network and have
  made this file available to other systems?

A successful network won't happen overnight, but if you put the 
time and effort into making your network something others will 
want to take part in, the duties of a network administrator can 
be a rewarding experience.

