On Wed, 2004-03-10 at 17:10, Chip Norkus wrote: > > This isn't quite correct. Oper wallops are differentiated from *local* > > oper wallops by that prefix, and it is done by issuing a /whois or > > /userhost (I'm not sure which EPIC is using these days). The client > > itself adds the prefix, not the server. (Undernet's '*' and '$' > > prefixes are a little more specialized...) > > > > I'm speaking of the prefix to the message itself. The client will get > something like: > :foo WALLOPS :this is a wallops message > on regular wallops and > :foo WALLOPS :OPERWALL - this is an operwall message > on operwalls. There's nothing preventing me from doing > '/wallops OPERWALL - HA HA FOOLED YOU'.
I don't know of any ircd that does this, but my range of experience is rather limited. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
