ChanServ changed the topic of #cinch to: The IRC Framework | http://groups.google.com/group/cinch-ruby/ | Latest version: Cinch 2.0.4 – Change log at http://bit.ly/14Q4s6Z – Migration guide at http://bit.ly/GO4qkW | This channel is being publicly logged at http://irclog.whitequark.org/cinch/
postmodern has quit [Quit: Leaving]
v0n has joined #cinch
v0n has quit [Ping timeout: 255 seconds]
postmodern has joined #cinch
postmodern has quit [Quit: Leaving]
v0n has joined #cinch
v0n has quit [Ping timeout: 276 seconds]
v0n has joined #cinch
bean__ has joined #cinch
rickmasta has joined #cinch
rickmasta has quit [Quit: Leaving...]
rickmasta has joined #cinch
bean__ has quit [Quit: Computer has gone to sleep.]
rickmasta has quit [Quit: Leaving...]
bean__ has joined #cinch
bean__ has quit [Max SendQ exceeded]
bean__ has joined #cinch
bean__ has quit [Quit: Computer has gone to sleep.]
bean__ has joined #cinch
postmodern has joined #cinch
<waxjar> how would you guys go about persistent storage for a user? i can't come up with a reliable way of linking a user to–for example–a record in a database, because nicknames may have been changed in between "sessions"
cout has quit [Read error: Operation timed out]
cout has joined #cinch
rickmasta has joined #cinch
rickmasta has quit [Read error: Connection reset by peer]
[Rickmasta] has joined #cinch
<aytch> waxjar: you'd probably need to have some sort of nickserv-type authentication
waxjar has quit [Ping timeout: 264 seconds]
[Rickmasta] has quit [Quit: Leaving...]
<dominikh> User#authname if you want to rely on nickserv/Q/K and limit it to identified users
waxjar has joined #cinch
v0n has quit [Ping timeout: 264 seconds]
v0n has joined #cinch
bean__ has quit [Quit: Computer has gone to sleep.]
rickmasta has joined #cinch
v0n has quit [Ping timeout: 248 seconds]