09:38 <blerrp> for options like messages_per_second, server_queue_size

09:38 <blerrp> it says 'Default value : Network dependent' in the docs

09:38 <blerrp> are they really determined dynamically?

09:39 <blerrp> by looking at the server messages upon connecting or something?

09:39 <blerrp> how i can i see what they're set at when a bot's running

09:39 <blerrp> (to help with deciding what to adjust them to)

09:41 <blerrp> *how can i see

13:27 <dominikh> you can just print the config values. @bot.config.something – and they're determined either by specific messages, or usually based on the network name.

13:57 <blerrp> i have a line m.reply @bot.config

13:57 <blerrp> and in there, i only see messages_per_second=nil, server_queue_size=nil

14:01 <dominikh> ah. right. dump @bot.irc.network instead. in particular, default_messages_per_second and default_server_queue_size

14:02 <blerrp> ty

14:02 <dominikh> actually, you have to dump these specifically, they're methods

14:03 <dominikh> https://github.com/cinchrb/cinch/blob/master/lib/cinch/network.rb#L78 – we don't exactly know about a lot of networks however

14:04 <blerrp> ahh

14:05 <blerrp> default_server_queue_size = sendQ?

14:05 <blerrp> guessing those are the same concepts

14:06 <blerrp> also interesting you have sendQ for quakenet but not freenode, and you have mps for freenode and not quakenet

14:06 <blerrp> lol

14:06 <dominikh> well, from the IRC server's point of view it's their recvq

14:07 <dominikh> but yeah, it boils down to the same concept

14:07 <dominikh> that code is old, so there's a non-zero chance that I just didn't specify freenode and quakenet respectively because their values match the default. there's no telling now.

14:07 <dominikh> maybe we just didn't have the information available

14:08 <blerrp> i don't think it's usually announced in the capability messages

14:09 <blerrp> have to determine experimentally

14:09 <dominikh> some mention it in documentation, which IIRC is where we got those values from. if they were announced, we sure as hell should've extracted that info

14:09 <dominikh> bbl

14:11 <blerrp> are there any helpers or something built in to help mitigate abuse

14:11 <blerrp> like users spamming commands

14:12 <blerrp> and eating up the bot's send capacity

14:12 <blerrp> or do you have to roll your own and put it on anything that sends a message

14:17 <blerrp> and if it's roll your own, do you have suggestions

14:30 <leftylink> the built-in functionality is noted at https://github.com/cinchrb/cinch/blob/master/lib/cinch/message_queue.rb#L5-L6

16:46 <dominikh> our ecosystem isn't really a thing… you'll have to implement most fancy things yourself. for rate limiting user commands you'll want to look into the "filter" feature for messages and into ruby mixins. that way you don't have to manually add the check to each handler, just mixin the filter stuff into each plugin class