nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-19 22:35:50 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

limitations->limitation fix, integer solution, nested obj disclaimed

Browse Source
This commit is contained in:
sandwich 2024-01-23 19:46:42 +00:00
parent 154ffc1a84
commit 2db9908166
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
66.md
View File

@ -98,11 +98,21 @@ Tags should be used to represent the Relay's abilities and meta at any given poi
- Boolean values from `NIP-11`, for example - Boolean values from `NIP-11`, for example
``` ```
[ "L", "nip11.limitations" ] [ "L", "nip11.limitation" ]
[ "l", "payment_required", "nip11.limitations" ] //nip11.limitations.payment_required==true [ "l", "payment_required", "nip11.limitation" ] //nip11.limitation payment_required==true
[ "l", "auth_required", "nip11.limitations" ] //nip11.limitations.auth_required==true [ "l", "auth_required", "nip11.limitation" ] //nip11.limitation auth_required==true
``` ```
#### NIP-11 Integer Values
Any NIP-11 values that are integers should not be included as NIP-32 labels, instead they should use the `nip11` tag.
```
[ "nip11", "65535", "limitation.max_message_length" ]
```
#### NIP-11 Nested Objects
NIP-11 nested objects are not supported by NIP-66 at this time (For example, fees)
#### Geo tags <sup>NIP-YAGT</sup> #### Geo tags <sup>NIP-YAGT</sup>
- `NIP-66` leverages a draft NIP for geo tags, see [YAGT](https://github.com/nostr-protocol/nips/pull/952) - `NIP-66` leverages a draft NIP for geo tags, see [YAGT](https://github.com/nostr-protocol/nips/pull/952)
``` ```