nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-13 23:39:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 26.md

Browse Source
This commit is contained in:
sistemd 2023-04-17 18:35:03 +02:00 committed by ennmichael
parent a8e083d6d8
commit f93b55071b
No known key found for this signature in database
GPG Key ID: 6E6E183431A26AF7
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
26.md
View File

@ -44,7 +44,7 @@ The following fields and operators are supported in the above query string:
- `<${TIMESTAMP}` - delegatee may only sign events created ***before*** the specified timestamp
- `>${TIMESTAMP}` - delegatee may only sign events created ***after*** the specified timestamp
In order to create a single condition, you must use a supported field and operator. Multiple conditions can be used in a single query string, including on the same field. Conditions must be combined with `&`.
In order to create a single condition, you must use a supported field and operator. Multiple conditions can be used in a single query string. Conditions can be combined with `&`. Multiple `kind=` conditions mean that the delegation token can be used to sign any of the specified event kinds. Multiple `created_at>` or `created_at<` conditions should not be combined.
For example, the following condition strings are valid:
@ -52,7 +52,7 @@ For example, the following condition strings are valid:
- `kind=0&kind=1&created_at>1675721813`
- `kind=1&created_at>1674777689&created_at<1675721813`
For the vast majority of use-cases, it is advisable that query strings should include a `created_at` ***after*** condition reflecting the current time, to prevent the delegatee from publishing historic notes on the delegator's behalf.
For the vast majority of use-cases, it is advisable that query strings should include a `created_at>` condition reflecting the current time, to prevent the delegatee from publishing historic notes on the delegator's behalf.
#### Example
@ -105,4 +105,4 @@ Clients should display the delegated note as if it was published directly by the
Relays should answer requests such as `["REQ", "", {"authors": ["A"]}]` by querying both the `pubkey` and delegation tags `[1]` value.
Relays SHOULD allow the delegator (8e0d3d3e) to delete the events published by the delegatee (477318cf).
Relays SHOULD allow the delegator (8e0d3d3e) to delete the events published by the delegatee (477318cf).