🚀 go-pugleaf

John:

Here is the info you request about relay:

:READ  RELAY    INFO     A1 RLY1A1 12/15/89 10:57:40
                     RELAY - A CONFERENCING FACILITY


By using Relay, all users of this Relay are considered to have
accepted the Relay policies contained in this guide and are expected
to adhere to these guidelines.  If you have any questions related to
using Relay or Relay policies, please contact the MasterOp of your
Relay (obtained by sending "/co" to your Relay's id).

The Computing Services Center provides this Relay as a service
to the network community and users should be aware that use of this
Relay is a privilege, not a right.  In general, RelayOp decisions are
based on BITNET and Relay policies and the policies of this host
Relay and its node.  The MasterOp reserves the right to make the
final decision on appropriate use of and appropriate behavior on
this Relay.  Please follow all requests made by a RelayOp.  If you
feel the request was unjustified, please comply with the request and
then contact your MasterOp.


RELAY--A BENEFICIAL EDUCATIONAL TOOL

Relay provides faculty/staff/students the opportunity to electronically
"conference" with their colleagues at other educational institutions
around the world.  In the past, business meetings, committee meetings,
faculty conference sessions, and classes have been held and conducted
on Bitnet using the Relay facility.

Relay promotes computer literacy.  It teaches faculty/staff/students
basic computer skills as they learn how to use the system while
interacting with colleagues at other universities around the world.

Access to BITNET and Relay promotes the engineering and technical
resources that a school has and leaves a marked impression of the
quality of computing facilities that exist at a university.

Relay gives a user first-hand experience in network theory
by actually seeing how it operates.  It is a good example
for Computing Science courses such as Operating Systems,
Networks, etc. in which networking theories are studied.


GENERAL GUIDELINES FOR RELAY USAGE

Relay provides real-time communication between multiple users at various
institutions in the BITNET, EARN, and NetNorth networks.  Use of these
networks for any purposes not directly related to the research,
instructional, and/or administrative tasks for which your userid has
been authorized by your institution may result in the termination of
your ability to use the Relay and/or in termination of your userid.
Internal use, using and/or limiting the Relay conferencing system for
communication either wholly within one node, or within one institution
over several nodes and/or servers, is the total responsibility of that
institution and host.

Network-wide use of Relay falls under the guidelines presented herein.
Failure to adhere to these guidelines and to general network usage
guidelines may result in the loss of your ability to use Relay.


User Responsibilities

Relay is a distributed message server which, by selective switching and
redistribution of messages, provides real-time conferencing capabilities
while minimizing the overhead on the network links.  Since the potential
load of uncontrolled message traffic on the network can affect transfer
of files, stringent controls over Relay use are mandatory.  Most control
measures are enforced by Relay automatically, but some are necessarily
the responsibility of the user.  These include:

   * Each Relay server provides service to a specific collection of
     one or more nodes designated as a "service area".  You should
     direct your queries only to your assigned Relay.

   * Excessive queries, channel changes, nick changes, and other
     commands which must be processed by Relay generate considerable
     overhead and should be kept to a minimum.

   * File backlogs, Relay host CPU saturation, link failures, and node
     downtime may make Relay temporarily unavailable or restricted.

   * Proper and considerate behavior should be observed at all times.
     The same socially accepted behavior in public in real life also
     applies to your conduct and behavior on Relay.  Behavior on
     public channels (0-99) should follow conservative standards.  Less
     restrictive standards can be followed on private channels (100-999).

     Some DON'TS in the behavior category include, but are not limited
     to, the following:

     a. Disguising your identity in a /REGister by not specifying your
        full name or by specifying someone else's name.
     b. Transmitting rude or obscene language.
     c. Using obscene or offensive nicks; using all-symbol nicks.
     d. Signing-on more than one account on Relay at the same time.
     e. Channel scanning; attempting to intrude on a private channel
        without obtaining an invitation from a user on that channel.
     f. Annoying other Relay users by transmitting excessive and/or
        repetitive messages (including pictures).
     g. Failing to cease an activity in response to a request to do so
        from any individual designated as a 'Relay Operator'.
     h. Rude and discourteous behavior toward other users.  The same
        manners and courtesies that apply to every day life also
        apply to Relay.
     i. Using other people's accounts without their permission and
        without the node admin's permission.
     j. Running programs on Relay without prior permission from
        the MasterOp and/or node admin; signed onto Relay disconnected;
        (loads the net and raises cpu unnecessarily).

   * Abusive and obscene behavior should be reported to a RelayOp
     who is signed onto Relay at that time by issuing the "/GETOP"
     command.  (This command shouldn't be used for trivial or
     non-Relay matters, however.)  If you get no response from the
     "/GETOP" command, you can send a note about the problem to
     your Master RelayOp.  (Sending the "/CO" command to your Relay
     will give you your Relay's MasterOp's name and userid.)

Not observing Relay and Bitnet guidelines and protocol can result in
suspension of Relay privileges.  Relay is a *privilege*, NOT a right,
and Relay abuse will NOT be tolerated!


Relay User Classification System

Due to high volumes of message traffic, users are placed into one of
the following classes.

(1) Public user class (Class 2).  Any user may obtain public access to
    Relay by a standard /REGister command.  Public users are limited to
    channels 0-999 and are additionally subject to channel limits, peak
    period shutdowns, and limited hours of operation.  The prime time
    period is closed to the public and Class 2 users.  (Prime time
    is usually 8 a.m. - 5 p.m., Monday - Friday, although each host
    Relay can adjust the time period as needed.)  In addition, there
    is a maximum signon limit of users per Relay host (10-16, depending
    on the limit set by the host Relay--most are set at 12).

(2) General user class (Class 3).  A user may, in certain circumstances,
    be given Class 3 status for full access to Relay (at the times the
    assigned Relay is running of course).  Class 3 users are not
    restricted by prime time, channel/signon limits, negative channels,
    etc.  Class 3 status is restricted to faculty/staff members (and
    under certain circumstances graduate students) and to academic
    conferencing activities during prime time.  Class 3 users are
    expected to adhere to all Relay/Bitnet rules and guidelines and
    should "set the example" for other users regarding proper behavior.
    Also, Class 3 users should not let other people use their accounts
    for Relaying.  ABUSE OF THIS CLASS WILL RESULT IN THE LOSS OF
    CLASS 3 PRIVILEGES (and possibly of Relay privileges also).

    General user class can only be granted by the host Relay.  Users
    desiring this class for academic conferencing use must submit a
    request in writing to their host Relay MasterOp, along with adequate
    evidence and justification for its use.  The host Relay may
    require additional information or replace further constraints
    on such services.


RELAY COMMANDS - DESCRIPTIONS

You communicate with Relay through messages just as you would send
messages to a user.  Relay commands start with a slash (/) character;
anything not beginning with a slash is considered a message and is
transmitted to all other current users.  The commands are listed
below and described in more detail following the list.

Relay: ******************** Relay Commands *********************
Relay: * /BYE . . . . . . . . . . . . . . . . . Signoff from Relay
Relay: * /Channel number <,force> . . . . .Change to channel <num>
Relay: * /COntact <relayhost> . . . . . . .Show Relay contact info
Relay: * /GETOP . . . . . . . . . . Try to summon a Relay operator
Relay: * /Help. . . . . . . . . . . . . . . . . . Prints this list
Relay: * /INFo. . . . . . . . . . . . . . . . Send RELAY INFO file
Relay: * /Invite nick . . . . . . . . .Invite user to your channel
Relay: * /LCL <relayhost> . . . . . . .Show users on a given relay
Relay: * /LINKMsg ON | OFF. . . . . . Turn link messages on or off
Relay: * /LINks . . . . . . . . . . . . . . . .Shows active relays
Relay: * /List. . . . . . . . . . . . . . . . List active channels
Relay: * /Msg nick text . . . . . . . . . . .Sends private message
Relay: * /NAmes <channel> . . . . . . . . . .Show users with names
Relay: * /NIck newnick  . . . . . . . . . . . Change your nickname
Relay: * /OPNames . . . . . . . . . . . . . .Show active Operators
Relay: * /Rates . . . . . . . . . . . . . . .Display message rates
Relay: * /REGISTER full name  . . . . . . . . . Register full name
Relay: * /RULES . . . . . . . . . . . . Sends the RELAY RULES file
Relay: * /SErvers <node>  . . . . . . . . Show relays serving node
Relay: * /SIGNOFF . . . . . . . . . . . . . . . Signoff from Relay
Relay: * /Signon <nick> <chan><,force><,unshift>  .Signon to Relay
Relay: * /SINce . . . . . . . . . . .  Show recently arrived users
Relay: * /STats . . . . . . . . . . . . . Display Relay statistics
Relay: * /SUmmon userid@node  . . . . . . . . Invite user to Relay
Relay: * /SWho <channel>  . . . . . . . . . . . . . Show nicknames
Relay: * /TList . . . . . . . . . List channels which have a topic
Relay: * /Topic subject . . . . . . . . . . Topic for your channel
Relay: * /Users <Detailed> <Full> . . . . . . Show number of users
Relay: * /Who <channel> | <*> . . . . . . Show users and nicknames
Relay: * /WHOIs nick | user@node  . . . . . . .Identify a nickname
Relay: ********************** End of list **********************


/REGister (first-name) (last-name)

In order to start using Relay, you must be in the Relay Users file.
This command makes an entry in the local users file so that you will
be a registered Relay user.  Relay guidelines require that users register
with their real name--a policy that most Relays enforce.  Registering
with a false name can cause one to be denied Relay use privileges.  The
/REGister command needs to be done *only once* per userid!
     Example of a REGister:  /reg John Smith


/Signon nickname (channel),(options)

In order to get on Relay, you must use the /Signon command.  The
nickname parameter is used to give yourself a name which will be used
to prefix all of your messages.  If you omit the nickname, Relay will
use your userid.  Users are requested to refrain from using vulgar or
offensive nicknames (please try to be considerate of the other users).
If you wish to signon to a specific channel, you can give the
channel number following the nickname, i.e., "/s Charli 777"
would put you on channel 777 with a nick of Charli; if channel
number is omitted, you will be put on channel 1.

For the benefit of users on special terminals, you can signon with
UNSHIFT or SHIFT as an option field, i.e. "/s Charli 777,unshift".
Users on terminals with uppercase only should use the unshift option
which will translate their messages to lowercase.  (It is considered
impolite to SHOUT, i.e. transmit messages all caps.)


/BYE

This command is used to leave Relay.  Ex:  /bye


/Who (channel)

The /Who command will list all users on all channels, showing their
channel number (if not private), nickname, userid and nodename, and the
Relay they are signed onto.  To list only those users on a certain
channel, use "/who channel-no", i.e., "/who 10".  To list only those
users on your own channel, use "/who *".


/WHOis (nickname) (userid@node)

The /WHOis command will show the userid, node, and name of the user,
i.e., "who charli".


/NAmes

Same as "/who" except will show users' names in place of Relay host.


/LCL

Lists local signed-on users only.


/OPNames

Lists signed-on RelayOps.


/COntact (relayhost)

Will return the contact info (the MasterOp) for the host Relay (or
for the Relay specified, i.e., /CO or /CO aggieland.


/List

The /List command displays all currently active channels and how many
users are on each channel as well as any topics which have been set
for any of the channels.


/TList

Lists only channels with assigned topics.


/Help

The /Help command will display an abbreviated list of commands.


/Getop

The /Getop command sends a "needing help" message to all signed
on RelayOps.


/INFo

At most Relays, the /INFo command sends you this file.


/Channel (number)

The /Channel command is used to change to another channel.  To avoid
overcrowding and to provide for "private" conversations among groups
of people, Relay provides channels.  Channels are always a number,
and the following channels are supported:

     Channel 1 is the default public channel.
     Channels 0-99 are the public channels.
     Channels 100-999 are the private channels.
     Channels 1000-999999999 are the private channels for the general
       user class only (Class 3).
     Channels less than zero (negative channels) are superprivate
       and for the general user class only (Class 3).

Channels above 99 do not appear on the user list when doing a /who;
they are shown as ??.  Negative channels do not appear on the user
list at all.


/Msg (nickname) (message-text)

The /Msg command sends a private message to only the user you specify by
nickname.  You can send private messages to anyone signed on.  Private
messages appear with asterisks around the sending user's nickname,
i.e., <*Charli*> Hello.


/SUmmon (userid@node)

The /SUmmon command causes an invitation to be sent to the specified
remote user asking them to join Relay on your channel.


/Invite (nickname)

The /Invite command causes a private message to be sent to the specified
nickname inviting them to join you on your channel.  This is a quick way
to summon a user who is already signed on, but on a different channel.


/NIck (new-nickname)

Used to change your nickname--useful for correcting typos.  (Some
Relays have disabled this command due to it being abused.)


/LINks

Displays currently active Relays connected to the host Relay.


/Topic (one-word-topic)

The /Topic command adds a one-word entry to the topic field of /List
for the channel you are currently on.  Three one-word topics are
supported and may be used to show the general interest of the people
on a given channel.


Helpful Hints

Messages sent on Relay which begin with an asterik (*) will not be
transmitted.  To start a message with an asterik, put another character
before it, such as a period.  example:  ..*smile*

Users of Relay can send a note to their Relay MasterOp if they have
any problems or questions regarding Relay.


CORRECTIVE ACTIONS -- Relay Operator Responsibilities

The day-to-day maintenance and operation of a Relay server is carried out
by the "Relay Operator", an individual or group of individuals who are
responsible to the institution's network administrative authority.  The
Relay Operator is also responsible for implementing corrective action to
temporarily or permanently terminate a user's access to Relay in cases
of violation of the guidelines described in this document.

Actions that can be taken by any Relay Operator against offending users
of any and all Relay servers:

   * sending an offending user a warning notification by message or mail;
   * forcing the offending user from the current Relay session;
   * temporary lockout (2 days or less) of the offending user.

Actions that can be taken only by a Relay Operator of the offending
user's host Relay server:

   * temporary (2 days or more) or permanent lockout of the
     offending user from Relay use.

Any corrective action taken by a Relay Operator against an offending user
of another institution's Relay server, other than single instances of an
abusive user being forced as a warning, should be documented by sending
mail to that server's Relay MasterOp outlining the reason for the action.


BACKGROUND INFORMATION

When chats first appeared on the network, they quickly became popular
with users, and lots of people started chatting.  Unfortunately, they
soon became the target of intense criticism because of the load they
placed on the network.  Relays alleviate the problem by spreading the
load across the network.  The local Relay only has to send out messages
to its immediate users, and a single copy to its neighboring Relays.
They, in turn, send out the message to their users and forward to the
next Relay, and so forth.  It is very much like BITNET itself; rather
than all nodes connecting to a single central site, they only connect
to their neighboring nodes and process only their own traffic,
forwarding the rest.