So, I've had this itty bitty little issue with my client (KVIrc 5.2.6) constantly sending /WHO commands, and its a little annoying. I looked into the settings of my client, and it says it doesn't need to send /WHOs if the server supports cap :away-notify. I connect to Libera.Chat, which does support it, but connecting the client to the znc server, it doesn't send away-notify as a capability.
Strangely, after connecting, and sending cap ls myself, it then shows a full list of server capabilities.
If I'm doing something wrong, please tell me, I know its not really a big deal, but its a little inconvenient for me, thanks.
And yes, corecaps is loaded already.
So, I've had this itty bitty little issue with my client (KVIrc 5.2.6) constantly sending /WHO commands, and its a little annoying. I looked into the settings of my client, and it says it doesn't *need* to send /WHOs if the server supports cap :away-notify. I connect to Libera.Chat, which does support it, but connecting the client to the znc server, it doesn't send away-notify as a capability.
<img width="1220" height="125" alt="Image" src="https://github.com/user-attachments/assets/17c84b63-b60d-41eb-8264-9d15dcf1075c" />
Strangely, after connecting, and sending `cap ls` myself, it *then* shows a full list of server capabilities.
<img width="1200" height="54" alt="Image" src="https://github.com/user-attachments/assets/bf77c924-0a22-4c8e-ad44-d82da8e739a3" />
If I'm doing something wrong, please tell me, I know its not really a big deal, but its a little inconvenient for me, thanks.
And yes, corecaps is loaded already.
<!-- github-sync-id:3506423462 -->
Some capabilities (e.g. away-notify) rely on server to support them, where ZNC cannot emulate them itself.
During connect to ZNC, before the login, ZNC doesn't know yet which network you're going to attach to, so can only offer caps which don't rely on server. But after login, it knows the server, so can offer it.
The solution for this is to support cap-notify on client. With cap-notify on, ZNC will send the additional caps to client upon login.
Some capabilities (e.g. away-notify) rely on server to support them, where ZNC cannot emulate them itself.
During *connect* to ZNC, before the login, ZNC doesn't know yet which network you're going to attach to, so can only offer caps which don't rely on server. But after login, it knows the server, so can offer it.
The solution for this is to support `cap-notify` on client. With cap-notify on, ZNC will send the additional caps to client upon login.
<!-- github-comment-id:3393715819 -->
Some capabilities (e.g. away-notify) rely on server to support them, where ZNC cannot emulate them itself.
During connect to ZNC, before the login, ZNC doesn't know yet which network you're going to attach to, so can only offer caps which don't rely on server. But after login, it knows the server, so can offer it.
The solution for this is to support cap-notify on client. With cap-notify on, ZNC will send the additional caps to client upon login.
> Some capabilities (e.g. away-notify) rely on server to support them, where ZNC cannot emulate them itself.
>
> During _connect_ to ZNC, before the login, ZNC doesn't know yet which network you're going to attach to, so can only offer caps which don't rely on server. But after login, it knows the server, so can offer it.
>
> The solution for this is to support `cap-notify` on client. With cap-notify on, ZNC will send the additional caps to client upon login.
so i took a peek at https://ircv3.net/specs/extensions/capability-negotiation.html, and it turns out kvirc does not support `cap-notify`, thanks for the help
<!-- github-comment-id:3393717283 -->
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.
So, I've had this itty bitty little issue with my client (KVIrc 5.2.6) constantly sending /WHO commands, and its a little annoying. I looked into the settings of my client, and it says it doesn't need to send /WHOs if the server supports cap :away-notify. I connect to Libera.Chat, which does support it, but connecting the client to the znc server, it doesn't send away-notify as a capability.
Strangely, after connecting, and sending
cap lsmyself, it then shows a full list of server capabilities.If I'm doing something wrong, please tell me, I know its not really a big deal, but its a little inconvenient for me, thanks.
And yes, corecaps is loaded already.
Some capabilities (e.g. away-notify) rely on server to support them, where ZNC cannot emulate them itself.
During connect to ZNC, before the login, ZNC doesn't know yet which network you're going to attach to, so can only offer caps which don't rely on server. But after login, it knows the server, so can offer it.
The solution for this is to support
cap-notifyon client. With cap-notify on, ZNC will send the additional caps to client upon login.This should be added to FAQ
so i took a peek at https://ircv3.net/specs/extensions/capability-negotiation.html, and it turns out kvirc does not support
cap-notify, thanks for the help