#cinch on 2014-07-24 — irc logs at freenode.irclog.whitequark.org

2014-02-27 15:35 dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.1.0

00:56 _djbkd has quit [Remote host closed the connection]

00:56 djbkd has joined #cinch

01:01 djbkd has quit [Ping timeout: 240 seconds]

03:20 djbkd has joined #cinch

04:36 djbkd has quit [Quit: My people need me...]

05:42 FIQ has quit [Excess Flood]

05:44 Guest57908 has joined #cinch

08:08 postmodern has quit [Quit: Leaving]

08:23 irsol has quit [Ping timeout: 264 seconds]

08:24 irsol has joined #cinch

09:46 Guest57908 has quit [Excess Flood]

09:49 goez has joined #cinch

09:49 Guest75653 has joined #cinch

10:11 Guest75653 has quit [Changing host]

10:11 Guest75653 has joined #cinch

10:11 Guest75653 is now known as FIQ

15:31 v0n has quit [Ping timeout: 256 seconds]

16:01 FIQ has quit [Excess Flood]

16:03 Guest49231 has joined #cinch

16:54 djbkd has joined #cinch

17:39 postmodern has joined #cinch

19:20 Guest49231 has quit [Excess Flood]

19:23 Guest61793 has joined #cinch

19:26 v0n has joined #cinch

19:49 ironing has joined #cinch

19:49 <ironing> Is there any way to cause cinch to ignore certain or all events originating from certain hostmasks?

19:58 <onewheelskyward> Sure.

20:03 <ironing> Would you please be so kind as to give me a few pointers as to how to achieve that?

21:00 <onewheelskyward> well, when you execute your match, you have the msg object, which has a user, which has host. http://rubydoc.info/github/cinchrb/cinch/Cinch/User

21:00 <onewheelskyward> So, if it doesn't (or does) match a certain value, just bail out, do nothing, or tell them you're ignoring them,.

21:40 djbkd has quit [Remote host closed the connection]

22:14 postmodern has quit [Quit: Leaving]

22:17 postmodern has joined #cinch

22:21 djbkd has joined #cinch

22:46 djbkd has quit [Remote host closed the connection]

22:47 djbkd has joined #cinch