diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2024-09-28 12:26:48 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2024-09-28 12:29:03 -0300 |
| commit | a736e629be5c4c9125d98bdb4965851d8110c483 (patch) | |
| tree | 3674e4f23c873dca200904e2893fc842e74ea342 /32.md | |
| parent | 4438b892d8abd189afc75f9f54532ec95f108d9f (diff) | |
complete renaming to "addressable" events.
as noticed by @bezysoftware at https://github.com/nostr-protocol/nips/pull/1437#issuecomment-2380626514.
I don't know how so many of these instances were left from the original PR at following ca3c52e3e74f0a4679f1c6c0d9ac6461ea748d2d.
Diffstat (limited to '32.md')
| -rw-r--r-- | 32.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -8,7 +8,7 @@ Labeling | |||
| 8 | 8 | ||
| 9 | This NIP defines two new indexable tags to label events and a new event kind (`kind:1985`) to attach those labels to existing events. This supports several use cases, including distributed moderation, collection management, license assignment, and content classification. | 9 | This NIP defines two new indexable tags to label events and a new event kind (`kind:1985`) to attach those labels to existing events. This supports several use cases, including distributed moderation, collection management, license assignment, and content classification. |
| 10 | 10 | ||
| 11 | New Tags: | 11 | New Tags: |
| 12 | 12 | ||
| 13 | - `L` denotes a label namespace | 13 | - `L` denotes a label namespace |
| 14 | - `l` denotes a label | 14 | - `l` denotes a label |
| @@ -146,7 +146,7 @@ Other Notes | |||
| 146 | ----------- | 146 | ----------- |
| 147 | 147 | ||
| 148 | When using this NIP to bulk-label many targets at once, events may be requested for deletion using [NIP-09](09.md) and a replacement | 148 | When using this NIP to bulk-label many targets at once, events may be requested for deletion using [NIP-09](09.md) and a replacement |
| 149 | may be published. We have opted not to use parameterizable/replaceable events for this due to the | 149 | may be published. We have opted not to use addressable/replaceable events for this due to the |
| 150 | complexity in coming up with a standard `d` tag. In order to avoid ambiguity when querying, | 150 | complexity in coming up with a standard `d` tag. In order to avoid ambiguity when querying, |
| 151 | publishers SHOULD limit labeling events to a single namespace. | 151 | publishers SHOULD limit labeling events to a single namespace. |
| 152 | 152 | ||