From 3b5d3ca677829333779bb46874bb0dc816283dc9 Mon Sep 17 00:00:00 2001 From: git Date: Fri, 29 Sep 2023 11:46:30 -0700 Subject: [PATCH 1/3] 65: normalize relay uri --- 65.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/65.md b/65.md index 89fc5941..352ee28d 100644 --- a/65.md +++ b/65.md @@ -60,4 +60,4 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f 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. -6. Clients SHOULD trim trailing slashes (`/`) from relay URIs to canonicalize connections. +6. Clients SHOULD deduplicate connections by normalizing relay URIs according to RFC 2616. From 4de43f65a1bc5f312dba039d8b405358ad1f7397 Mon Sep 17 00:00:00 2001 From: git Date: Fri, 29 Sep 2023 12:00:07 -0700 Subject: [PATCH 2/3] Update RFC reference --- 65.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/65.md b/65.md index 352ee28d..49d1d170 100644 --- a/65.md +++ b/65.md @@ -60,4 +60,4 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f 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. -6. Clients SHOULD deduplicate connections by normalizing relay URIs according to RFC 2616. +6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 6455](https://www.rfc-editor.org/rfc/rfc6455.html#section-3). From 0d267aab5a74a7f63275f47ceb3c2773ce437f97 Mon Sep 17 00:00:00 2001 From: git Date: Mon, 2 Oct 2023 15:34:24 -0700 Subject: [PATCH 3/3] Better RFC reference --- 65.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/65.md b/65.md index 49d1d170..b6760290 100644 --- a/65.md +++ b/65.md @@ -60,4 +60,4 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f 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. -6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 6455](https://www.rfc-editor.org/rfc/rfc6455.html#section-3). +6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6).