James Wheare

What exactly is the difficulty for clients that this solves? They have to handle servers with no labeled-response at all anyway so I'm struggling to understand the problem.

Is this a hypothetical or is there a specific client implementation that is struggling with something concrete? An example involving irc protocol traffic and code/pseudo would be great. I don’t...

It doesn't appear that this issue has much consensus but correct me if I'm wrong. Is anyone interested in implementing this or continuing the discussion?

My opinion is unchanged since https://github.com/ircv3/ircv3-specifications/pull/490#issuecomment-1069381428

While it might not be great to send this to channels, there is a use for this functionality in bouncers/gateways. Perhaps not as a client tag though.

That said, the BOUNCER command is probably better placed for that. https://github.com/ircv3/ircv3-ideas/issues/39 https://gist.github.com/prawnsalad/d864822d9bb8116626a4370bee6e6fc6#changing-a-buffer `[c] BOUNCER changebuffer netid buffername seen=1`

There was strong concensus in the [24 Feb 2021 meeting](https://github.com/ircv3/ircv3.github.io/issues/353) that this should definitely be restricted to PMs only, and removed from the roadmap pending further implementation interest.

I’m basically gonna rewrite everything so maybe hold off on wording reviews for a bit (already changed most of these)

OK, reviews welcome on the Mechanisms section. Still need to rewrite the opening preamble, the subcommand headings and revisit examples.

The notification isn’t new. It used to be enabled by the optional metadata-notify cap. Same as away/account notify. Keyvalue is the still the reply for queries.