diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-01-02 07:16:59 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-01-02 07:17:13 -0300 |
| commit | 3dd52e5cb4ec3a16011afed1ecef6cd07026ddcd (patch) | |
| tree | 921691e37d7017d372ec2a2d1af06f01300c0c1b | |
| parent | da7899cebefef4b652fcb10cab26adca239d4c54 (diff) | |
increase requirements for nips.
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
| @@ -72,10 +72,11 @@ When experimenting with kinds, keep in mind the classification introduced by [NI | |||
| 72 | 72 | ||
| 73 | ## Criteria for acceptance of NIPs | 73 | ## Criteria for acceptance of NIPs |
| 74 | 74 | ||
| 75 | 1. They should be implemented in at least one client and one relay -- when applicable. | 75 | 1. They should be implemented in at least two clients and one relay -- when applicable. |
| 76 | 2. They should make sense. | 76 | 2. They should make sense. |
| 77 | 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. | 77 | 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. |
| 78 | 4. Other rules will be made up when necessary. | 78 | 4. There should be no more than one way of doing the same thing. |
| 79 | 5. Other rules will be made up when necessary. | ||
| 79 | 80 | ||
| 80 | ## License | 81 | ## License |
| 81 | 82 | ||