On Fri, 2005-02-11 at 10:22, Jeremy Nelson wrote: > Presently, EPIC does not permit > > /QUOTE WHO
My only problem with the restriction on "/quote who" is that it's a bit difficult to use, say, some of Undernet's /WHO extensions, particularly together. (I frequently want to look up everyone using a particular IP, which would look like "/quote who <IP> xi" in pre-restriction clients.) The options that EPIC has don't seem to cover all the possibilities. Also, Undernet's /WHO has a syntax that lets the user specify the fields which they want to see, and I could see an oper using that for some scripting--but the EPIC restrictions make it difficult to use that extension. (Moreover, that use shouldn't affect EPIC's standard who queue, since when that extension is used, ircu uses a different numeric in its reply specifically to avoid confusing clients and scripts.) From a purist standpoint, though, any restriction on /quote seems bad. The /quote mechanism is intended to allow a knowledgeable user to do things that the client does not have specific support for. Putting restrictions on it seems to me to be making policy decisions for the user. As to how to resolve the who queue issue, I don't really have any answers to that. Perhaps a /set to turn it on and off and a set of built-ins to manipulate it from a script? That way, a knowledgeable user can do stuff guaranteed to break the queue, but protect it by turning it off or manipulating it to restore integrity? -- Kevin L. Mitchell <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ List mailing list [email protected] http://epicsol.org/mailman/listinfo/list
