Jeremy Nelson <[EMAIL PROTECTED]> wrote: > Since time immemorial, when you are inside of an /on caused by a privmsg > (/on msg, /on public*, /on ctcp, etc) and you try to send a PRIVMSG (/msg, > /ctcp, /redirect, etc), ircII has always (silently) changed it into a NOTICE.
> EPIC maintains backwards compatability with ircII in this regard, and changes > your PRIVMSGs to NOTICEs because avoiding accidental message loops is one of > the responsibilities a client has. While browsing EPIC's home site I found a notice stating that the client's goal is to be more feature-rich while still getting less bloated and overly complicated. Same with that you're just giving tools, as you stated, not the whole product. I may not see any reason for replying to PRIVMSG with another PRIVMSG, but this may cause confusion among ones, who create well-thought innovations by scripting. It's not your responsibility for one's bad creation, you're just giving the tool, ie. the knife. You got the picture. If I were you, I would just remove the code (along with the one preventing replying to NOTICEs) and wash my hands. But it's up to you. regards, -- Stanisław Halik :: http://weirdo.ltd.pl _______________________________________________ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
