While ZNC can be easy for someone who has been using it for year, for a new person, its rather confusing, as the help command is rather limited.
Currently with services, a user can "/msg NickServ help register" and see a rather verbose wall of text explaining what to do. I am suggesting doing the same thing for ZNC.
Possibly store the content in separate files like "help/autoop/adduser" for "/msg *autoop help adduser", so that when the help content is changed, the module does not have to be recompiled (Atheme Services does this).
While ZNC can be easy for someone who has been using it for year, for a new person, its rather confusing, as the help command is rather limited.
Currently with services, a user can "/msg NickServ help register" and see a rather verbose wall of text explaining what to do. I am suggesting doing the same thing for ZNC.
Possibly store the content in separate files like "help/autoop/adduser" for "/msg *autoop help adduser", so that when the help content is changed, the module does not have to be recompiled (Atheme Services does this).
<!-- github-sync-id:11639689 -->
/znc help jump
2015-09-09 17:03:14+0300 < *status> ------
2015-09-09 17:03:14+0300 < *status> Command: JumpNetwork <network>
2015-09-09 17:03:14+0300 < *status> Description: Jump to another network (Alternatively, you can connect to ZNC several times, using `user/network` as username)
2015-09-09 17:03:14+0300 < *status> ------
2015-09-09 17:03:14+0300 < *status> Command: Jump [server]
2015-09-09 17:03:14+0300 < *status> Description: Jump to the next or the specified server
2015-09-09 17:03:14+0300 < *status> ------
I think this can be closed?
```
/znc help jump
2015-09-09 17:03:14+0300 < *status> ------
2015-09-09 17:03:14+0300 < *status> Command: JumpNetwork <network>
2015-09-09 17:03:14+0300 < *status> Description: Jump to another network (Alternatively, you can connect to ZNC several times, using `user/network` as username)
2015-09-09 17:03:14+0300 < *status> ------
2015-09-09 17:03:14+0300 < *status> Command: Jump [server]
2015-09-09 17:03:14+0300 < *status> Description: Jump to the next or the specified server
2015-09-09 17:03:14+0300 < *status> ------
```
I think this can be closed?
<!-- github-comment-id:138918597 -->
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.
While ZNC can be easy for someone who has been using it for year, for a new person, its rather confusing, as the help command is rather limited.
Currently with services, a user can "/msg NickServ help register" and see a rather verbose wall of text explaining what to do. I am suggesting doing the same thing for ZNC.
Possibly store the content in separate files like "help/autoop/adduser" for "/msg *autoop help adduser", so that when the help content is changed, the module does not have to be recompiled (Atheme Services does this).
I think this can be closed?