00:55 <Paradox> hey dominikh, my bots all seem to be throwing a lot of errors regarding user AWAY messages

00:55 <Paradox> http://pastebin.com/fd0AWVhx

00:56 <dominikh> Paradox: one sec

00:56 <Paradox> its on snoonet, #reddit

00:56 <Paradox> irc.snoonet.org

00:56 <dominikh> weird, must've forgotten to release a version for that. if you build from git, it's fixed

00:56 <dominikh> will release 2.1.1 once I boot my dev system

00:56 <Paradox> alright

00:56 <Paradox> i'll do a git pull

00:57 <Paradox> does…uh…the git version have oper and sanitize?

00:57 <Paradox> they are in the docs but nonfunctional in 2.1.0

00:57 <Paradox> well…sanitize works but it whines about being private

00:57 <dominikh> what's "sanitize"? and oper should work just fine.

00:58 <Paradox> idk, i've seen it mentioned a few times throughout your changelogs/readmes, but ideally some simple way to strip color codes from messages for processing

00:59 <Paradox> oh my mistake, its called filter_string or strip_colors

01:00 <dominikh> huh, when did those become private

01:00 <dominikh> oh, have been forever. odd.

01:01 <Paradox> yeah, i wanted to use them in a bot that announces reddit posts

01:01 <dominikh> guess I'll have to change that, too

01:01 <Paradox> but it kept yelling at me so i just C+P code

01:01 <Paradox> lol

01:01 <dominikh> a) there's nobody to yell at you but the docs, they're not private in the ruby sense

01:01 <dominikh> only documented as private

01:01 <dominikh> b) there's the #safe_* methods for sending messages, those use filter_string on the argument

01:01 <Paradox> huh, well i wasnt sure of the official stauts

01:02 <Paradox> and yeah, those work for outgoing messages, but if you use Format anywhere it removes it

01:02 <dominikh> true

01:02 <dominikh> I'll remove the private tag later

01:02 <Paradox> cool

01:02 <dominikh> but you can already just use them

01:02 <Paradox> so i can freely use string.filter…

01:02 <Paradox> that will clean up some code later

01:02 <Paradox> thanks

01:02 <dominikh> Cinch::Utilities::String.filter_string, yeah

01:03 <dominikh> actually, considering they're private right now and filter_string as a name bugs me, I'll rename that method to filter

01:03 <dominikh> or sanitize or something like that..

01:03 <Paradox> sanitize is what rails would call it

01:03 <Paradox> ie h()

01:03 <dominikh> yeah

01:03 <Paradox> aliased as sanitize

01:04 <dominikh> okay, will release 2.1.1 later that fixes the AWAY bug, and somewhen after that 2.2.0 which will make the string utilities public and rename filter_string

01:06 <Paradox> also, this isn't really something you have to worry about, something I need to eventually fix on snoonet

01:07 <Paradox> but, if a channel has some replay mode cinch freaks out about it

01:07 <Paradox> i.e. in InspIRCD, we have +H, which shows a per-channel configurable history, bracketed by start-and-end notices

01:07 <Paradox> which causes the sync to freak out because its getting messages from users that may not be there anymore

01:07 <Paradox> again, not something *you* need to worry about, just letting you know

01:08 <dominikh> mhm

01:08 <dominikh> maybe one day IRCv3 will have an official extension for replays, then we can implement that

01:08 <Paradox> well, the patch i'm working on for INSP is to make it not send replays to +B users

01:08 <Paradox> +B being bot-mode

01:08 <dominikh> sounds like a good idea.

01:09 <Paradox> problem is my C++ is janky

01:09 <Paradox> yeah git head fixes the away spam dominikh

01:09 <Paradox> thanks

01:09 <dominikh> no problem