Last line character cut off using netcat - is this some \n vs \r\n issue?

[ghost]

Describe the bug
When connecting via netcat, the last input character is cut off. With telnet it works. Do you hardcode-assume \r\n and cut off a character when a line just terminates in \n? I get that this is what most telnet clients would send, but IMHO you should still be flexible with this on the input side even when strict with it on the output side.

To Reproduce
Connect via netcat, enter account name -> suggested name has last character cut off

Expected behavior
All types of line breaks are processed correctly. You may also want to treat single \r as a correct line break for robustness (even if it's not followed by \n).

Error logs
No idea, don't have server access to this instance

Environment (please complete the following information):
Again no idea

Additional context
Add any other context about the problem here.

[Akeri]

Same issue here.
However using telnet is ok