NIP-11 for publishing server metadata #51
Conversation
nips/11.md
Outdated
| }] | ||
| ``` | ||
|
|
||
| Additional fields may be present, but they MUST be prefixed with `x-` to indicate they are not standard. |
There was a problem hiding this comment.
I'm strongly against the x- stuff. If people want to return extra fields they should be able to. And if others want to rely on these fields then they are a standard -- even if they're not covered on these documents.
Also software implementations must know reasonably well what they're supposed to return and what they must look for.
There was a problem hiding this comment.
No problem, I can remove the x- suggestion.
nips/11.md
Outdated
|
|
||
| ### 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 string identifiers of `NIP`s that are implemented in the relay. The string should match the title of the `NIP` document. Examples would include `"NIP-01"` and `"NIP-09"`. Client-side `NIPs` SHOULD not be advertised, and can be ignored by clients. |
There was a problem hiding this comment.
What if we made this a list of integers instead of strings? It's less prone to typo errors.
There was a problem hiding this comment.
No strong preference from me here. It's all going to be machine-read anyways, so we can take the position that all NIPs will be integers. The only thing to consider is we have a lot more flexibility with strings, but people can make up numbers just as easily.
|
Looks good! Thank you! |
scsibug
changed the title
This NIP proposes a way of publishing server metadata.
closes #50