mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-12 18:36:24 +00:00
limitations->limitation fix, integer solution, nested obj disclaimed
This commit is contained in:
parent
154ffc1a84
commit
2db9908166
16
66.md
16
66.md
@ -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
|
||||
```
|
||||
[ "L", "nip11.limitations" ]
|
||||
[ "l", "payment_required", "nip11.limitations" ] //nip11.limitations.payment_required==true
|
||||
[ "l", "auth_required", "nip11.limitations" ] //nip11.limitations.auth_required==true
|
||||
[ "L", "nip11.limitation" ]
|
||||
[ "l", "payment_required", "nip11.limitation" ] //nip11.limitation payment_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>
|
||||
- `NIP-66` leverages a draft NIP for geo tags, see [YAGT](https://github.com/nostr-protocol/nips/pull/952)
|
||||
```
|
||||
|
Loading…
Reference in New Issue
Block a user