Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Tristan Seligmann
On Wed, Sep 12, 2012 at 2:12 AM, Adrian Overbury wrote: > However it is entirely possible to sanely parse and store replies in a > reactionary system because the first component of an RPL_NAMREPLY message is > the name of the channel it applies to. > > You can log or quietly drop replies that ar

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Adrian Overbury
On 12/09/2012, at 8:01 AM, "Jasper St. Pierre" wrote: > On Tue, Sep 11, 2012 at 9:43 AM, wrote: >> On 10:49 am, mithra...@mithrandi.net wrote: >>> On Tue, Sep 11, 2012 at 6:05 AM, Glyph wrote: Such a bug may already exist - if you wouldn't mind, would you search for it, and if y

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Glyph
On Sep 11, 2012, at 3:01 PM, Jasper St. Pierre wrote: > Additionally, IRC daemons may play tricks and send out "replies" that > doesn't associate with any request you've sent, as a means to have a > client perform a specific action; for instance, bouncers usually send > join replies without any

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Jasper St. Pierre
On Tue, Sep 11, 2012 at 9:43 AM, wrote: > On 10:49 am, mithra...@mithrandi.net wrote: >>On Tue, Sep 11, 2012 at 6:05 AM, Glyph wrote: >>>Such a bug may already exist - if you wouldn't mind, would you search >>>for >>>it, and if you can't find it, file a new one? >> >>I don't know if there's an e

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Tristan Seligmann
On Tue, Sep 11, 2012 at 6:46 PM, Glyph wrote: > So... you're recommending exactly what twisted.words.im already does? :) Well, yeah: "The only way to reliably use the NAMES command is the way twisted.words.im.ircsupport [already does]" :) > Keep in mind that we can assume to have control over ou

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Glyph
On Sep 11, 2012, at 9:12 AM, Tristan Seligmann wrote: > On Tue, Sep 11, 2012 at 3:43 PM, wrote: >> This is the excuse that is always given for not implementing a new >> feature on `IRCClient`. However, here's another equivalent way of >> stating the objection: >> >> IRC is a terrible protoc

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Tristan Seligmann
On Tue, Sep 11, 2012 at 3:43 PM, wrote: > This is the excuse that is always given for not implementing a new > feature on `IRCClient`. However, here's another equivalent way of > stating the objection: > > IRC is a terrible protocol and it is very difficult to implement a > method like `name

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread exarkun
On 10:49 am, mithra...@mithrandi.net wrote: >On Tue, Sep 11, 2012 at 6:05 AM, Glyph wrote: >>Such a bug may already exist - if you wouldn't mind, would you search >>for >>it, and if you can't find it, file a new one? > >I don't know if there's an existing bug or not, but implementing a >names() m

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-11 Thread Tristan Seligmann
On Tue, Sep 11, 2012 at 6:05 AM, Glyph wrote: > Such a bug may already exist - if you wouldn't mind, would you search for > it, and if you can't find it, file a new one? I don't know if there's an existing bug or not, but implementing a names() method is problematic. The natural API would be some

Re: [Twisted-Python] implementing NAMES in IRC

2012-09-10 Thread Glyph
On Sep 10, 2012, at 6:24 PM, Art Scheel wrote: > Now, is stackoverflow overriding that method or was it perhaps written prior > to the implementation of the irc.py portion I linked to? The StackOverflow answer is implementing a new method, on IRCClient. The implementation in irc.py that you'