Skip to content
This repository was archived by the owner on Jun 6, 2021. It is now read-only.

CAP CLEAR and client->server CAP ACK are no longer valid#172

Open
jesopo wants to merge 1 commit intofreenode:masterfrom
jesopo:master
Open

CAP CLEAR and client->server CAP ACK are no longer valid#172
jesopo wants to merge 1 commit intofreenode:masterfrom
jesopo:master

Conversation

@jesopo
Copy link

@jesopo jesopo commented Jun 26, 2019 •
edited
Loading

https://ircv3.net/specs/core/capability-negotiation#errata

Previous versions of this specification referred to a CAP CLEAR command, which has been removed because it is not useful. We do not recommend implementing or supporting CAP CLEAR. See issue #134 for more information, including rationale for this clarification.

Previous versions of this spec listed that CAP ACK could be sent from the client to server, for capabilities that required extra client acknowledgement. This was removed since cap modifiers have been deprecated and removed (except for -, which has been specified in other ways).

@jesopo
Copy link
Author

jesopo commented Jun 26, 2019

CAP CLEAR has already been removed from charybdis charybdis-ircd/charybdis@ceabbbb

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jesopo