Mirror/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-12 18:36:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge 38c983dc42 into a1ca7a194b

Browse Source
This commit is contained in:
Tomas Bezouska 2024-12-11 08:50:08 +01:00 committed by GitHub
commit 31fe6d926c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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>,
"pubkey": <administrative contact pubkey>,
"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>,
"version": <string version identifier>
}
@ -64,7 +64,7 @@ An alternative contact may be listed under the `contact` field as well, with the
### 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