home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BLUDNET.ZIP
/
BLUDNET.DOC
< prev
next >
Wrap
Text File
|
1997-07-04
|
6KB
|
135 lines
Blⁿdnet Guidelines
and
Policies
I Joining Blⁿdnet
To join Bluegate, you should have been running your board for a minimum
of 1 to 3 months and have an established base of users. Your BBS Should be up
for at least 12 Consecutive hours a day. Unregistered Sysop's are allowed on
the network, and will not be hassled to register. This does not mean that we
promote not Registering/Supporting WWIV Software, it just means that if you
are grown-up enough to run the software you run, then you are old enough to
pay.
Qualifying Sysops must send the following information to their local Area
Coordinator to have their BBS included in the network. All of the information
is necessary. Omissions will delay the processing of the network update.
1. The name of the BBS.
2. The phone number of the BBS.
3. The maximum supported baud rate of the BBS.
4. The brand or type of modem used by the BBS.
5. Hours of operation.
6. How long the BBS has been in operation.
7. Number of active users.
8. Your WWIV registration number (optional)
9. SysOp's real name (and handle, if applicable).
10. SysOp's voice phone number.
11. SysOp's mailing address.
12. SysOp's birthdate
If you provide your WWIV registration number, please also let me know if
you would like it displayed in your BBSLIST entry.
If there is a system currently in the network that you would like to
connect with, please include that information. Wherever possible,
I will honor your request. Otherwise, I will assign your connection to a
board as local as is practical. @1 will NOT make more than ONE callout a
month except for first time connects. Additionally, it would probably help
to tell the Area Coordinator a little about the board's theme or major
interest areas and kinds of systems supported, etc.
II Additional Requirements
Each new SysOp will receive a copy of the Blⁿdnet Guidelines. This document
governs the operation of the network as a whole and outlines the network
responsibilities of SysOps, Area Coordinators and Group Coordinators. It is
expected that new SysOps joining Blⁿdnet will have read and understood the
guidelines and will abide by the laws and regulations governing
telecommunications networks.
Given that a sysop is responsible for what happens on his board, a sysop
in the network must keep control over thier users in their usage of the
net. This is not meant to tell others sysops how to run their board, but
that we must all cooperate in order to ensure the flow of 'meaningful'
communication throughout the network.
I would suggest that all sysops who carry networked subs post a notice
(preferably in their G-files) informing their users of what is generally
OK for posts going out over the network. Then, if a user violates the
rule, he/she MAY be subject to censure from the network - POSSIBLY even
denied future access to the board.
III New nodes are requested to wait 1-3 weeks before attempting to
host networked subboards. Sub types recommended are in the form xNNNN,
where NNNN is the last four digits of the host node number and the x is
a consecutive number from 1 to 9 indicating the number of the sub hosted
by that system. Example: the first sub hosted by 19900 would be 19900,
the next one would be 29900 and so on. Hosted subs are to be reported to
the SubsList Coordinator (Currently @1).
IV All connections will be handled by the Area Coordinator.
Requests should be sent via email, and should clearly show the requested
connection(s). In addition, if the request is to add a connect to
another system in another area code, then both systems must request it before
it will be added. There are no exceptions to this. Under *no circumstances*
should a system edit their own data files, UNLESS SPECIFICALLY DIRECTED TO BY
THE AREA COORDINATOR.
A new board will only be given one connect, and where practical, such
connect will be a local call. Additional connections will only be
considered after 3 months participation in the network.
V Network nodes are expected to keep their BBSes in the
network for a minimum of 2 months. If a net node goes down before
that time, that node may not rejoin the network for 6 months.
VI SysOps taking their BBS down for longer than 48 hours are
required to notify the Area Coordinator and the systems to which they
are directly connected.
VII SysOps taking their BBS down permanently are required give at
least two weeks notice to the Area Coordinator and to notify the hosts
of any networked subs they carry.
VIII No illegal activities. If network traffic is found containing
material in violation of ECPA and FCC statutes, the originating system
will be removed from the network and authorities will be notified
immediately.
IX ALL disputes regarding the network will be mediated by the Local
Area Coordinator. Systems that explore this alternative and cannot
reach agreement may be referred to the Network Coordinator to resolve the
problem at the Area Coordinator's discretion. Any Sysop who enlists
others in their difficulties without the consent of the Area Coordinator
will be subject to immediate removal from the network.
X AC/GC/NC
If your area does not have an AC the GC is the acting AC.
If your area does not have an AC or GC the NC is the acting AC and GC
An AC can be appointed only when there are at least 3 boards in one area
code. If there are at least 10 boards in 3 area codes that are close to
each other than a GC may be appointed.
XI Problems with the net
If there are ANY problems with the network please contact the NC in some
way shape or form.
Kinglizard
sysop of The Lizard Den
BLⁿDNET
WWIVNET
TERRANET
ICENET
WWIVLINK