home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR21
/
IN_9401.ZIP
/
NETRULES.IN
< prev
next >
Wrap
Text File
|
1994-01-01
|
15KB
|
223 lines
┌────┐ ┌──▄─┐ ┌────┐ ┌────┐ ┌──▄▄▄ ┌────┐ ┌────┐
██ ██ │ █ │ ██ ██ │ ▀██ │ ███ │ ▀██ │ ███
██ ██ │ █ │ ██ ██ │ ███ │ ███ │ ███ │ ███
└────┘ └─▀──┘ ▀▀──▀▀ └────┘ └────┘ └────┘ └────┘
Intelec International E-Mail Network
Rules of Operation/Participation
Copyright (c) 1994 Intelec Business Network, Inc
Release v4.01 01-01-94
Valid through 02-28-94 (28-02-94)
While it is not the intent of the Administration to interfere with any SysOp's
authority on their own BBS, all Intelec Network participants must abide by all
present and/or future network rules. These network rules are *fully* enforced.
┌───────────────┐
│ General Rules │
└───────────────┘
Illegal activities of any kind are not tolerated, violators can be prosecuted.
Network issues must be discussed in the appropriate Administrative conference.
Political and religious posts must be made within the appropriate conference.
BBS-Software-specific macros are not permitted for use within Intelec Network.
"Obvious" aliases are prohibited from use in all Intelec Network conferences.
Quote size is limited to only what is necessary for proper "train of thought".
Elaborate "box-quoting" utilities are banned from use in the Intelec Network.
Posts may NOT be made available to users currently on suspension from the net.
Abusive, insulting, slanderous, instigative posts are grounds for net removal.
Intelec Network messages must never be gated to any non-Intelec-member BBS's.
Posts must not be used to proselytize, campaign, or advance personal agendas.
Profane, offensive, obscene, indecent, or any demeaning posts are prohibited.
Topics deemed immoral, unethical or poor taste by the NetAdmin are prohibited.
Message encryption, for any reason, is prohibited in all Intelec conferences.
English is the only language approved for use anywhere in the Intelec Network.
ANSI is permitted in the Intelec ANSI conference only, no post may exceed 7K.
RIP is permitted ONLY within the RIP Graphics conf, and no post may exceed 7K.
Large RIP screens may not be "split up" into several posts to bypass 7K limit.
BBS ads are only allowed in the BBS_ADS and ANSI conf & once per BBS per week.
Signature, taglines from moderators of other nets must be kept out of Intelec.
Signatures may not be more than 3 lines and 80 total characters and/or spaces.
Taglines must not be more than 1 line and 79 total characters and/or spaces.
Taglines must not be worded in such a way that its intent is to demean others.
Taglines which parody public figure(s) must not be used with malicious intent.
MLM's, Fast Cash, and get rich quick schemes are grounds for instant removal.
Solicitations or donation requests are prohibited in ALL Intelec conferences.
Solicitations do not include listing "subscription rates" within any BBS Ads.
Donations do not include requests directly from Freeware & Shareware software.
┌─────────────┐
│ SysOp Rules │
└─────────────┘
NetAdmin must be read at least by all member SysOps for mail to "ALL and YOU".
Network taglines must begin with the string "Intelec ■" (without the quotes).
In the following 9 lines, Hubs refers to Super Regionals, Regionals, and Hubs.
Hub BBS's are expected to have the current IN_yymm.ZIP file available for DL.
Hub SysOps may not TCAN any user from the network without approval of admin.
Hub SysOps must abide by any administrative decisions effecting their regions.
Hub SysOps must carry any & all Intelec conferences requested by their Nodes.
Hub SysOps are authorized to remove access of nodes if the situation warrants.
Hub SysOps must notify the Administrator if nodes are removed for any reason.
Hub SysOps must relay mail at least once per day unless temporarily unable to.
Hub SysOps may not shut down for 24 hours without making provisions for nodes.
Hub SysOps failing to relay for 2 days, without notification, will be removed.
Hubs must relay through their respective SR, Regional Hub at least once a day.
Regional Hubs must relay at least once a day through their Super-Regional Hub.
Super-Regional Hubs must relay through the Network Host BBS on a daily basis.
SysOps may never edit in any way, any message relayed via the Intelec Network.
SysOps must follow any and all directives of their SR, Regional or Hub SysOps.
SysOps must not post "xxx BBS is now echoing here" messages outside NetAdmin.
No Intelec posts may be placed "outside" the network without admin permission.
┌─────────────────┐
│ Chief Moderator │
└─────────────────┘
The Chief Moderator (CM, Rod Wardlow) is the Moderators of all the Moderators.
The CM is responsible for settling any disputes between users and moderators.
The CM may join any conference to see to the "enforcement" of network rules.
The CM may overrule a moderator when it's in the best interest of the network.
┌────────────────────────┐
│ Moderator Rules & Tips │
└────────────────────────┘
Moderators go to the CM 1st for assistance with a conference related problem.
Moderator appointments can be revoked should they fail their responsibilities.
Moderators must have access to the Moderators Conference on their "home BBS".
Keep threads on topic. Ask off-topic posts be moved to appropriate conference.
Welcome any new participants to your conference soon after a user's arrival.
When moderating someone make sure they know they received an official warning.
Include words "first, second, Official Warning" in any warnings to your users.
Ask for acknowledgement of all warning messages (to counter-act user excuses).
If a user chooses to dispute your moderation, they must move it to USER-2-MOD.
Never fan the flames by insulting in return. Be polite and avoid any sarcasm.
If 1st reaction is to blast away with warnings, step back until you calm down.
Consider mail lag time. Users may break the same rule before getting warning.
Keep record in a notebook or file to serve as reminders of who/when moderated.
Besides you representing your conference your "actions" represent our network.
Moderators found making "enflamatory statements" will be removed as moderator.
When in doubt... ask. Use the Moderators conference for the exchange of ideas.
Seek help if you are not sure of your position or how to handle unusual cases.
Inform the CM of all Official Warnings. Include user name, tagline & subject.
Suspensions are granted or denied by CM after reviewing a review of situation.
1st priority considered for suspension is non-compliance to the Intelec rules.
Moderators may not suspend participants on their own but by request to the CM.
The CM can't Ban (TCAN) anyone. This action is made by the Net Administrator.
Moderators should keep their personal beliefs out of decision making process.
Be impartial. Strong religious/political view points may cloud your judgement.
Avoid letting users know your personal beliefs on any subjects of controversy.
Keep the Intelec distribution files handy. You are expected to know our rules.
Put yourself in another persons shoes when you're trying to cool off disputes.
Do not let this hobby get to you. You are dealing with a very diverse public.
Moderator should pose tact, decorum, diplomacy and good communication skills.
Having an active interest in the conference topic is helpful but not required.
Moderators must read NetAdmin, Moderators and UseR-2-Mod on regular basis.
In NetAdmin you may use the YA option in your reader but real "ALL" in others.
If conference mail traffic drops too low, attempt to "stimulate" new threads.
"Plug" your conference in confs similar to yours (with moderators permission).
Before responding harshly to off topic posts, make sure it's not a cross-feed.
Report any cross-feed or duplicate problems to the Net Administrator (not CM).
Don't criticize, critique other moderators, especially in a public conference.
If you feel a moderator needs "advice", do so only in Moderators conference.
Conference specific guidelines may be used if for "success" of the conference.
Conference specific guidelines must be approved by the CM (Chief Moderator).
Be sure your position is known. Identify yourself as the moderator in tagline.
Never use "official sigs/tags" out of your conf, except for admin conferences.
If you disagree with the CM's ruling, you may appeal to the Net Administrator.
Moderators can allow ads to be placed in a conference if beneficial to users.
Intelec prohibits "vendor posts" advertising in any conference except ForSale.
┌──────────────────────┐
│ Bans and Suspensions │
└──────────────────────┘
"Network Tcans" are subject to the sole approval of the Network Administrator.
Request for suspension and/or bans must be done in the Moderator's conference.
Suspension and network-wide bans are determined by the following procedures:
1 - Warning message must come from the moderator before administrative action.
2 - If user's violation is severe or blatant enough, #1 above is not required.
3 - If there is a repeated incident, then 30 day suspension is a minimum term.
4 - Offenses do not need to be the same type nor be in the same conference(s).
5 - The Administrator can [Ban] or CM can [Suspend] the user if situation #2.
6 - A 90 day minimum probationary period will follow all bans and suspensions.
Moderator may request user suspensions only when above conditions 1-2 are met.
Temporary suspensions are 30 days, unless shortened/extended by Administrator.
If users breaks rules while on suspension they may be banned from the network.
Bans are any term, inc. "until further notice" as determined by Administrator.
Bans are "conference specific or network-wide" as determined by Administrator.
The CM, upon enacting a user suspension, will inform the user's SysOp that the
user has been suspended for 30 days from a conference and inform that SysOp to
remove the user's access to it. Upon network-wide suspension or ban SysOps may
appeal the decision on behalf of the user in the Moderators conference but may
only take place "after" the suspension or ban has been enforced by the SysOp.
┌──────────────┐
│ Conf Configs │
└──────────────┘
NetAdmin: Public/Required of all members for administrative-related topics.
User2Mod: Public/Required of all members for "user-2-moderator" discussion.
Moderators: Private/Required open only to Intelec SysOps and their Moderators.
SysOps: Private/NOT Required and open only to validated System Operators.
Regionals: Private/Required of all hub SysOps for any application processing.
Applications must NOT be relayed through any other conference within Intelec.
Any other "public" Intelec conferences may be made private on any member BBS.
SysOps MUST make their users aware of any conferences that they do not carry.
┌──────────────────────┐
│ Conference Proposals │
└──────────────────────┘
Conference proposals/suggestions are to be made to the Network Administrator.
Conference must have sufficient [user] interest before it can be considered.
Conference that can be construed as "adult or immoral" will never be added.
Conference can't be topic-related to existing conference unless branching off.
Conference must have a moderator appointed before it can be added to the net.
Moderators are "appointed" by the Network Administrator, make requests to him.
New conferences will be added to the host system on the 1st of the month only.
┌────────────────────┐
│ Software Supported │
└────────────────────┘
The only BBS and Networking software that is approved for use with Intelec is:
PCB:Rnet/Qnet/Cam-Mail/RoseMail WC:Tnet Gap:GapNet SynchroNet:SynchroNet
TriBBS:TriNet Spitfire:Jnet Auntie:QWiKerNet Remote Access:MkNet
If something isn't shown, we're no longer accepting BBS applicants running it.
Applications requesting to use software not listed above won't be processed.
┌────────────────────┐
│ Approvals/Removals │
└────────────────────┘
Acceptance to Intelec Network is determined by the Administrator or an Intelec
Super, Regional or Hub SysOp authorized to handle this. Incomplete or outdated
applications aren't processed. The Network Administrator reserves the right to
admit or refuse any BBS SysOp as participating members of the Intelec Network.
The Network Administrator also reserves the right to remove and/or suspend net
access of any member-SysOp for any action considered detrimental to the goals,
spirit or quality of the Intelec Network or for failure to abide by our rules.
┌──────────────┐
│ Private Mail │
└──────────────┘
Pursuant to the Electronic Communications Privacy Act of 1986, 18 USC 2510 et.
seq, all BBS SYSOPs and users participating within Intelec, must be aware that
there are no facilities provided by Intelec for sending/receiving confidential
electronic communications. Although Intelec maintains the capability/capacity
to send or receive mail that is flagged as "Receiver-Only", mail so flagged is
not to be considered by any user as actual "private" messages. Intelec Online
is NOT configured to permit the passing of "RO" mail through the host system.
┌─────────────────┐
│ Host Operations │
└─────────────────┘
Intelec Host BBS equipment is NOT the property of any system relaying Intelec.
No claims may be made against the software & hardware that "comprises" the Net
Host BBS. All software, hardware required to run the Net Host BBS is privately
owned and used with permission by the owners of Intelec Business Network, Inc.
Intelec is operated as a "public service" by Intelec Business Network, Inc and
Intelec Online serves as the Net Host BBS. Intelec is administrated by Cliff
Watkins, SysOp of Intelec Online. While Intelec operates as a public service,
it is NOT a "public access" network. We're a "private network", thus the rules
of operation that are set forth within this document, supersede any/all rights
set forth outside the boundaries of this document.
┌────────────────┐
│ Membership Fee │
└────────────────┘
Membership fee is a $35 one-time charge, and is due within 10 days of approval
(not from the start of relays). The failure of fee to arrive within this time
will result in the termination of access to the network. If a SysOp is removed
from the network for network rule infractions, or in the case of fraudulent
applications the fee isn't refundable. Payment must be made either by check or
money order and MUST be in the form of US dollars. Non-US applicants MUST pay
by Postal Money Order ONLY and only in US dollars. Personal checks *cannot* be
accepted from Non-US applicants. There's a $20.00 fee for any returned checks.
Make checks payable to Cliff Watkins, and mail to:
Cliff Watkins
P.O. Box 212
Baldwin, NY 11510-0212