home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.irc
- Path: sparky!uunet!usc!sdd.hp.com!ux1.cso.uiuc.edu!randall
- From: Upholder@uiuc.edu (THE Upholder of Truth)
- Subject: Re: /summon command?
- Message-ID: <Bttvs4.3K8@ux1.cso.uiuc.edu>
- Sender: randall@ux1.cso.uiuc.edu (THE Upholder of Truth)
- Reply-To: Upholder@uiuc.edu (THE Upholder of Truth)
- Organization: The University of Illinois at Urbana-Champaign (UIUC)
- References: <BtsBCJ.1BM@ux1.cso.uiuc.edu> <Btt0ov.8n4@news.cso.uiuc.edu>
- Date: Mon, 31 Aug 1992 03:16:37 GMT
- Lines: 27
-
- jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
- >randall@ux1.cso.uiuc.edu (THE Upholder of Truth) writes
- >> Not their client.. but another client on the same host.
-
- >Doesn't sound to me like that would fall within the bounds of what a
- >client does. Also, since there would be no way to turn this messaging off
- >(like you can turn talk and write requests off via "mesg n" or "chmod go-w
- >`tty`") it might be better if the summoning went through mail.
-
- The Original Idea I had was that it would user writes to the tty...
- (ie, if they *DO* 'mesg n' or 'chmod go-w `tty`' then they summon
- would fail with the usuall 'This user seems to have disabled summoning'
- message).
-
- The Other reason I proposed implementing it in the client is that clients
- are found on almost every machine that people IRC from (ie, the machines
- that you would want to /summon someone from). Currently, you can only
- summon people from machines that have *SERVERS* on them... (and we all
- know that there are already way too many servers on the net).
-
- But... it seems that nobody is interested in /summon working as easliy
- as talk(1) requests... Oh well... it was just an idea to kick around anyway.
- --
- The Upholder of Truth I am not only ready to
- Upholder@uiuc.edu (BSD/ASCII mail) retract this, but also
- jar42733@sumter.cso.uiuc.edu (NeXT mail) deny I said anything. =)
- wi.4173@wizvax.methuen.ma.us (anon. mail) This is *NOT* CCSO's opinion.
-