Forums Feature Suggestions Ignoring un-requested IRCv3 server tags

Apparently it's part of the IRCv3 specs that it's righteous for the server to keep sending you the @time server-time tag as part of the message-tags 'capability' in spite of having requested that the server-time capability be disabled. And the only way to keep from having other people's #channel messages showing timestamps from a different clock than your own messages is to disable message tags completely.

I'm finding this happening at both ircd test servers ...

irc.unrealircd.org
testnet.inspircd.org

... and everyone insists that they're faithfully following the IRCv3 specs, and they claim my client is broken.

Apparently, even though you can request that server time not be sent to you by "/raw CAP REQ -server-time", if the server has message-tags 'capability' enabled, the specs considers that it's righteous for the server to send the @time=servertime tag along with the @msgid and other tags, and that my client is broken because it's supposed to be my client's job to not use the server-time tag if it didn't request it. They were not impressed when I countered that they shouldn't ACK the -server-time and take it off my CAP LIST yet still send it at me, and that the client gives the user the ability to request and un-request things on its own, and that if the tag comes in, that the client assumes that the script must've requested it, because why else would the server be sending it?

So either mIRC will need to start snooping at all /parseline and /raw strings to see if the user tried to disable server-time, or there needs to be some kind of command that can be used in scripts or perform-on-connect to tell mIRC itself to ignore the @time tag being attached to incoming IRCv3 @tag strings.

Or, the only way to disable timestamps using a different clock depending on whether it's me vs everyone else, is to script something with ON PARSELINE:in: to intercept incoming messages to strip out the @time= tag or edit it into being the meaningless @zime= tag.

I tried to find out which other settings besides server-time would have this similar issue, where something is an a-la-carte thing that's LS-listed separately which you can decline, but is still put on your plate as part of the message-tags combo platter, but couldn't get an answer for that. Nor could I get an answer for why someone who had disabled the server-time capability would still want to receive them as part of message-tags.