When multiple my clients are connected, and I'm asking CTCP VERSION of someone else, I'm getting my another client's version, twice, in addition to response of the nick I wanted. Probably it has something to do with self-message cap.
For reference, my clients are WeeChat 1.7 and KVIrc 4.9.3 git:e2a7b9ec1c3c8c6. It could be a bug in both clients, not ZNC itself.
ZNC 1.7.x-git-878-d4ae3115, and I didn't check yet whether this affects 1.6.5.
When fixing this, need to also check that CTCP VERSION to myself triggers correct number of responses (one per client)
When multiple my clients are connected, and I'm asking CTCP VERSION of someone else, I'm getting my another client's version, twice, in addition to response of the nick I wanted. Probably it has something to do with `self-message` cap.
For reference, my clients are WeeChat 1.7 and KVIrc 4.9.3 git:e2a7b9ec1c3c8c6. It could be a bug in both clients, not ZNC itself.
ZNC 1.7.x-git-878-d4ae3115, and I didn't check yet whether this affects 1.6.5.
When fixing this, need to also check that CTCP VERSION to myself triggers correct number of responses (one per client)
<!-- github-sync-id:293815066 -->
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.
When multiple my clients are connected, and I'm asking CTCP VERSION of someone else, I'm getting my another client's version, twice, in addition to response of the nick I wanted. Probably it has something to do with
self-messagecap.For reference, my clients are WeeChat 1.7 and KVIrc 4.9.3 git:e2a7b9ec1c3c8c6. It could be a bug in both clients, not ZNC itself.
ZNC 1.7.x-git-878-d4ae3115, and I didn't check yet whether this affects 1.6.5.
When fixing this, need to also check that CTCP VERSION to myself triggers correct number of responses (one per client)