echo-message delay before msg appears/sent.
Hi, I notice a small delay after I type the msg and press enter, the line goes black for few ms before it appears in chan/query, was that done on purpose? It is possible to disable the delay completely? That's the only reason I keep echo-message disabled and I still use a script for znc.in/self-message.
I get it but... in decades of IRC I never once had the issue that a msg wasn't delivered, why the need to double check that with delays and responses? Is there a way to remove the delay completely? Not sure I will ever use echo-message until it feels normal.
Sry I edited at the last second yeah. I think echo-message was made exactly as an IRCv3 replacement for znc.in/self-message.
edit: mIRC just integrated echo-message in the latest beta and K said the gray delay was intentional to show the msg was delivered, that's why I was asking to remove that delay completely, who cares about the server response, IRC msgs always go through anyway.
edit2: Btw, I am testing echo-message on HexChat (https://github.com/hexchat/hexchat/discussions/2701) and there is absolutely 0 delay. There is one more thing to fix for double messages printed but once that's done I think I'll keep it enabled there.
Updated by Per Amundsen 7 months ago
"The capability is useful for clients to get an acknowledgement that a message was delivered. It can be also used for measuring lag between client and server, that is, the time it takes from sending a message to receiving it back."
So this is a new use case, but I'll think about shat can be done.
Talking about this, how hard would it be to integrate znc.in/self-message (https://defs.ircdocs.horse/info/selfmessages.html) in the client instead of using a script? It's just a request for a CAP on connect no? I bet thousands of people use a ZNC why no one is bothered by the double queries?