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 other question is, will this channel mode break IRC clients?
stoney`

At 04:33 PM 7/27/2002 +1200, you wrote:
>Due to the nature of IRC's client<->server protocol, the join/parts are a
>must, but because of the server and traffic load, setting (and in particular
>removing) a channel mode to do this is probably not practical, how about
>creating a new channel type, that is global (like # and + channels) but is
>always in this "auditorium" mode with perhaps a channel mode for defining
>whether +v users can be seen or not.
>
> > On Fri, Jul 26, 2002 at 09:15:26PM +0200, bas wrote:
> >
> >> Sounds like "auditorium" mode. IRCplus has it, check ircplus for which
> >> char they use (if you must). i dont think this feature should be used on
> >> undernet, as its far from "pure", which ircu is atm.
> >
> > Thanks for the tip about IRCplus; I'm talking about this change for the
> > QuakeNet patch rather than ircu "proper" anyway, so whether it gets used or
> > not depends on whether I can persuade the QuakeNet people that it's
> > worthwhile :).
> >
> > Anyway, ircplus uses +x for "auditorium" mode.  It appears to have the
> > following properties:
> >
> > * When +x is set, it broadcasts lots of PARTs such that only the opped 
> users
> > remain visible to the non-opped users.  Opped users still see everyone.
> >
> > * Once +x is set, opped users can see everything, non-ops can only see
> > ops; the same goes for channel text (so ops can see things said by
> > non-ops)
> >
> > * If someone is opped, a JOIN is broadcast to everyone, and the opped user
> > sees a JOIN flood of all the previously-invisible users.
> >
> > * If someone is deopped, a PART is broadcast to everyone, and the opped 
> user
> > sees a PART flood of all the non-op users.
> >
> > * If the chan is set -x, it appears to break horribly :).  I don't know if
> > it's just a bug in the particular version I tested[1] but it completely
> > shafts client sync; doesn't even broadcast the -x change to clients
> > (although the -x change does happen).  mIRC users doing a /names get their
> > namelist back in sync but I don't think this can be relied upon.
> >
> > I think if we do implement this feature we need something more along the
> > lines of what I explained initially (i.e. +v users are visible and can
> > talk but can't see everyone).
> >
> > splidge
> >
> > [1] It spewed some random error at me, so it did know it was broken..
> >
>
>
>--
>http://www.mediadesign.school.nz/
>
>CAUTION: This communication is confidential and may be legally privileged.
>If you have received it in error you must not use, disclose, copy or retain
>it. Please immediately notify us by return email and then delete the email.
>
>This message has been scanned for viruses and dangerous content by
>MailScanner with McAfee UVScan, and is believed to be clean.

Py Fivestones
[EMAIL PROTECTED]


Reply via email to