dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.0.9
Spami has quit [Read error: Connection timed out]
Spami has joined #cinch
space_ has joined #cinch
rickmasta has quit [Quit: Leaving...]
Rick has joined #cinch
Rick is now known as Guest48528
kludge` has quit [Ping timeout: 248 seconds]
kludge` has joined #cinch
davidboy has quit [*.net *.split]
resure has quit [*.net *.split]
davidboy has joined #cinch
resure has joined #cinch
davidboy has joined #cinch
davidboy has quit [Changing host]
postmodern has quit [Quit: Leaving]
Spami has quit [Quit: This computer has gone to sleep]
space_ has quit [Ping timeout: 248 seconds]
space has joined #cinch
jonahR has joined #cinch
jonahR has quit [Quit: jonahR]
kludge` has quit [Ping timeout: 248 seconds]
kludge` has joined #cinch
leftylin1 has quit [Ping timeout: 252 seconds]
space has quit [Read error: Connection reset by peer]
space has joined #cinch
leftylink has joined #cinch
anternat has joined #cinch
v0n has quit [Ping timeout: 264 seconds]
v0n has joined #cinch
<nickrw> any idea why a cinch bot might get the case wrong for a user?
<dominikh> define "get the case wrong"
<nickrw> e.g. User('kevin').nick # => "Kevin"
<nickrw> authname is lower case too
<dominikh> probably because the first time we saw kevin, he was Kevin
<dominikh> not sure if he's named Kevin and renames himself to kevin it updates; it should tho
<nickrw> ah, that wouldn't update with #refresh?
<dominikh> we don't update the nick on #refresh. technically nicks are case insensitive
<dominikh> and it's not an information we need to acquire; that's like using an ID to get the ID
<nickrw> I would expect an actual nick change updates it, but I suspect the user has disconnected and reconnected
<nickrw> thanks
<dominikh> is it really a problem?
<nickrw> nah, I just need to make the rest of my code handle names case insensitively
<dominikh> keep in mind that IRC defines different case maps
<dominikh> String#downcase will often not be the right thing
<nickrw> oh?
<dominikh> if you do need to work with strings instead of User objects, there's String#irc_{down,up}case, which take a `mapping` argument, which can be obtained via @bot.irc.isupport["CASEMAPPING"]
* nickrw goes off to read RFC1459
Spami has joined #cinch
Spami has quit [Changing host]
Spami has joined #cinch
anternat has quit [Ping timeout: 252 seconds]
anternat has joined #cinch
anternat is now known as Guest63036
sacc91_ has quit [Quit: sacc91_]
sacc91 has joined #cinch
UberDragon has quit [Quit: UberDragon]
Guest63036 has quit [Ping timeout: 246 seconds]
leftylink has quit [Ping timeout: 252 seconds]
leftylink has joined #cinch
Spami has quit [Quit: Leaving]
rikai has quit [Read error: Connection reset by peer]
rikai has joined #cinch
v0n has quit [Ping timeout: 264 seconds]
v0n has joined #cinch
leftylink has quit [Ping timeout: 252 seconds]
leftylink has joined #cinch
leftylink has quit [Ping timeout: 245 seconds]
v0n has quit [Ping timeout: 272 seconds]
postmodern has joined #cinch