/cap req -chghost Causes znc to think all cloaked users that identify to services after joining a channel are in ALL your attached, detached, and disabled channels, even though they might be only in one channel.
That fixed the detached channel, but the nick is still being sent into channels client side they are not actually in. ZNC told my client the nick joined #b and #c, even though it never actually happened.
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.
/cap req -chghostCauses znc to think all cloaked users that identify to services after joining a channel are in ALL your attached, detached, and disabled channels, even though they might be only in one channel.IRC Client side raw log:
I had handled detached channels, but forgot about disabled ones. Fixed.
Please test
That fixed the detached channel, but the nick is still being sent into channels client side they are not actually in. ZNC told my client the nick joined
#band#c, even though it never actually happened.Using
/msg *send_raw server KindOne foobar cap req -chghostfixed the issue and gets rid of thechghostboth client and znc side.Ah, of course