I mentioned this in #znc, but my setup with ZNC is where I have my main bouncer, and this chains onto another ZNC instance not under my control. However, the connection to other ZNC instances (and possibly other bouncers too) does not have support for IRCv3 capabilities in the ZNC codebase.
I suspect this might fix an old bug from 2018 I commented on (#1269), and I am looking into IRCSock.cpp currently for ideas, but could do with guidance on getting a PR in for fixing this issue.
Thank you :)
I mentioned this in #znc, but my setup with ZNC is where I have my main bouncer, and this chains onto another ZNC instance not under my control. However, the connection to other ZNC instances (and possibly other bouncers too) does not have support for IRCv3 capabilities in the ZNC codebase.
I suspect this _might_ fix an old bug from 2018 I commented on (#1269), and I am looking into `IRCSock.cpp` currently for ideas, but could do with guidance on getting a PR in for fixing this issue.
Thank you :)
<!-- github-sync-id:2855650033 -->
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 mentioned this in #znc, but my setup with ZNC is where I have my main bouncer, and this chains onto another ZNC instance not under my control. However, the connection to other ZNC instances (and possibly other bouncers too) does not have support for IRCv3 capabilities in the ZNC codebase.
I suspect this might fix an old bug from 2018 I commented on (#1269), and I am looking into
IRCSock.cppcurrently for ideas, but could do with guidance on getting a PR in for fixing this issue.Thank you :)