asciilifeform: !q uptime
snsabot: asciilifeform: time since my last reconnect : 2d 13h 5m
phf: asciilifeform: http://p.bvulpes.com/pastes/6wcKt/?raw=true that's the CTCP action bits
asciilifeform: ty phf , makes sense
phf ... rest might be utf until you encounter a closing 0x1
asciilifeform: seems to me that 0x01 can't even occur in utf8 at all, so safe to lose'em entirely at the intake filter
phf: ah but then somebody typing
phf foo
phf: is equivalent to typing /me foo
asciilifeform: btw wb , phf
phf: eh
asciilifeform foo' == '/me foo' tho
phf: well, if you want to parse /me ctcp actions
phf 0x1 wrapped around it
asciilifeform: currently it's a barbaric regexp on 'ACTION' at start of payload
asciilifeform: seems like the 0x01 doesn't occur anywhere else, can match on it there and lose it
phf: right, exactly
phf: and it should only ever occur at the end of action string, unless the action was too long, so the 0x1 at the end will be cutoff. on irc protocol level.
phf: ok, hope that helps.
asciilifeform: it does, ty phf
asciilifeform: phf if yer back inbiz , plz can update http://btcbase.org/patches?patchset=m ? ty
asciilifeform: ( and http://btcbase.org/patches?patchset=ffa also, diana_coman posted buncha sigs )