From d5906545f897c8d5006af06402b3500359fefd29 Mon Sep 17 00:00:00 2001 From: Leo Wandersleb Date: Sat, 6 May 2023 12:34:30 -0400 Subject: [PATCH] some clarification --- 45.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/45.md b/45.md index f0267f6b..21dc123e 100644 --- a/45.md +++ b/45.md @@ -6,15 +6,15 @@ Event Counts `draft` `optional` `author:staab` -Relays may support the `COUNT` verb, which provides a mechanism for obtaining event counts. +Relays may support the verb `COUNT`, which provides a mechanism for obtaining event counts. ## Motivation -Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey and count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr. +Some queries a client may want to execute against connected relays are prohibitively expensive, for example, in order to retrieve follower counts for a given pubkey, a client must query all kind-3 events referring to a given pubkey only to count them. The result may be cached, either by a client or by a separate indexing server as an alternative, but both options erode the decentralization of the network by creating a second-layer protocol on top of Nostr. ## Filters and return values -This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md). +This NIP defines the verb `COUNT`, which accepts a subscription id and filters as specified in [NIP 01](01.md) for the verb `REQ`. ``` ["COUNT", , ...]