diff options
| author | kuiperanon <164939804+kuiperanon@users.noreply.github.com> | 2024-04-09 11:25:05 -0500 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2024-04-10 12:53:59 -0300 |
| commit | b765b3c0301958d46115b834872bbd0c8bac588c (patch) | |
| tree | 8bc9daedd6d8bdb30717859b0813e6d8c52c9dd3 | |
| parent | b224f6d05d5b208b632e8e1f5ac489b7f27079ae (diff) | |
Clarify use of ambiguous terminology in spec of bunker token
It's very confusing as to whether it refers to remote user pubkey vs remote signer pubkey. This is complicated further by the typo in the explanation of "remote signer pubkey".
| -rw-r--r-- | 46.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -25,7 +25,7 @@ This is most common in a situation where you have your own nsecbunker or other t | |||
| 25 | The remote signer would provide a connection token in the form: | 25 | The remote signer would provide a connection token in the form: |
| 26 | 26 | ||
| 27 | ``` | 27 | ``` |
| 28 | bunker://<remote-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> | 28 | bunker://<remote-user-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> |
| 29 | ``` | 29 | ``` |
| 30 | 30 | ||
| 31 | This token is pasted into the client by the user and the client then uses the details to connect to the remote signer via the specified relay(s). | 31 | This token is pasted into the client by the user and the client then uses the details to connect to the remote signer via the specified relay(s). |