@@ -164,7 +164,7 @@ We do _not_ use the "Transit" portion of Magic Wormhole: all communications are
...
@@ -164,7 +164,7 @@ We do _not_ use the "Transit" portion of Magic Wormhole: all communications are
- the code is encoded in a QR code using a variation of a "wormhole URI"
- the code is encoded in a QR code using a variation of a "wormhole URI"
- "Wormhole URIs" are currently specified for file-transfer: https://github.com/magic-wormhole/magic-wormhole-protocols/blob/main/uri-scheme.md
- "Wormhole URIs" are currently specified for file-transfer: https://github.com/magic-wormhole/magic-wormhole-protocols/blob/main/uri-scheme.md
- our scheme doesn't use file-transfer (it is a custom protocol) so we need a different scheme (likely with some overlap to the above)
- our scheme doesn't use file-transfer (it is a custom protocol) so we need a different scheme (likely with some overlap to the above)
- something like `ps-pair:4-hurricane-equipment` with defaults for AppID (`private.storage/pairing`), version (`0`), and rendezvous (`mailbox.mw.leastauthority.com`)
- something like `ps-pair:4-hurricane-equipment` with defaults for AppID (`private.storage/magic-folder/invites`), version (`0`), and rendezvous (`mailbox.mw.leastauthority.com`)
- that is, the QR code encodes the bytes: `ps-pair:4-hurricane-equipment`
- that is, the QR code encodes the bytes: `ps-pair:4-hurricane-equipment`
- we _could_ include query-type arguments for the other parts (similar to file-transfer) if we need
- we _could_ include query-type arguments for the other parts (similar to file-transfer) if we need
- (our application could register as the handler for `ps-pair:` URIs).
- (our application could register as the handler for `ps-pair:` URIs).
