diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2022-11-29 11:41:46 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2022-11-29 11:41:46 -0300 |
| commit | bbc931d02d6233a0906b08d4fb1433db2e78ff36 (patch) | |
| tree | 793e4c2e242bccee7f8314fef6d420f5312a6ba3 | |
| parent | 0dcf11df8065be99aed1de2c4aba1c42adf78d74 (diff) | |
refine NIP rules.
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
| @@ -69,9 +69,10 @@ When experimenting with kinds, keep in mind the classification introduced by [NI | |||
| 69 | 69 | ||
| 70 | ## Criteria for acceptance of NIPs | 70 | ## Criteria for acceptance of NIPs |
| 71 | 71 | ||
| 72 | 1. They should be implemented somewhere at least as a prototype somewhere. | 72 | 1. They should be implemented in at least one client and one relay -- when applicable. |
| 73 | 2. They should make sense. | 73 | 2. They should make sense. |
| 74 | 3. Other rules will be made up when necessary. | 74 | 3. They should be optional and backwards-compatible: care must be taken such that clients and relays that choose to not implement them do not stop working when interacting with the ones that choose to. |
| 75 | 4. Other rules will be made up when necessary. | ||
| 75 | 76 | ||
| 76 | ## License | 77 | ## License |
| 77 | 78 | ||