mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-04-04 09:58:05 +02:00
add encoding type and example
This commit is contained in:
parent
b71a190db5
commit
a57c8056c2
3
26.md
3
26.md
@ -45,7 +45,7 @@ The following fields and operators are supported in the above query string:
|
||||
- `>${TIMESTAMP}` - delegatee may only sign events created ***after*** the specified timestamp
|
||||
3. `content`
|
||||
- *Operators*:
|
||||
- `=${CONTENT}` - delegatee may only sign events with this content
|
||||
- `=${CONTENT}` - delegatee may only sign events with this content in RFC 3986 URI encoding
|
||||
|
||||
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 `&`.
|
||||
|
||||
@ -54,6 +54,7 @@ For example, the following condition strings are valid:
|
||||
- `kind=1&created_at<1675721813`
|
||||
- `kind=0&kind=1&created_at>1675721813`
|
||||
- `kind=1&created_at>1674777689&created_at<1675721813`
|
||||
- `kind=1&created_at>1674777689&content=Hello%20world`
|
||||
|
||||
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.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user