Handle messages that are terminated with '\n' instead of '\r\n'

[424ever]

The IRC Server of osu! sends QUIT messages that are terminated with \n instead of \r\n, which causes parsing to fail.

[424ever]

I think the splitting in codec.rs doesn't quite work how I wrote it, I'll change it later today

[tarkah]

Irc docs specifically state use of cr/lf, not lf on it's own.

https://modern.ircdocs.horse/#message-format

I'm afraid of the unintended consequences this change would cause. Why does this server not use carriage return?

[424ever]

I'm afraid of the unintended consequences this change would cause.

I understand that this doesn't follow the specification, but since this pattern being supported by most irc implementations I've checked, I suspect it wouldn't cause any issues.

• node-irc
• the irc-proto crate
• HexChat (this one looks like it might be accidental, to be fair)

As seen in the node-irc pr, rfc1459 also recommends splitting messages on different line endings instead of requiring CR-LF.

Why does this server not use carriage return?

This server is primarily used as the in-game chat, and the lead developer has previously said that adhering to the specification and supporting specific clients is not a priority