diff options
| author | hodlbod <jstaab@protonmail.com> | 2024-05-28 11:38:17 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-28 11:38:17 -0700 |
| commit | 57fcad3e13a1ae82018b7948034a758a03bc659e (patch) | |
| tree | 578e572204a47d493fbcaf21ae7c404a7c52687a | |
| parent | 244666ed0d6cb13b7459e9710ad3ab67bec61b4c (diff) | |
| parent | 8199b795716a253655db5f7cce7463202e0d47d0 (diff) | |
Merge pull request #1264 from coracle-social/client-implementation-requirements
Raise bar for NIP implementation
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -278,7 +278,7 @@ Please update these lists when proposing NIPs introducing new event kinds. | |||
| 278 | 278 | ||
| 279 | ## Criteria for acceptance of NIPs | 279 | ## Criteria for acceptance of NIPs |
| 280 | 280 | ||
| 281 | 1. They should be implemented in at least two clients and one relay -- when applicable. | 281 | 1. They should be fully implemented in at least two clients and one relay -- when applicable. |
| 282 | 2. They should make sense. | 282 | 2. They should make sense. |
| 283 | 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. | 283 | 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. |
| 284 | 4. There should be no more than one way of doing the same thing. | 284 | 4. There should be no more than one way of doing the same thing. |