draft/account-registration: should all responses use standard-replies? about ircv3-specifications HOT 2 OPEN

Ergo is correct in this case because "Servers which support this capability SHOULD NOT replace standardised error numerics with standard replies, unless the replacement is explicitly described by some other specification.", from the Standard Replies specification. The Account Registration spec doesn't mention a FAIL code for lack of required params, so Ergo is correct in this case.

from ircv3-specifications.

I agree with @ValwareIRC's interpretation of the specification, but also I think issues like this come up regularly and there's actually not that much at stake here, because the error condition here is a programming error, not a runtime error. It's important to have clear specifications for runtime errors, because clients need to handle them at runtime (in the context of this specification, FAIL REGISTER ACCOUNT_EXISTS is a good example). But there's no way to "handle" 461 ERR_NEEDMOREPARAMS or an equivalent FAIL code --- it's a client code bug and the only solution is to fix the code.

I'm curious what FAIL code Unreal is sending, and whether it's in the registry? But I don't think it's a correctness issue either way, since there's no correct way for client code to make use of the response.

from ircv3-specifications.