diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-03-07 07:28:53 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-03-07 07:28:53 -0300 |
| commit | 6eb18389212430f91f293f7a57895b05b9e37e13 (patch) | |
| tree | c8c5f8d0c83c59662ec38cb58c7e81cc7ad3edbf | |
| parent | b99723efcca383affd43eb2efb5b25c949346588 (diff) | |
remove reserved range from NIP-28.
| -rw-r--r-- | 28.md | 8 | ||||
| -rw-r--r-- | README.md | 59 |
2 files changed, 30 insertions, 37 deletions
| @@ -9,7 +9,7 @@ Public Chat | |||
| 9 | 9 | ||
| 10 | This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation. | 10 | This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation. |
| 11 | 11 | ||
| 12 | It reserves five event kinds (40-44) for immediate use and five event kinds (45-49) for future use. | 12 | It reserves five event kinds (40-44) for immediate use: |
| 13 | 13 | ||
| 14 | - `40 - channel create` | 14 | - `40 - channel create` |
| 15 | - `41 - channel metadata` | 15 | - `41 - channel metadata` |
| @@ -138,12 +138,6 @@ For [NIP-10](10.md) relay recommendations, clients generally SHOULD use the rela | |||
| 138 | Clients MAY recommend any relay URL. For example, if a relay hosting the original kind 40 event for a channel goes offline, clients could instead fetch channel data from a backup relay, or a relay that clients trust more than the original relay. | 138 | Clients MAY recommend any relay URL. For example, if a relay hosting the original kind 40 event for a channel goes offline, clients could instead fetch channel data from a backup relay, or a relay that clients trust more than the original relay. |
| 139 | 139 | ||
| 140 | 140 | ||
| 141 | Future extensibility | ||
| 142 | -------------------- | ||
| 143 | |||
| 144 | We reserve event kinds 45-49 for other events related to chat, to potentially include new types of media (photo/video), moderation, or support of private or group messaging. | ||
| 145 | |||
| 146 | |||
| 147 | Motivation | 141 | Motivation |
| 148 | ---------- | 142 | ---------- |
| 149 | If we're solving censorship-resistant communication for social media, we may as well solve it also for Telegram-style messaging. | 143 | If we're solving censorship-resistant communication for social media, we may as well solve it also for Telegram-style messaging. |
| @@ -39,36 +39,35 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh | |||
| 39 | - [NIP-78: Application-specific data](78.md) | 39 | - [NIP-78: Application-specific data](78.md) |
| 40 | 40 | ||
| 41 | ## Event Kinds | 41 | ## Event Kinds |
| 42 | | kind | description | NIP | | 42 | | kind | description | NIP | |
| 43 | | ------------- | -------------------------------- | ----------------------- | | 43 | | ------------- | -------------------------------- | ----------- | |
| 44 | | 0 | Metadata | [1](01.md), [5](05.md) | | 44 | | 0 | Metadata | [1](01.md) | |
| 45 | | 1 | Short Text Note | [1](01.md) | | 45 | | 1 | Short Text Note | [1](01.md) | |
| 46 | | 2 | Recommend Relay | [1](01.md) | | 46 | | 2 | Recommend Relay | [1](01.md) | |
| 47 | | 3 | Contacts | [2](02.md) | | 47 | | 3 | Contacts | [2](02.md) | |
| 48 | | 4 | Encrypted Direct Messages | [4](04.md) | | 48 | | 4 | Encrypted Direct Messages | [4](04.md) | |
| 49 | | 5 | Event Deletion | [9](09.md) | | 49 | | 5 | Event Deletion | [9](09.md) | |
| 50 | | 7 | Reaction | [25](25.md) | | 50 | | 7 | Reaction | [25](25.md) | |
| 51 | | 8 | Badge Award | [58](58.md) | | 51 | | 8 | Badge Award | [58](58.md) | |
| 52 | | 40 | Channel Creation | [28](28.md) | | 52 | | 40 | Channel Creation | [28](28.md) | |
| 53 | | 41 | Channel Metadata | [28](28.md) | | 53 | | 41 | Channel Metadata | [28](28.md) | |
| 54 | | 42 | Channel Message | [28](28.md) | | 54 | | 42 | Channel Message | [28](28.md) | |
| 55 | | 43 | Channel Hide Message | [28](28.md) | | 55 | | 43 | Channel Hide Message | [28](28.md) | |
| 56 | | 44 | Channel Mute User | [28](28.md) | | 56 | | 44 | Channel Mute User | [28](28.md) | |
| 57 | | 45-49 | Public Chat Reserved | [28](28.md) | | 57 | | 1984 | Reporting | [56](56.md) | |
| 58 | | 1984 | Reporting | [56](56.md) | | 58 | | 9734 | Zap Request | [57](57.md) | |
| 59 | | 9734 | Zap Request | [57](57.md) | | 59 | | 9735 | Zap | [57](57.md) | |
| 60 | | 9735 | Zap | [57](57.md) | | 60 | | 10002 | Relay List Metadata | [65](65.md) | |
| 61 | | 10002 | Relay List Metadata | [65](65.md) | | 61 | | 22242 | Client Authentication | [42](42.md) | |
| 62 | | 22242 | Client Authentication | [42](42.md) | | 62 | | 24133 | Nostr Connect | [46](46.md) | |
| 63 | | 24133 | Nostr Connect | [46](46.md) | | 63 | | 30008 | Profile Badges | [58](58.md) | |
| 64 | | 30008 | Profile Badges | [58](58.md) | | 64 | | 30009 | Badge Definition | [58](58.md) | |
| 65 | | 30009 | Badge Definition | [58](58.md) | | 65 | | 30023 | Long-form Content | [23](23.md) | |
| 66 | | 30023 | Long-form Content | [23](23.md) | | 66 | | 30078 | Application-specific Data | [78](78.md) | |
| 67 | | 30078 | Application-specific Data | [78](78.md) | | 67 | | 1000-9999 | Regular Events | [16](16.md) | |
| 68 | | 1000-9999 | Regular Events | [16](16.md) | | 68 | | 10000-19999 | Replaceable Events | [16](16.md) | |
| 69 | | 10000-19999 | Replaceable Events | [16](16.md) | | 69 | | 20000-29999 | Ephemeral Events | [16](16.md) | |
| 70 | | 20000-29999 | Ephemeral Events | [16](16.md) | | 70 | | 30000-39999 | Parameterized Replaceable Events | [33](33.md) | |
| 71 | | 30000-39999 | Parameterized Replaceable Events | [33](33.md) | | ||
| 72 | 71 | ||
| 73 | ## Message types | 72 | ## Message types |
| 74 | 73 | ||