dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.3.1
michae has left #cinch ["WeeChat 1.1.1"]
Azure has quit [Ping timeout: 264 seconds]
Azure has joined #cinch
Azure|dc has joined #cinch
Azure has quit [Ping timeout: 258 seconds]
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
Rickmasta has quit [Remote host closed the connection]
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Ping timeout: 260 seconds]
FiXato has joined #cinch
FiXato has quit [Ping timeout: 244 seconds]
FiXato has joined #cinch
FiXato has quit [Max SendQ exceeded]
FiXato has joined #cinch
FiXato has quit [Ping timeout: 244 seconds]
FiXato has joined #cinch
FiXato has quit [Ping timeout: 260 seconds]
FiXato has joined #cinch
NekkaLucifer has joined #cinch
<NekkaLucifer>
So this is a long-shot, but is there anyone here that has managed to make a Cinch bot with per-channel rate limiting
<leftylink>
NekkaLucifer: yeah, I have, works fine. I can't show the code for various reasons, but I just have an instance variable that's a hash where the k/v pairs are channel and time last command was issued on that channel. if time was too recent, reject command
<leftylink>
note that cinch already limits itself on how many messages it will send to a channel, but it's can still be useful to rate limit commands
<leftylink>
it's also possible to implement it as a hook if desired
<NekkaLucifer>
I was hoping to implement a message queue per channel and delay replies rather than rejecting