Project

General

Profile

Actions

Feature #5567

open

echo-message delay before msg appears/sent.

Added by eahm eahm almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/03/2022
Due date:
% Done:

0%

Estimated time:
Operative System:
All

Description

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.

Thanks.

Actions #1

Updated by Per Amundsen almost 2 years ago

Yes this is intended, when echo-message is enabled, local messages are not shown, instead you see the reply from the server.

Actions #2

Updated by eahm eahm almost 2 years ago

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.

Actions #3

Updated by Per Amundsen almost 2 years ago

The whole point of echo-message is to be notified that the message was sent correctly, if you don'r care about that, there is no reason to enable echo-message.

It's a pretty useless feature which is why it's off by default.

Actions #4

Updated by eahm eahm almost 2 years ago

I'm only interested in it because I like minimalism and with it enabled I wouldn't need the script for znc.in/self-message but yeah I get that too, it's not a big deal at all, trying to ask to fix the unfixable.

Actions #5

Updated by Per Amundsen almost 2 years ago

I don't quite get the connection with znc self-message, can you explain what exactly you are trying to archive?

Actions #6

Updated by eahm eahm almost 2 years ago

znc.in/self-message makes sure you will see your nick and msgs as well as the other's in queries after you reconnect to a znc and load the buffer. Without that you only see the other person's nick and msgs.

echo-message does all that on its own.

Actions #7

Updated by Per Amundsen almost 2 years ago

I see, how does echo-message come into play?

Actions #8

Updated by Per Amundsen almost 2 years ago

Oops didn't see the last line, that explains it.

I'll think about this use case.

Actions #9

Updated by eahm eahm almost 2 years ago

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.

Actions #10

Updated by Per Amundsen almost 2 years 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.

Actions #11

Updated by eahm eahm almost 2 years ago

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?

Actions #12

Updated by Per Amundsen almost 2 years ago

I don't really understand the question, but for znc specific features, you'll have to use scripts.

Actions #13

Updated by eahm eahm almost 2 years ago

I see, I tried, thanks man.

Actions

Also available in: Atom PDF