nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

typos.

Browse Source
This commit is contained in:
k 2024-09-23 19:36:15 +03:30 committed by GitHub
parent 6f36e86b0e
commit 1a8d8c4496
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
09.md
View File

@ -6,7 +6,7 @@ Event Deletion Request
`draft` `optional`
A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author is requesting to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion.
A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author requests to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion.
The event's `content` field MAY contain a text note describing the reason for the deletion request.
@ -53,11 +53,11 @@ For example:
The above event requests the deletation of all text notes and reactions from a user.
A kind 5 MUST NOT contain a `f` tag beside other tags, or multiple `f` tags in one event. The `"authors"` field of filter should be implicit.
A kind 5 MUST NOT contain a `f` tag beside other tags, or multiple `f` tags in one event. The `"authors"` field of the filter should be implicit.
### 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 deletation requests with consuming small space and this bring possiblited to remove ***all posts***, ***direct messages***, or ***delete account***.
## Client Usage
@ -79,4 +79,4 @@ Publishing a deletion request event against a deletion request has no effect. C
## 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 don't 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.