NIP-91: remove `has_more`, add `auth_recommended`

1 files changed, 6 insertions, 5 deletions

diff --git a/91.md b/91.md
index 76e8123..582a1d2 100644
--- a/91.md
+++ b/91.md
@@ -30,7 +30,8 @@ This MAY be higher or lower than the lowest `created_at`, and the clients SHOULD
 
 ### `cursor`
 
-The value of this extension MUST be a string if present, and represents a cursor the client can use to paginate this query.
+The value of this extension MUST be a string or `null` if present, and represents a cursor the client can use to paginate this query.
+If the value is `null`, then it indicates that no more events are available for the given set of filters.
 To get more events, the client MUST send a `REQ` with the same filters (except limit, which can be changed), and the `cursor` string
 in the 1st filter with the key `cursor`. Example:
 ```jsonc
@@ -46,8 +47,8 @@ in the 1st filter with the key `cursor`. Example:
 This cursor MUST be valid for the duration of the connection, and MAY be valid in a new connection. A relay may indicate a cursor is no longer valid
 by sending a CLOSED with the prefix `bad-cursor: `.
 
-### `has_more`
-`recommended`
+### `auth_recommended`
 
-The value of this extension MUST be a boolean if present, and should represent if the client should continue trying to get events.
-This MAY be false if the relay has completed the query due to not having more events available, or may not be able to complete this query due to a permanent failure (scan limit exceeded is one).
+The value of this extension MUST be a boolean if present, and indicates if the client should `AUTH` to get more events that match this query.
+This is a less disruptive alternative to `CLOSED` with `auth-required:` for filters that don't explicitly ask for access controlled events,
+but may match them.