Add 62: Curated Publications#1782
Conversation
Fixed wordings from collection to publication Added <E, A> for derivative works nostr-protocol#1600 (comment)
| - Additional event kinds MAY be supported | ||
| - MUST include an `auto-update` tag specifying update behavior: | ||
| - Format: `["auto-update", "<yes|ask|no>"]` | ||
| - Controls whether clients should automatically update to newer versions |
There was a problem hiding this comment.
what does this mean? auto-update what and from where?
There was a problem hiding this comment.
Optional event ID field enables version tracking while maintaining updateable references>
Its for case where a publisher would rather have a stable snapshot of the publication, rather than have it continually update. They'd use the the event id over the coordinate
["a", "<kind:pubkey:dtag>", "<relay hint>", "<event id>"],There was a problem hiding this comment.
if that's what intent, using the e tag instead of the a tag is the right way to go; the "auto-update" tag is not necessary as it's already signaled by the a vs e tag.
This tag looks very implementation-specific, so it should not be in the NIP, specially not with a MUST; if you still want to have behavior of knowing when to ask the user, you could put that in a NIP-78 event.
3 participants
Originally from #1600
Fixed wordings from collection to publication
For derivative works:
ptag requirementNIP-62: Curated Publications #1600 (comment)