00:20 <Lite> hmm

00:20 <Lite> I wonder how much work it would be to port my card games from rbot to cinch.

00:21 <dominikh> can't answer that

00:21 <dominikh> depends on how much of rbot specific features you use

00:22 <Lite> I used the rbot registry to keep track of players' high scores.

00:23 <dominikh> you'll need to implement your own persistent storage

00:23 <Lite> ok

00:23 <dominikh> even though DonovanYoung worked on something for that

00:23 <Lite> Any recommendations on where to start? Maybe another plugin for cinch that does it well on its own?

00:25 <dominikh> basic persistent storage is easy if you use sqlite and whatever driver/ORM you fancy

00:27 <Lite> I really like using key-based storage over tables, so I might just whip something up in kyotocabinet or just make a yaml file I suppose.

00:27 <dominikh> sure, or that. https://github.com/achiu/cinch-memo uses redis

00:28 <Lite> My plugins dump everything to rbot's registry hash, so it would be less rewriting that way I think.

00:28 <Lite> thanks

00:28 <Lite> I'll look into this

00:30 <Lite> Also, is there a centralized location where people contribute plugins or snippets? I'm sure a lot of my plugins aside from the game already exist in one form or another.

00:30 <Lite> games*

00:31 <dominikh> there used to be, but eh. you can use http://rubygems.org/search?query=cinch- though

00:32 <Lite> alright

00:32 <Lite> I think I'm good with questions for now.

00:33 <dominikh> cool. if there's more, you know where we are

00:33 <Lite> not sure why you are on irc anwering questions on Christmas, but thanks

00:34 <txdv> dominikh: can you give me a pointer on how you create a inclass method like match which somehow gets a reference to the next defined method?

00:34 <Lite> and if anybody wants any snippets for card games for cinch I've made tons that I can port

00:34 <dominikh> Lite: in Germany, the major part of christmas with family and gifts etc happens on the 24th

00:34 <Lite> ah, yeah

00:34 <Lite> didn't think about that

00:34 <dominikh> (also I really don't care much for Christmas ;))

00:35 <dominikh> txdv: that'd be a decorator; but Cinch's match has no idea about the next method you define. match either defaults to a method called execute, or expects you to give it the method name.

00:35 <dominikh> txdv: anyway, google for ruby + decorator pattern. even though in ruby 2.1 there's a new way to implement them

00:36 <txdv> thanks

00:38 <txdv> if I match against /func .../ it will invoke the method func in the plugin?

00:38 <dominikh> what? no.

00:38 <dominikh> look at the examples.

00:54 <txdv> o yeah, i'm blind, i provide the method name

00:55 <txdv> and I thought I just can get the next defined method name somehow magically

00:55 <dominikh> there are ways; none of which Cinch will ever make use of :)

00:56 <txdv> they all overload an operator like +

00:58 <dominikh> https://github.com/dominikh/keyword_arguments/blob/master/lib/keyword_arguments.rb

00:58 <dominikh> that there is a years old library of mine that uses the decorator pattern.

01:00 <dominikh> you simply overwrite the method_added/singleton_method_added methods

01:00 <txdv> thanks ill look into it

03:49 <mlipienski> hi, I'm new to cinch. I have two plugins that share some data, I'm making that data available to each other thru a class variable. I'm wondering whether this is the right way to do it, is there a better way or I'm doing something really messy?!

03:55 <dominikh> well, class variables are wrong as soon as you want to run multiple instances of the plugin in a single ruby process (e.g. when running multiple bots)

03:56 <dominikh> you can use instance variables and use the plugin_list to find the concrete instance, you can use the `shared` helper (which is a bot-global shared hash), you can use an event driven way of exchanging data if that makes sense for your use case, and there are probably other ways as well

03:56 <dominikh> depends on what you're actually sharing the data for

04:00 <mlipienski> oh so many options, I guess I should dive into the documentation. thanks for your help dominikh

04:01 <dominikh> fwiw, `shared` isn't documented. it's not officially part of Cinch because I haven't decided whether to keep it yet or not

12:34 <txdv> metaprogramming is brainfuck

12:57 <txdv> dominikh: your keywords_arguments does more than decorate a method

12:57 <txdv> it intercepts all the calls

12:57 <txdv> which is a nice

14:32 <dominikh> that's the point of the decoration. it's a wrapper, a poor man's advice

14:43 <txdv> I wanted to do something different! Call a decorator on intatiation of a class with the class instance and method information

14:44 <txdv> the interception could be a nice feature too

15:17 <dominikh> ... on instantiation? that's what the initialize method is for

16:04 <cout> txdv: I didn't realize brainfuck had metaprogramming support

20:02 <ColdBlooder> Hi, how can i ban users with cinch?

20:03 <dominikh> http://rubydoc.info/search/gems/cinch?q=ban

20:03 <Cinchy> [URL] — Documentation for cinch (2.0.10)

20:16 <somasonic> Cinchy, ban ColdBlooder

20:16 <dominikh> eh?

20:17 <somasonic> Cinchy, ban dominikh

20:18 <dominikh> we can ban you instead if you want.

20:18 <somasonic> Cinchy, ban somasonic

20:18 <somasonic> :[

20:18 <txdv> what does Cinchy do?

20:18 <dominikh> bunch of stuff.

20:25 <ColdBlooder> Channel("#channel").ban (mask) is supposed to ban someone from a channel, right?

20:25 <dominikh> yes

20:26 <ColdBlooder> I get an error message though.

20:27 <ColdBlooder> http://pastebin.com/cDUfYwSn

20:27 <txdv> is there a way toget the channel from an m?

20:27 <dominikh> ColdBlooder: what's the mask you're passing it

20:28 <txdv> match /join/, method: join; def join(m, ...)

20:28 <ColdBlooder> username, dominikh

20:28 <dominikh> txdv: http://rubydoc.info/gems/cinch/Cinch/Message

20:28 <Cinchy> [URL] Class: Cinch::Message — Documentation for cinch (2.0.11)

20:28 <dominikh> ColdBlooder: that's not a valid mask.

20:28 <ColdBlooder> -/mode +b <username> usually works well

20:29 <dominikh> then your client expands it to a proper mask

20:29 <ColdBlooder> oh

20:29 <dominikh> nick!user@host

20:29 <dominikh> with * and ? for wildcards

20:29 <ColdBlooder> Using hostname should work?

20:29 <ColdBlooder> ah no

20:29 <ColdBlooder> so for example

20:30 <dominikh> (also I am pretty sure that that /mode +b <username> does NOT work. maybe with nickname instead of username

20:31 <ColdBlooder> Idiot001@100-100-100-100.mystupidprovider.com <-- mask for single user called Idiot001 (for example)