diff options
| author | Mike O'Bank <111360219+mikeobank@users.noreply.github.com> | 2023-02-25 07:02:48 +0100 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-02-25 15:55:28 -0300 |
| commit | 5a80a906d41a2d756a01addb50f6bead0061fb29 (patch) | |
| tree | 2772c72b178aa60995fe9819adc800334c1775c1 /01.md | |
| parent | ab1f26a3fd8fa0703a4be76091566c92aeadbd4b (diff) | |
Improve `<subscription_id>` specification
- "random" is not an accurate description
- I've noticed long (sha256 hashes in hex) being rejected by some relays. So there seems a need to specify a max length.
- "non empty", cause an empty string could be interpreted as `null`
To be decided:
- Max length number
- Are `subscription_id`s case sensitive?
- Will `subscription_id`s be white space trimmed?
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -55,7 +55,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th | |||
| 55 | * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates. | 55 | * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates. |
| 56 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. | 56 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. |
| 57 | 57 | ||
| 58 | `<subscription_id>` is a random string that should be used to represent a subscription. | 58 | `<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. |
| 59 | 59 | ||
| 60 | `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: | 60 | `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: |
| 61 | 61 | ||