[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Weechat-dev] [task #9335] Parsing for a KNOCK event

From: Sid
Subject: [Weechat-dev] [task #9335] Parsing for a KNOCK event
Date: Tue, 21 Apr 2009 19:58:08 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/2009033008 GranParadiso/3.0.8


                 Summary: Parsing for a KNOCK event
                 Project: Wee Enhanced Environment for Chat
            Submitted by: trashlord
            Submitted on: Tue 21 Apr 2009 07:58:06 PM GMT
                Category: irc plugin
         Should Start On: Tue 21 Apr 2009 12:00:00 AM GMT
   Should be Finished on: Sun 31 May 2009 12:00:00 AM GMT
                Priority: 3 - Low
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                IRC nick: Trashlord



Networks running the ConferenceRoom IRCd have a channel mode U.

When the mode is set (+U), all failed channel joins make the server send a
KNOCK message to the channel ops.

Channel join failures can be caused by a user being banned, the channel being
set to invite only (+i), and so on.

Here is how a KNOCK message for a CHANNEL BAN looks like:

:address@hidden KNOCK #nif 474 :Channel join
failed: Channel ban (address@hidden)

address@hidden KNOCK #channel 474 :Channel join failed: reason

This is not a critical feature, it is merely for the convinience factor of
not being flooded with unparsed raw messages in the status window of the

If an easy way of grabbing this event with a script (such as grabbing privmsg
events) will be added to the plugin API, this will be a big plus - but, again,
is not really necessary at this point.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]