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

add update-pin-list to nip29

Browse Source
This commit is contained in:
Sepehr Safari 2024-08-11 15:03:26 +03:30 committed by GitHub
parent 010fc579a9
commit 962752cb29
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
29.md
View File

@ -120,8 +120,7 @@ Each moderation action uses a different kind and requires different arguments, w
| 9005 | `delete-event` | `e` (id hex) |
| 9006 | `edit-group-status` | `public` or `private`, `open` or `closed` |
| 9007 | `create-group` | |
| 9008 | `add-pin` | `e` (id hex) |
| 9009 | `remove-pin` | `e` (id hex) |
| 9008 | `update-pin-list` | `e` (id hex) |
- *group metadata* (`kind:39000`) (optional)
@ -204,7 +203,7 @@ Admins may decide to pin one or more messages on top of the group.
Similar to *group members*, this event is supposed to be generated by relays that host the group.
It's a NIP-51-like list of events (e.g. kind 9, 10, 11, 12) that are pins of the group. Relays might choose to not to publish this information or to restrict what pubkeys can fetch it.
It's a NIP-51-like list of events (e.g. kind 9, 10, 11, 12) that are pins of the group. Relays might choose to not to publish this information or to restrict what pubkeys can fetch it. The order of the pins is the order they should be displayed. The relay may choose to limit the number of pins to a fixed number.
```json
{