From 8e5a275f991c8fe31aba9db0ea0dac2586d50ca3 Mon Sep 17 00:00:00 2001 From: Josua Schmid Date: Tue, 26 Dec 2023 21:57:04 +0100 Subject: [PATCH] NIP-01 Tighten-up subscription_id management rule Rephrase to "MUST" so that one does not assume a connection could `CLOSE` any `subscription_id`, which it must not. --- 01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01.md b/01.md index eed20a5..ec872c3 100644 --- a/01.md +++ b/01.md @@ -104,7 +104,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th * `["REQ", , , , ...]`, used to request events and subscribe to new updates. * `["CLOSE", ]`, used to stop previous subscriptions. -`` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. Relays should manage ``s independently for each WebSocket connection; even if ``s are the same string, they should be treated as different subscriptions for different connections. +`` is an arbitrary, non-empty string of max length 64 chars. It represents a subscription per connection. Relays MUST manage ``s independently for each WebSocket connection. ``s are not guarantueed to be globally unique. `` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: