diff options
| author | git <badonyx@proton.me> | 2023-09-29 12:00:07 -0700 |
|---|---|---|
| committer | git <badonyx@proton.me> | 2023-09-29 12:00:07 -0700 |
| commit | 4de43f65a1bc5f312dba039d8b405358ad1f7397 (patch) | |
| tree | 3266c57cab4c9abb77bfe1c224386843c3abc023 | |
| parent | 3b5d3ca677829333779bb46874bb0dc816283dc9 (diff) | |
Update 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 2616. | 63 | 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 6455](https://www.rfc-editor.org/rfc/rfc6455.html#section-3). |