mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-01-18 20:21:35 +00:00
typos.
This commit is contained in:
parent
7d5cee8752
commit
d0b3108e8e
13
09.md
13
09.md
@ -15,7 +15,7 @@ For example:
|
|||||||
```jsonc
|
```jsonc
|
||||||
{
|
{
|
||||||
"kind": 5,
|
"kind": 5,
|
||||||
"pubkey": <32-bytes hex-encoded public key of the event creator>,
|
"pubkey": "<32-bytes hex-encoded public key of the event creator>",
|
||||||
"tags": [
|
"tags": [
|
||||||
["e", "dcd59..464a2"],
|
["e", "dcd59..464a2"],
|
||||||
["e", "968c5..ad7a4"],
|
["e", "968c5..ad7a4"],
|
||||||
@ -36,13 +36,14 @@ When an `a` tag is used, relays SHOULD delete all versions of the replaceable ev
|
|||||||
|
|
||||||
## Filter Deletion
|
## Filter Deletion
|
||||||
|
|
||||||
A client MAY use a `filter` tag to provide a filter, relays and clients SHOULD consider deletation of all events matching to this specific filter from this client up to `kind 5` created at.
|
A client MAY use a `filter` tag to provide a filter, relays and clients SHOULD consider deletion of all events matching to this specific filter from this `pubkey`.
|
||||||
|
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
```jsonc
|
```jsonc
|
||||||
{
|
{
|
||||||
"kind": 5,
|
"kind": 5,
|
||||||
"pubkey": <32-bytes hex-encoded public key of the event creator>,
|
"pubkey": "<32-bytes hex-encoded public key of the event creator>",
|
||||||
"tags": [
|
"tags": [
|
||||||
["filter", "{\"kinds\":[1,7]}"]
|
["filter", "{\"kinds\":[1,7]}"]
|
||||||
],
|
],
|
||||||
@ -53,11 +54,11 @@ For example:
|
|||||||
|
|
||||||
The above event requests the deletion of all text notes and reactions from a user.
|
The above event requests the deletion of all text notes and reactions from a user.
|
||||||
|
|
||||||
A kind 5 MUST NOT contain a `filter` tag beside other tags, or multiple `filter` tags in one event. The `"authors"` field of the filter should be implicit. relays and clients must consider filter `since` and `until` fields to find events to be deleted in case of the time range, not the deletion event `created_at`.
|
The Relays MUST only consider the first `filter` tag. The `"authors"` field of the filter should be implicit. relays and clients MUST consider filter `since` and `until` fields to find events to be deleted in case of the time range, not the deletion event `created_at`.
|
||||||
|
|
||||||
### Usages
|
### Usages
|
||||||
|
|
||||||
User can make complex bulk deletation requests with consuming small space and this bring possiblited to remove ***all posts***, ***direct messages***, or ***delete account***.
|
User can make complex bulk deletion requests with consuming small space and this bring possibility to remove ***all posts***, ***direct messages***, or ***delete account***.
|
||||||
|
|
||||||
## Client Usage
|
## Client Usage
|
||||||
|
|
||||||
@ -79,4 +80,4 @@ Publishing a deletion request event against a deletion request has no effect. C
|
|||||||
|
|
||||||
## Protection for a Deletion Request
|
## Protection for a Deletion Request
|
||||||
|
|
||||||
if the deletion request is intended to be applied in a set of limited relays, clients can send them as protected events and expect other relays to not execute them in sync or broadcasting.
|
If the deletion request is intended to be applied in a set of limited relays, clients can send them as protected events and expect other relays to not execute them in sync or broadcasting.
|
||||||
|
Loading…
Reference in New Issue
Block a user