Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecate and eventually phase out CAP CLEAR #134
CAP CLEAR is of dubious utility to client authors and of very dubious utility to users. It is not desirable that features be able to be turned off (just do not request CAPs you do not want), and may in fact harm user experience by being in the spec - it just screams "don't push this button" to anyone who comes across reading it. It also is limited in utilty by sticky caps, which cannot be removed once requested.
The only use case that even came up in discussion in #ircv3 was for bouncers - but servers cannot even send CAP CLEAR, making it useless for even this purpose. A well-written bouncer should be able to translate caps, anyway, or mandate them if needs be.
Anecdotally, the only reason I can find that it's even in the spec was apparently because in the past, it was desirable to demonstrate that everything was optional and could be turned off at any time for political reasons. Such political reasons have long since passed, as CAP is now a thing of the present and implemented by most major clients - sans CAP CLEAR in any of them known to me :).
…pointer to the errata bug closes ircv3#134