I am primarily thinking of global way to disable DCC like the current /znc *controlpanel addctcp $me DCC, but providers might like being able to advertise themselves in other CTCP replies.
I am primarily thinking of global way to disable DCC like the current `/znc *controlpanel addctcp $me DCC`, but providers might like being able to advertise themselves in other CTCP replies.
E.g. CTCP VERSION could give "%clientversion% via FreeZNCProvider https://znc.example.org/` (see also #1091)
- Debian GNU/Linux 7.9 (wheezy)
- ZNC 1.7.x-git-392-73d5f38 - http://znc.in
- IPv6: yes, SSL: yes, DNS: threads, charset: yes
##
<bountysource-plugin>
---
There is a **[$10 open bounty](https://www.bountysource.com/issues/26747654-global-ctcp-replies?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:106911231 -->
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 am primarily thinking of global way to disable DCC like the current
/znc *controlpanel addctcp $me DCC, but providers might like being able to advertise themselves in other CTCP replies.E.g. CTCP VERSION could give "%clientversion% via FreeZNCProvider https://znc.example.org/` (see also #1091)
- Debian GNU/Linux 7.9 (wheezy)
- ZNC 1.7.x-git-392-73d5f38 - http://znc.in
- IPv6: yes, SSL: yes, DNS: threads, charset: yes
--- There is a **[$10 open bounty](https://www.bountysource.com/issues/26747654-global-ctcp-replies?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).