Re: [EPIC] (important discussion) privmsg in response to a privmsg
My reaction: No; do not change this. There is a very good reason it exists, and having it be that way makes people who wish to do that learn what not to do. They can still get around it (and I do it myself) but with what we hope is a more clear understanding of what happens when they screw up. Forgive the analogy, but it's like getting a concealed weapon permit. -scromp On Aug 24, 2005, at 13:10, Jeremy Nelson wrote: [ snip whether to remove poo loop traps ] ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
Re: [EPIC] (important discussion) privmsg in response to a privmsg
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
[EPIC] (important discussion) privmsg in response to a privmsg
Preface: Jm has wanted this change for a while, but has resisted my suggestions he should appeal this issue to the list (all of you). Since I do not support the request to change this, I must apologize in advance for any lack of impartiality I may have regarding this discussion. Anyone who disagrees with me, I beg and implore you to speak up now, because once the matter is settled, I want to keep it that way... - 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. This behavior is implied by the wording of the irc protocol, but is not explicitly mandatory. There are various hackish ways around it, using /quote, /timer 0, etc. 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. Shall this feature be removed, and shall all restrictions on sending PRIVMSGs from any place for any reason be removed? I shall abide by the will of the consensus of those who participate in this discussion, and I will consider the matter closed once we reach that consensus. If there is no consensus, then I will not make any changes, but will continue to consider the matter open. Jeremy ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
