diff options
| author | git <badonyx@proton.me> | 2023-10-02 15:34:24 -0700 |
|---|---|---|
| committer | git <badonyx@proton.me> | 2023-10-02 15:34:24 -0700 |
| commit | 0d267aab5a74a7f63275f47ceb3c2773ce437f97 (patch) | |
| tree | 240830c5c644129ed1f582a117e164006d7fb4ba | |
| parent | 4de43f65a1bc5f312dba039d8b405358ad1f7397 (diff) | |
Better RFC reference
| -rw-r--r-- | 65.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -60,4 +60,4 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f | |||
| 60 | 60 | ||
| 61 | 5. If a relay signals support for this NIP in their [NIP-11](11.md) document that means they're willing to accept kind 10002 events from a broad range of users, not only their paying customers or whitelisted group. | 61 | 5. If a relay signals support for this NIP in their [NIP-11](11.md) document that means they're willing to accept kind 10002 events from a broad range of users, not only their paying customers or whitelisted group. |
| 62 | 62 | ||
| 63 | 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 6455](https://www.rfc-editor.org/rfc/rfc6455.html#section-3). | 63 | 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6). |