Kick reason is not sent correctly
/kick This is a long kick message
This results in the kick reason being "message" only. Probably something about the parameter handling in the kick user handler.
Encodings are now honored for both sending and receiving. Cleaned up encode/decode
stuff in the handlers and switched putCmd() et. al. to accepting (encoded) QByteArray only instead
Also fixed notices being shown in a separate buffer upon reconnect, and the kick message problem (BR #99).
Oh, and the default kick reason defined in your identity is used if appropriate now.