From 0b08cf545b50b4799000e90aa4c5ada2cb73ca62 Mon Sep 17 00:00:00 2001
From: Yoji Shidara <dara@shidara.net>
Date: Thu, 13 Jul 2023 14:14:36 +0900
Subject: [PATCH] Explicitly state that the `subscription_id` is treated per
 connection

---
 01.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/01.md b/01.md
index 4c2ccd9d..8b1471d8 100644
--- a/01.md
+++ b/01.md
@@ -55,7 +55,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th
   * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates.
   * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.
 
-`<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription.
+`<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. Relays should manage `<subscription_id>`s independently for each WebSocket connection; even if `<subscrption_id>`s are the same string, they should be treated as different subscriptions for different connections.
 
 `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: