CTCP VERSION response handling about thelounge HOT 6 CLOSED

Don't know that my own opinion holds any weight, but my preference are (in descending order):

1. An option in config.js to turn CTCP off
2. Just don't support CTCP at all; kill it with 🔥
3. A checkbox when adding a server connection to enable or disable, since allegedly there are some servers that check client versions...even though the value is trivially spoofable.

from thelounge.

1. ZNC has supported overriding the VERSION string (or any other CTCP response) for ages. In your own words, "nobody died" from that either.

2. Some IRC networks require that clients respond to VERSION requests.
   What happens to TL users on one of these networks if the VERSION response is completely removed? They can be banned at any time, at the discretion of network staff, for policy violation.

That said, (1) is just a minor point of interest. Only (2) will affect me, because TL has replaced my old ZNC install and at least one network I use daily has "clients must respond to VERSION" as one of its rules.

If you want to make VERSION replies opt-in and have TL ignore those requests by default, that's great, as long as the user can turn it back on (as a per-network setting?) if required.

from thelounge.

I guess to keep aligned with RFC and IRC standards it's a good practice to keep the option, and allow the final user to enable or disable the reply, even customize or modify the default CTCP VERSION REPLY.

from thelounge.

Just my 2 cents: we can start by removing the version number from the response, without adding any options to show/hide it. This shouldn't break anyone.

from thelounge.

doesn't break anyone but as stated above also has no benefit. Makes the version response mostly useless at which point we can just send nothing

from thelounge.

I agree with xPaw.

also has no benefit

There's still the user's client, which might have value to someone.

from thelounge.