I've compiled ZNC 1.11.x-git-5-7e5a2673 and tested it on my server, all works fine. but by the message-tags can't send the typing message to the server. When a another user (not on znc) is the typing message for me as znc user availabe.
I've compiled ZNC 1.11.x-git-5-7e5a2673 and tested it on my server, all works fine. but by the message-tags can't send the typing message to the server. When a another user (not on znc) is the typing message for me as znc user availabe.
<!-- github-sync-id:3165329586 -->
I've just tried to connect to this server, and this works:
```
[2025-06-22 11:43:02.116067] (qwe/midiandmore) CLI -> ZNC [@+typing=active TAGMSG #dgtest]
[2025-06-22 11:43:02.116368] (qwe/midiandmore) ZNC -> IRC [@+typing=active TAGMSG #dgtest]
```
Maybe one of modules you loaded strips it?
<!-- github-comment-id:2994115731 -->
If you pastebin your znc.conf, I can try to test with it, just remove passwords and list of channels for privacy
Or you can check if clean config fixes it, and if it does, search which setting is at fault
If you pastebin your znc.conf, I can try to test with it, just remove passwords and list of channels for privacy
Or you can check if clean config fixes it, and if it does, search which setting is at fault
<!-- github-comment-id:2994137065 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I've compiled ZNC 1.11.x-git-5-7e5a2673 and tested it on my server, all works fine. but by the message-tags can't send the typing message to the server. When a another user (not on znc) is the typing message for me as znc user availabe.
please show logs of
znc -D(except for passwords, of course), starting from CAP or earlierI think that the message tag was not redirected to the server, but the server supports that.
Here the outgoing typing messages:
[2025-06-21 19:15:13.372486] (WarPigs/midiandmore) CLI -> ZNC [@+typing=active TAGMSG #Skibidi.Bop.mm.DADA][2025-06-21 19:15:17.254429] (WarPigs/midiandmore) CLI -> ZNC [@+typing=active TAGMSG #Skibidi.Bop.mm.DADA][2025-06-21 19:15:17.938440] (WarPigs/midiandmore) CLI -> ZNC [PRIVMSG #Skibidi.Bop.mm.DADA :testmsg][2025-06-21 19:15:17.938553] (WarPigs/midiandmore) ZNC -> IRC [PRIVMSG #Skibidi.Bop.mm.DADA :testmsg][2025-06-21 19:15:20.268456] (WarPigs/midiandmore) CLI -> ZNC [@+typing=done TAGMSG #Skibidi.Bop.mm.DADA]Here the ingoing typing messages:
[2025-06-21 19:22:56.413056] (WarPigs/midiandmore) IRC -> ZNC [@+draft/typing=active :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:56.413145] (WarPigs/midiandmore) ZNC -> CLI [@+draft/typing=active;time=2025-06-21T19:22:56.413Z :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:56.413193] (WarPigs/midiandmore) IRC -> ZNC [@+typing=active :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:56.413217] (WarPigs/midiandmore) ZNC -> CLI [@+typing=active;time=2025-06-21T19:22:56.413Z :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:56.413288] (DevPigs/midiandmore) IRC -> ZNC [@+draft/typing=active :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:56.413401] (DevPigs/midiandmore) IRC -> ZNC [@+typing=active :Source!S@urce TAGMSG #coolchat][2025-06-21 19:22:57.808038] (WarPigs/midiandmore) IRC -> ZNC [:Source!S@urce PRIVMSG #coolchat :hallo][2025-06-21 19:22:57.808120] (WarPigs/midiandmore) ZNC -> CLI [@time=2025-06-21T19:22:57.808Z :Source!S@urce PRIVMSG #coolchat :hallo]I said, starting from CAP.
Can you show full log, not just TAGMSG itself?
ok ,i started a second instance of znc to debug on that will it work without problems...
So i'm showing the log from the CAPs...
I've just tried to connect to this server, and this works:
Maybe one of modules you loaded strips it?
that are the loaded modules...
If you pastebin your znc.conf, I can try to test with it, just remove passwords and list of channels for privacy
Or you can check if clean config fixes it, and if it does, search which setting is at fault
Here is the pastebin:
znc.conf
I had to remove sasl module, because this was happening:
But without sasl it works: https://bpa.st/IISQ
(and please fix SASL on your server - failing one mechanism shouldn't fail the whole connection)
So, i'm fixed SASL on my server. But when i remove the SASL, the issue is still there....
Can you try this patch and show what happens? https://bpa.st/ALQQ
It shows following
Thanks, I've managed to reproduce this
Thx, it works :)