Perhaps it is worth making status reply "You must authenticate first!" when stuck at authentication stage of ZNC.
Connect to ZNC
/msg *status anything
No response.
Perhaps it is worth making status reply "You must authenticate first!" when stuck at authentication stage of ZNC.
1. Connect to ZNC
2. /msg *status anything
3. No response.
<!-- github-sync-id:261906764 -->
Presumably, "git" means a version of ZNC built from master. Would be good to know exactly which revision, though.
Presumably, "git" means a version of ZNC built from `master`. Would be good to know exactly which revision, though.
<!-- github-comment-id:334053420 -->
Isn't this impossible (without making some assumptions), since StatusPrefix can be changed per-user? One way to get around this would be to simply send a notice whenever something other than CAP, NICK, USER, or PASS is sent before login but that seems a little messy.
Isn't this impossible (without making some assumptions), since StatusPrefix can be changed per-user? One way to get around this would be to simply send a notice whenever [something other than CAP, NICK, USER, or PASS is sent before login](https://github.com/znc/znc/blob/master/src/Client.cpp#L196) but that seems a little messy.
<!-- github-comment-id:353704319 -->
Don't many IRCds already do this in the form of " You must register first"?
:server.name 451 * :You have not registered
Don't many IRCds already do this in the form of "<somenumeric> You must register first"?
```
:server.name 451 * :You have not registered
```
<!-- github-comment-id:353727907 -->
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.
Perhaps it is worth making status reply "You must authenticate first!" when stuck at authentication stage of ZNC.
What exactly is "git"?
Presumably, "git" means a version of ZNC built from
master. Would be good to know exactly which revision, though.Also, to what should ZNC reply with that message? And in which way?
I added in reproduction steps. git is just the version I tried it on, although it probably applies to any version
Oops, I meant to close #1422
Isn't this impossible (without making some assumptions), since StatusPrefix can be changed per-user? One way to get around this would be to simply send a notice whenever something other than CAP, NICK, USER, or PASS is sent before login but that seems a little messy.
Don't many IRCds already do this in the form of " You must register first"?