home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!LATECH.BITNET!SPJRG
- Message-ID: <RELUSR-L%93012115462899@NCSUVM.CC.NCSU.EDU>
- Newsgroups: bit.listserv.relusr-l
- Date: Thu, 21 Jan 1993 14:34:02 CST
- Sender: Relay Users Forum <RELUSR-L@NCSUVM.BITNET>
- From: "Jim Glover (Key), Relay Op" <SPJRG@LATECH.BITNET>
- Subject: Re: Changing /signon options ?
- Lines: 25
-
- >But is it really such a chore to type
- >
- >/si 543
- >
- >instead of
- >
- >/si
- >
- >?
-
- Actually, one should never /signon to a private channel (any channel
- besides 0-99) without checking first to see if the channel is vacant.
- Before entering the quoted command, you should wait for a response to
- the command: /who 543 Only if Relay responds by telling you that
- there is no one on that channel should you go ahead and /signon to that
- channel. Please note that you should *never* /signon or /ch to a
- private channel you haven't been invited to until you have confirmed
- that the channel is empty.
-
- Of course, it would be perfectly OK to /signon to a public channel
- without checking first, e.g.:
-
- /si 43
-
- --Jim (Key)
-