It's probably best if this was implemented on the client side. When we used to host #cricket many years ago, I remember a nifty lil ircII script (can't remember the name - /load quiet or /load silent or some such) that used to mute all the joins/leaves/nick changes into the status bar.
Mmmm Mandar Mirashi Maintainer: ftp.undernet.org, Undernet IRC FAQ. ftp://rtfm.mit.edu/pub/usenet/alt.irc.undernet For IRC help/Undernet information, check out http://www.undernet.org On Sun, 28 Jul 2002 [EMAIL PROTECTED] wrote: > Date: Sun, 28 Jul 2002 01:42:31 +0100 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [Coder-Com] Patch idea.. any thoughts? > > On Sat, Jul 27, 2002 at 02:43:11AM -0400, Py Fivestones wrote: > > > Doesn't that pretty much destroy the concept behind IRC, that is to allow > > people to chat with each other? Also, don't people on a channel have the > > right to see who they are keeping company, and thus being associated with? > > The mode under discussion is only for use for very large channels (and if > implemented would probably only be settable on channels at least 500 users > or something). Under these circumstances the points you mention are less > important (particularly if without the mode the users can't stay on the > network!). > > > The other question is, will this channel mode break IRC clients? > > If the implementation works as I envisage it, not really. There would be > users on the channel that the ircd knows about but the client doesn't, but > there is no way for the client to find out about them anyway (they can't > talk or anything, and nick changes etc. would be supressed). Enabling ops > to see all channel members would allow bots to function normally, too. > > splidge >
