From 69fd7ca6beece0069a314f0fdc4d9264765e7bc9 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Tue, 16 Jun 2026 18:12:10 +0100 Subject: [PATCH 1/6] Update the specs submodule. --- specs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs b/specs index 42ade61..5eca32c 160000 --- a/specs +++ b/specs @@ -1 +1 @@ -Subproject commit 42ade61d4e49203a1c808203135efe6532845302 +Subproject commit 5eca32ce8cbc0c8f9d123529ef221d8da9516b65 From a1bcf27bd583fb1fb8347b95d6c519383cb993ad Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Tue, 16 Jun 2026 18:12:18 +0100 Subject: [PATCH 2/6] Update the channel-context-client-tag table. --- _data/irc_versions.yml | 18 +++++++++--------- _data/sw_clients.yml | 16 +++++++++++----- 2 files changed, 20 insertions(+), 14 deletions(-) diff --git a/_data/irc_versions.yml b/_data/irc_versions.yml index 392d83f..442f5a5 100644 --- a/_data/irc_versions.yml +++ b/_data/irc_versions.yml @@ -204,7 +204,15 @@ stable: link: /specs/extensions/whox.html isupport: - WHOX - + + channel-context-client-tag: + name: +channel-context + description: Channel context client tag + link: /specs/client-tags/channel-context.html + hide-if-no-support: true + tags: + - +channel-context + reply-client-tag: name: +reply description: Reply client tag @@ -307,14 +315,6 @@ stable: caps: - draft/read-marker - channel-context-client-tag: - name: +draft/channel-context - description: Channel context client tag DRAFT - link: /specs/client-tags/channel-context.html - draft: true - tags: - - +draft/channel-context - react-client-tag: name: +draft/react description: React and unreact client tags DRAFT diff --git a/_data/sw_clients.yml b/_data/sw_clients.yml index 8bac824..e5ed911 100644 --- a/_data/sw_clients.yml +++ b/_data/sw_clients.yml @@ -436,7 +436,6 @@ cap-notify: cap-3.1: cap-3.2: - channel-context-client-tag: chathistory: echo-message: extended-monitor: @@ -452,6 +451,9 @@ standard-replies: typing-client-tag: whox: + partial: + stable: + channel-context-client-tag: "draft cap" SASL: plain: - name: Srain @@ -581,7 +583,6 @@ cap-notify: chghost: account-registration: - channel-context-client-tag: chathistory: echo-message: extended-join: @@ -598,6 +599,9 @@ server-time: setname: whox: + partial: + stable: + channel-context-client-tag: "draft cap" SASL: - plain - oauthbearer @@ -615,7 +619,6 @@ cap-3.1: cap-3.2: channel-rename: - channel-context-client-tag: chghost: echo-message: extended-join: @@ -641,6 +644,9 @@ react-client-tag: reply-client-tag: typing-client-tag: + partial: + stable: + channel-context-client-tag: "draft cap" SASL: - plain - scram-sha-256 @@ -1004,7 +1010,6 @@ server-time: setname: whox: - channel-context-client-tag: react-client-tag: typing-client-tag: reply-client-tag: @@ -1012,6 +1017,7 @@ - plain partial: stable: + channel-context-client-tag: "draft cap" no-implicit-names: "draft cap" - name: Bouncers @@ -1372,7 +1378,6 @@ cap-3.1: cap-3.2: cap-notify: - channel-context-client-tag: chghost: echo-message: extended-join: @@ -1401,6 +1406,7 @@ - scram-sha-256 partial: stable: + channel-context-client-tag: "draft cap" reply-client-tag: "draft cap" - name: Moon Moon # ref: https://github.com/wiseguiz/Moon-Moon/blob/master/irc.moon From 74a4181a21950e0f83414dbb5e35c628fbcea689 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Tue, 16 Jun 2026 19:22:25 +0100 Subject: [PATCH 3/6] Add a link to the OAUTHBEARER spec on the SASL mechs page. --- docs/sasl-mechs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/sasl-mechs.md b/docs/sasl-mechs.md index cfcf2f6..1804ecd 100644 --- a/docs/sasl-mechs.md +++ b/docs/sasl-mechs.md @@ -8,6 +8,7 @@ page-header: > IRC SASL authentication primarily uses the same mechanisms as SASL in other protocols. Most commonly: * [PLAIN](https://tools.ietf.org/html/rfc4616) as defined by RFC 4616 +* [OAUTHBEARER](https://tools.ietf.org/html/rfc7628) as defined by RFC 7628 * [EXTERNAL](https://tools.ietf.org/html/rfc4422#appendix-A) as defined by RFC 4422 * [SCRAM-SHA-256](https://tools.ietf.org/html/rfc7677) as defined by RFC 7677 From 7782340d7f0c499184dcde6d48f82d0e9b2a8752 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Thu, 25 Jun 2026 09:49:57 +0100 Subject: [PATCH 4/6] Fix channel-context being listed as draft on /irc. --- _irc/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_irc/index.md b/_irc/index.md index 49ab629..6e9e3eb 100644 --- a/_irc/index.md +++ b/_irc/index.md @@ -222,7 +222,7 @@ and as such we detail them in their own section here. Here are the client-only tags the IRCv3 WG defines: -* [The `channel-context` client-only tag]({{site.baseurl}}/specs/client-tags/channel-context.html) **[draft]** indicates the channel a private message should be displayed in. +* [The `channel-context` client-only tag]({{site.baseurl}}/specs/client-tags/channel-context.html) indicates the channel a private message should be displayed in. * [The `reply` client-only tag]({{site.baseurl}}/specs/client-tags/reply.html) marks that a given message is intended as a reply to a specific sent message. * [The `react` client-only tag]({{site.baseurl}}/specs/client-tags/react.html) **[draft]** sends a reaction to a specific sent message, allowing such functionality from other chat systems. * [The `typing` client-only tag]({{site.baseurl}}/specs/client-tags/typing.html) lets users know when another user is typing a message in their channel or private message. From 229119cdba4f554f7eed6353cbd1dc9eb989dc25 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Thu, 25 Jun 2026 10:00:11 +0100 Subject: [PATCH 5/6] Update the site metadata files for oper-tag. --- _data/irc_versions.yml | 10 ++++++++++ _data/registry.yml | 4 ++++ 2 files changed, 14 insertions(+) diff --git a/_data/irc_versions.yml b/_data/irc_versions.yml index 442f5a5..24ae941 100644 --- a/_data/irc_versions.yml +++ b/_data/irc_versions.yml @@ -324,6 +324,16 @@ stable: - +draft/react - +draft/unreact + oper-tag: + name: draft/oper-tag + description: oper-tag Extension DRAFT + link: /specs/extensions/oper-tag.html + draft: true + caps: + - draft/oper-tag + tags: + - draft/oper + proposed: name: Proposed Pull Requests specs: {} diff --git a/_data/registry.yml b/_data/registry.yml index c79ec41..e13eb04 100644 --- a/_data/registry.yml +++ b/_data/registry.yml @@ -327,6 +327,10 @@ specs: - channel-context-client-tag description: Indicates the channel a private message should be displayed in. + - name: draft/oper + specs: + - oper-tag + description: Indicates that the source of the message is an IRC operator. - name: Batches include_numeric: false From 4bb789a4cab351a69fab0a3edc17c580b2b98775 Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Thu, 25 Jun 2026 10:05:24 +0100 Subject: [PATCH 6/6] Add oper-tag to /irc. --- _irc/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_irc/index.md b/_irc/index.md index 6e9e3eb..e03b741 100644 --- a/_irc/index.md +++ b/_irc/index.md @@ -302,6 +302,10 @@ allows clients to disable the implicit `NAMES` responses sent after `JOIN` in case they don't always need that information for all channels. Clients can still query that information as needed via the `NAMES` or `WHO` command. +The **work-in-progress** [`oper-tag` spec]({{site.baseurl}}/specs/extensions/oper-tag.html) +defines a way for clients to receive a message tag on messages specifying that +the source of the message is from an IRC operator. This is useful for letting +users know that a message is from a trusted source. ## [Message IDs]({{site.baseurl}}/specs/extensions/message-ids.html)