If you set a custom ctcp reply and save then spam the user with ctcp it will eventually leak the real reply.
Example of the problem (spamming /ctcp version):
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION * Client CTCP Reply *
If you set a custom ctcp reply and save then spam the user with ctcp it will eventually leak the real reply.
Example of the problem (spamming /ctcp <username> version):
```
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION * Client CTCP Reply *
```
<!-- github-sync-id:42598242 -->
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.
If you set a custom ctcp reply and save then spam the user with ctcp it will eventually leak the real reply.
Example of the problem (spamming /ctcp version):
Was able to confirm on my live installation (running 1.5-nightly-20140509-3b01efc0).