Update specs #540
Merged
Update specs #540
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Includes message formats for `CAP` and the new metadata spec.
Merged
Member
|
I don't think we should publish the metadata spec to the website until the issue of multiple caps has been resolved. My feeling is that we only need a single metadata cap to enable all spec functionality, rather than having a separate notify cap which (as currently written) only applies to users tracked with MONITOR. See also ircv3/ircv3-specifications#558 |
Member
|
ircv3/ircv3-specifications#559 is now merged along with ircv3/ircv3-specifications@3775504, resolving outstanding issues. TODO in this PR: update submodules and fix references to non-existent caps in registry. |
Member
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Includes message formats for
CAPand the new metadata spec.