laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2026-07-22 07:48:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

One sentence in NIP-01 that helps resolves a huge issue with relay connection management. (#2307)

Browse Source 
Co-authored-by: sandwich <dskvr@users.noreply.github.com>
This commit is contained in:
sandwich
2026-05-28 23:19:10 +02:00
committed by GitHub
parent 9c9846e11d
commit 8495b325d4
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
01.md
View File

@@ -108,6 +108,8 @@ These are just conventions and relay implementations may differ.
Relays expose a websocket endpoint to which clients can connect. Clients SHOULD open a single websocket connection to each relay and use it for all their subscriptions. Relays MAY limit number of connections from specific IP/client/etc.
Relays MUST only accept connections to a single endpoint when additional path segments do not influence its behavior.
### From client to relay: sending events and creating subscriptions
Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns: