don't require account-notify/away-notify for WHOX #1793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when you connect weechat to znc, you first get a
CAP
dance like this:and then once znc has figured out what network you're connecting to, you get this:
and then it takes until after znc has already finished replaying
NAMES
to you for you to get thiswhich means by the time you're hitting the code that I'm changing, you don't know that the network you're on supports
away-notify
oraccount-notify
, which means thisif
will reliably fail and weechat simply won't send a WHOX request. this can be solved by simply sending WHOX whenever a network supports it.