nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-13 23:39:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Replace extra endpoint with query param

Browse Source
This commit is contained in:
arthurfranca 2023-06-28 11:23:46 -03:00
parent af4f963e0c
commit b48a4d0ca7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
34.md
View File

@ -44,14 +44,14 @@ Into this:
`SELECT * FROM events WHERE kind in (1) ORDER BY nip34a DESC LIMIT 5`
## Relay Extra Endpoints
## Relay Connection URL Query Parameter
`Relays` MUST make available an extra URL `clients` can connect to for each supported NIP-34 algorithm.
For each supported NIP-34 algorithm, the `relay` MUST allow `clients` to specify the algo as a `nip34` query param on connection URL string.
For example, if supporting the NIP-34a algo, a `relay` whose regular URL is `wss://relay.url/r1` must
also respond at `wss://relay.url/r1/nip34a`, i.e. the additional URL has the algo field name appended to the path.
also respond at `wss://relay.url/r1?nip34=a`.
Then when `clients` connect to `wss://relay.url/r1/nip34a` and request events using `limit`
Then when `clients` connect to `wss://relay.url/r1?nip34=a` and request events using `limit`
filter attribute, the relay will automatically sort events in **descending** order by the `nip34a` event field instead of by `created_at` when replying. Clients can still override the chosen algorithm if using the
`nip34` filter attribute.