Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ratify the reply client tag specification. #535

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Ratify the reply client tag specification. #535

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions client-tags/react.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
17 changes: 3 additions & 14 deletions client-tags/reply.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,17 +9,6 @@ copyrights:
email: "[email protected]"
---

## 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
Expand All @@ -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=<msgid>
+reply=<msgid>

## Client implementation considerations

Expand All @@ -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!