Compare commits

...

2 Commits

Author SHA1 Message Date
Tomas Bezouska
bcbb5267d5
Merge 38c983dc42 into e942427f8f 2024-12-09 21:20:33 -06:00
Tomas Bezouska
38c983dc42
NIPs are no longer numbers 2024-11-30 09:21:18 +01:00

4
11.md
View File

@ -18,7 +18,7 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
"icon": <a link to an icon (e.g. in .jpg, or .png format>, "icon": <a link to an icon (e.g. in .jpg, or .png format>,
"pubkey": <administrative contact pubkey>, "pubkey": <administrative contact pubkey>,
"contact": <administrative alternate contact>, "contact": <administrative alternate contact>,
"supported_nips": <a list of NIP numbers supported by the relay>, "supported_nips": <a list of NIPs supported by the relay>,
"software": <string identifying relay software URL>, "software": <string identifying relay software URL>,
"version": <string version identifier> "version": <string version identifier>
} }
@ -64,7 +64,7 @@ An alternative contact may be listed under the `contact` field as well, with the
### Supported NIPs ### Supported NIPs
As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`. This field is an array of the integer identifiers of `NIP`s that are implemented in the relay. Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`. Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients. As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`. This field is an array of the string identifiers of `NIP`s that are implemented in the relay. Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`. Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients.
### Software ### Software