Deprecate metadata-3.2 for the time being.#279
Merged
Conversation
We already practically don't recommend implementing it right now due to issues being solved in 3.3.
11 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We already practically don't recommend implementing it right now due to issues being solved in 3.3 (see various issues/PRs on this repo for more context here).
The IRCv3 version of metadata can include the basic metadata stuff and whatever new notify spec we have, so that we have one document we can point people towards to implement it. Right now, having this displayed as a regular, recommended spec on our site does more harm than good I feel.