mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-12-15 03:18:51 +00:00
rename "parameterized replaceable event" to "tagged-replaceable event".
This commit is contained in:
4
23.md
4
23.md
@@ -6,7 +6,7 @@ Long-form Content
|
||||
|
||||
`draft` `optional`
|
||||
|
||||
This NIP defines `kind:30023` (a _parameterized replaceable event_) for long-form text content, generally referred to as "articles" or "blog posts". `kind:30024` has the same structure as `kind:30023` and is used to save long form drafts.
|
||||
This NIP defines `kind:30023` (a _tagged-replaceable event_) for long-form text content, generally referred to as "articles" or "blog posts". `kind:30024` has the same structure as `kind:30023` and is used to save long form drafts.
|
||||
|
||||
"Social" clients that deal primarily with `kind:1` notes should not be expected to implement this NIP.
|
||||
|
||||
@@ -31,7 +31,7 @@ Other metadata fields can be added as tags to the event as necessary. Here we st
|
||||
|
||||
### Editability
|
||||
|
||||
These articles are meant to be editable, so they should make use of the parameterized replaceability feature and include a `d` tag with an identifier for the article. Clients should take care to only publish and read these events from relays that implement that. If they don't do that they should also take care to hide old versions of the same article they may receive.
|
||||
These articles are meant to be editable, so they should make use of the tagged replaceability feature and include a `d` tag with an identifier for the article. Clients should take care to only publish and read these events from relays that implement that. If they don't do that they should also take care to hide old versions of the same article they may receive.
|
||||
|
||||
### Linking
|
||||
|
||||
|
||||
Reference in New Issue
Block a user