From e94cd0bb4cf87b3906fad5b2003102c055829e5f Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Thu, 22 Feb 2024 18:19:38 +0000 Subject: [PATCH] Ratify the reply client tag specification. --- client-tags/react.md | 12 ++++++------ client-tags/reply.md | 17 +++-------------- 2 files changed, 9 insertions(+), 20 deletions(-) diff --git a/client-tags/react.md b/client-tags/react.md index 1fb538460..de463a3f7 100644 --- a/client-tags/react.md +++ b/client-tags/react.md @@ -32,7 +32,7 @@ This tag provides a means of communicating with context-sensitive, potentially n ### Dependencies -Clients wishing to use this tag MUST negotiate the [`message-tags`](../extensions/message-tags.html) capability with the server. Additionally, this tag MUST be used in conjunction with the [`+draft/reply`](./reply.html) client tag. +Clients wishing to use this tag MUST negotiate the [`message-tags`](../extensions/message-tags.html) capability with the server. Additionally, this tag MUST be used in conjunction with the [`+reply`](./reply.html) client tag. ### Format @@ -66,17 +66,17 @@ This specification doesn't define any restrictions on what can be sent as the re In this example, a `TAGMSG` is sent to a channel with an ID provided by the server. A client sends a reaction reply to this message and the server sends an echo-message back to the client. S: @msgid=123 :nick!user@host PRIVMSG #channel :Hello! - C: @+draft/reply=123;+draft/react=lol TAGMSG #channel - S: @msgid=456;+draft/reply=123;+draft/react=lol :nick2!user2@host2 TAGMSG #channel + C: @+reply=123;+draft/react=lol TAGMSG #channel + S: @msgid=456;+reply=123;+draft/react=lol :nick2!user2@host2 TAGMSG #channel An example of an emoticon reaction - C: @+draft/reply=123;+draft/react=:) TAGMSG #channel + C: @+reply=123;+draft/react=:) TAGMSG #channel An example of an emoji reaction - C: @+draft/reply=123;+draft/react=👋 TAGMSG #channel + C: @+reply=123;+draft/react=👋 TAGMSG #channel An example of a reaction sent as a `PRIVMSG` with an additional message body - C: @+draft/reply=123;+draft/react=lol PRIVMSG #channel :lol + C: @+reply=123;+draft/react=lol PRIVMSG #channel :lol diff --git a/client-tags/reply.md b/client-tags/reply.md index 015e28c90..522e7a101 100644 --- a/client-tags/reply.md +++ b/client-tags/reply.md @@ -9,17 +9,6 @@ copyrights: email: "james@irccloud.com" --- -## Notes for implementing work-in-progress version - -This is a work-in-progress specification. - -Software implementing this work-in-progress specification MUST NOT use the -unprefixed `+reply` tag name. Instead, implementations SHOULD use the -`+draft/reply` tag name to be interoperable with other software -implementing a compatible work-in-progress version. - -The final version of the specification will use an unprefixed tag name. - ## Introduction This specification defines a client-only message tag to indicate replies to other messages @@ -34,7 +23,7 @@ Clients wishing to use this tag MUST negotiate the [`message-tags`](../extension The reply tag is sent by a client with the client-only prefix `+` and its value references the server provided ID of another message: - +draft/reply= + +reply= ## Client implementation considerations @@ -49,5 +38,5 @@ In this situation, it might make more sense to leave the reply in place chronolo In this example, a `PRIVMSG` is sent to a channel with an ID provided by the server. A client sends a reply to this message and the server sends an echo-message back to the client. S: @msgid=123 :nick!user@host PRIVMSG #channel :Hello! - C: @+draft/reply=123 PRIVMSG #channel :Hello to you! - S: @msgid=456;+draft/reply=123 :nick2!user2@host2 PRIVMSG #channel :Hello to you! + C: @+reply=123 PRIVMSG #channel :Hello to you! + S: @msgid=456;+reply=123 :nick2!user2@host2 PRIVMSG #channel :Hello to you!