Add +draft/channel-context client tag draft/read-marker extension (#459)

Author: emersion

_data/irc_versions.yml

@@ -254,6 +254,22 @@ stable:
       tags:
         - +draft/reply
 
+    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
+
+    read-marker:
+      name: draft/read-marker
+      description: Read marker DRAFT
+      link: /specs/extensions/read-marker.html
+      draft: true
+      caps:
+        - draft/read-marker
+
 proposed:
   name: Proposed Pull Requests
   specs:

_data/registry.yml

@@ -194,6 +194,10 @@
       specs:
         - multiline
       description: Allows clients and servers to use send messages that can exceed the usual byte length limit and that can contain line breaks.
+    - name: read-marker
+      specs:
+        - read-marker
+      description: Allows clients of the same user to synchronize read markers.
     - name: sasl
       specs:
         - sasl-3.1
@@ -260,6 +264,10 @@
       specs:
         - typing-client-tag
       description: Allows users to see when other users are typing.
+    - name: +channel-context
+      specs:
+        - channel-context-client-tag
+      description: Indicates the channel a private message should be displayed in.
 
 - name: Batches
   include_numeric: false
@@ -331,6 +339,10 @@
       specs: 
         - userhost-in-names
       description: Not defined by IRCv3 but extended to include account names.
+    - name: MARKREAD
+      specs:
+        - read-marker
+      description: Fetches or stores a read marker.
     - name: REGISTER
       specs:
         - account-registration

_data/sw_clients.yml

@@ -349,6 +349,7 @@
           cap-notify:
           cap-3.1:
           cap-3.2:
+          channel-context-client-tag:
           chathistory:
           echo-message:
           invite-notify:
@@ -459,6 +460,7 @@
           cap-notify:
           chghost:
           account-registration:
+          channel-context-client-tag:
           chathistory:
           extended-monitor:
           echo-message:
@@ -469,6 +471,7 @@
           monitor:
           msgid:
           multi-prefix:
+          read-marker:
           sasl-3.1:
           sasl-3.2:
           server-time:
@@ -489,6 +492,7 @@
           cap-notify:
           cap-3.1:
           cap-3.2:
+          channel-context-client-tag:
           chghost:
           echo-message:
           extended-join:
@@ -813,6 +817,7 @@
           message-tags:
           monitor:
           multi-prefix:
+          read-marker:
           sasl-3.1:
           sasl-3.2:
           server-time:
@@ -978,6 +983,7 @@
           monitor:
           msgid:
           multi-prefix:
+          read-marker:
           sasl-3.1:
           sasl-3.2:
           server-time:
@@ -1140,6 +1146,7 @@
           cap-3.1:
           cap-3.2:
           cap-notify:
+          channel-context-client-tag:
           chghost:
           echo-message:
           extended-join:

_data/sw_servers.yml

@@ -43,6 +43,7 @@
           msgid:
           multi-prefix:
           multiline:
+          read-marker:
           sasl-3.1:
           sasl-3.2:
           server-time:

_irc/index.md

@@ -199,6 +199,8 @@ The `chathistory` extension standardizes a mechanism for clients to request mess
 
 The **work-in-progress** [`chathistory` spec]({{site.baseurl}}/specs/extensions/chathistory.html) describes the syntax and semantics of the new `CHATHISTORY` command.
 
+The **work-in-progress** [`read-marker` spec]({{site.baseurl}}/specs/extensions/read-marker.html) adds a new command to synchronize read markers between several clients of the same user.
+
 
 ## Changing User Properties
 
@@ -225,6 +227,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 `reply` client-only tag]({{site.baseurl}}/specs/client-tags/reply.html) **[draft]** 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.