22:55 <qb> why is it that user.mask returns and out of date mask

23:06 <qb> having a problem now where a user can get banned and return and the bot thinks their current mask is their previous mask

23:07 <qb> so they can't ban again

23:11 <dominikh> you'll need to explicitly User#refresh the user I'm afraid

23:11 <dominikh> I wonder if we should update the host more often; right now it's set the first time we see it and cleared on quit/kill

23:12 <dominikh> maybe we should set the host every time we see the host

23:12 <dominikh> (especially because User#refresh is expensive)

23:17 <qb> I'm using the bot on rizon where they limit .whois

23:18 <qb> but really why does there need to be a whois?

23:18 <qb> the bot shows the correct mask in the debug when the user joins and sends a message

23:18 <qb> but when getting user.mask it shows an older one

23:19 <qb> is there a way to get it to update when someone joins without using whois?

23:19 <dominikh> I just explained to you why. We only update the internally stored host on specific events; and the only way to fix that is by changing Cinch

23:21 <qb> ah sorry

23:21 <qb> hmm

23:21 <qb> well this is going to be a problem

23:22 <dominikh> I'd say it's a bug in Cinch that we should fix

23:34 <dominikh> qb: I'll suggest a patch in a couple minutes that should help.

23:35 <qb> kk

23:36 <dominikh> qb: are you on master or the release version (2.0.9)?

23:37 <qb> release

23:58 <dominikh> qb: you can build from the maint-fix-user-updating branch in git (https://github.com/cinchrb/cinch/tree/maint-fix-user-updating) which should have a working fix