Closed jaraco closed 8 years ago
Duplicate of #40.
Original comment by: Jason R. Coombs
This IRC library is opinionated about the default encoding, in particular that it's better to use a rich, preferred encoding and to fail when than assumption is violated rather than provide an imperfect decoding and silently pass. I'm confident in this opinion as this code is being used with the default decoder in many environments with great success. I recognize that others prefer a more lenient default decoding, which is why the decoder is supplied and documented in the readme.
Thanks for registering your concerns and sorry for any inconvenience.
Original comment by: Jason R. Coombs
Hey,
got another stacktrace:
Doesn't seem like there is any way for application layer (library consumer) to get ahold of this decoding error and handle it. Imho LenientLineDecodingBuffer should be used by default, or DecodingBuffer class to use should be made configurable. On IRC clients will send any kind of data, and a client shouldn't explode because of non-utf8 data sent.