Ricardo Arturo Cabral Mejía 147cd0a2ea
Merge pull request from Semisol/patch-1
nip16: small fix
2022-10-17 14:24:06 -04:00
2022-10-07 17:17:34 -03:00
2022-05-01 07:48:57 -03:00
2022-05-01 07:48:57 -03:00
2022-05-08 21:34:27 -03:00
2022-05-01 07:48:57 -03:00
2022-05-06 20:54:45 -03:00
2022-05-01 07:48:57 -03:00
2022-05-01 07:48:57 -03:00
2022-09-02 18:47:42 -03:00
2022-05-01 07:48:57 -03:00
2022-05-06 22:04:57 -03:00
2022-05-24 07:33:11 -05:00
2022-05-27 19:43:15 +03:00
2022-10-16 20:24:21 +03:00
2022-08-14 11:26:39 -04:00
2022-08-24 13:24:50 +01:00
2022-09-10 14:28:08 -03:00
2022-09-11 08:23:02 -03:00

NIPs

NIPs stand for Nostr Implementation Possibilities. They exist to document what MUST, what SHOULD and what MAY be implemented by Nostr-compatible relay and client software.

Event Kinds

kind description NIP
0 Metadata 1, 5
1 Text 1
2 Recommend Relay 1
3 Contacts 2
4 Encrypted Direct Messages 4
5 Event Deletion 9
7 Reaction 25
40 Channel Creation 28
41 Channel Metadata 28
42 Channel Message 28
43 Channel Hide Message 28
44 Channel Mute User 28
45-49 Public Chat Reserved 28

Please update this list when proposing NIPs introducing new event kinds.

When experimenting with kinds, keep in mind the classification introduced by NIP-16.

Criteria for acceptance of NIPs

  1. They should be implemented somewhere at least as a prototype somewhere.
  2. They should make sense.
  3. Other rules will be made up when necessary.

License

All NIPs are public domain.

Description
A mirror for NIPS
Readme 20 MiB
Languages
Markdown 100%