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

remove reserved range from NIP-28.

Browse Source
This commit is contained in:
fiatjaf 2023-03-07 07:28:53 -03:00
parent b99723efcc
commit 6eb1838921
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1
2 changed files with 30 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
28.md
View File

@ -9,7 +9,7 @@ Public Chat
This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation. This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation.
It reserves five event kinds (40-44) for immediate use and five event kinds (45-49) for future use. It reserves five event kinds (40-44) for immediate use:
- `40 - channel create` - `40 - channel create`
- `41 - channel metadata` - `41 - channel metadata`
@ -138,12 +138,6 @@ For [NIP-10](10.md) relay recommendations, clients generally SHOULD use the rela
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. 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.
Future extensibility
--------------------
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.
Motivation Motivation
---------- ----------
If we're solving censorship-resistant communication for social media, we may as well solve it also for Telegram-style messaging. If we're solving censorship-resistant communication for social media, we may as well solve it also for Telegram-style messaging.

59
README.md
View File

@ -39,36 +39,35 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
- [NIP-78: Application-specific data](78.md) - [NIP-78: Application-specific data](78.md)
## Event Kinds ## Event Kinds
| kind | description | NIP | | kind | description | NIP |
| ------------- | -------------------------------- | ----------------------- | | ------------- | -------------------------------- | ----------- |
| 0 | Metadata | [1](01.md), [5](05.md) | | 0 | Metadata | [1](01.md) |
| 1 | Short Text Note | [1](01.md) | | 1 | Short Text Note | [1](01.md) |
| 2 | Recommend Relay | [1](01.md) | | 2 | Recommend Relay | [1](01.md) |
| 3 | Contacts | [2](02.md) | | 3 | Contacts | [2](02.md) |
| 4 | Encrypted Direct Messages | [4](04.md) | | 4 | Encrypted Direct Messages | [4](04.md) |
| 5 | Event Deletion | [9](09.md) | | 5 | Event Deletion | [9](09.md) |
| 7 | Reaction | [25](25.md) | | 7 | Reaction | [25](25.md) |
| 8 | Badge Award | [58](58.md) | | 8 | Badge Award | [58](58.md) |
| 40 | Channel Creation | [28](28.md) | | 40 | Channel Creation | [28](28.md) |
| 41 | Channel Metadata | [28](28.md) | | 41 | Channel Metadata | [28](28.md) |
| 42 | Channel Message | [28](28.md) | | 42 | Channel Message | [28](28.md) |
| 43 | Channel Hide Message | [28](28.md) | | 43 | Channel Hide Message | [28](28.md) |
| 44 | Channel Mute User | [28](28.md) | | 44 | Channel Mute User | [28](28.md) |
| 45-49 | Public Chat Reserved | [28](28.md) | | 1984 | Reporting | [56](56.md) |
| 1984 | Reporting | [56](56.md) | | 9734 | Zap Request | [57](57.md) |
| 9734 | Zap Request | [57](57.md) | | 9735 | Zap | [57](57.md) |
| 9735 | Zap | [57](57.md) | | 10002 | Relay List Metadata | [65](65.md) |
| 10002 | Relay List Metadata | [65](65.md) | | 22242 | Client Authentication | [42](42.md) |
| 22242 | Client Authentication | [42](42.md) | | 24133 | Nostr Connect | [46](46.md) |
| 24133 | Nostr Connect | [46](46.md) | | 30008 | Profile Badges | [58](58.md) |
| 30008 | Profile Badges | [58](58.md) | | 30009 | Badge Definition | [58](58.md) |
| 30009 | Badge Definition | [58](58.md) | | 30023 | Long-form Content | [23](23.md) |
| 30023 | Long-form Content | [23](23.md) | | 30078 | Application-specific Data | [78](78.md) |
| 30078 | Application-specific Data | [78](78.md) | | 1000-9999 | Regular Events | [16](16.md) |
| 1000-9999 | Regular Events | [16](16.md) | | 10000-19999 | Replaceable Events | [16](16.md) |
| 10000-19999 | Replaceable Events | [16](16.md) | | 20000-29999 | Ephemeral Events | [16](16.md) |
| 20000-29999 | Ephemeral Events | [16](16.md) | | 30000-39999 | Parameterized Replaceable Events | [33](33.md) |
| 30000-39999 | Parameterized Replaceable Events | [33](33.md) |
## Message types ## Message types