mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-02-21 12:49:00 +00:00
Add self to NIP 11
This commit is contained in:
parent
63d1e89f53
commit
10dc301eb8
5
11.md
5
11.md
@ -17,6 +17,7 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
|
||||
"banner": <a link to an image (e.g. in .jpg, or .png format)>,
|
||||
"icon": <a link to an icon (e.g. in .jpg, or .png format>,
|
||||
"pubkey": <administrative contact pubkey>,
|
||||
"self": <relay's own pubkey>,
|
||||
"contact": <administrative alternate contact>,
|
||||
"supported_nips": <a list of NIP numbers supported by the relay>,
|
||||
"software": <string identifying relay software URL>,
|
||||
@ -58,6 +59,10 @@ An administrative contact may be listed with a `pubkey`, in the same format as N
|
||||
|
||||
Relay operators have no obligation to respond to direct messages.
|
||||
|
||||
### Self
|
||||
|
||||
A relay MAY maintain an identity independent from its administrator using the `self` field, which MUST be a 32-byte hex public key. This allows relays to respond to requests with events published either in advance or on demand by their own key.
|
||||
|
||||
### Contact
|
||||
|
||||
An alternative contact may be listed under the `contact` field as well, with the same purpose as `pubkey`. Use of a Nostr public key and direct message SHOULD be preferred over this. Contents of this field SHOULD be a URI, using schemes such as `mailto` or `https` to provide users with a means of contact.
|
||||
|
Loading…
Reference in New Issue
Block a user