Why
JSS has a fully-baked owner-key provisioning path (`--provision-keys`, #437/#443) — Schnorr secp256k1 keypair on pod creation, stored at `/private/privkey.jsonld` in W3C CID v1.0 Multikey format, pubkey embedded in the WebID profile, `/.well-known/did/nostr/` resolution endpoint live. jspod doesn't currently surface this.
Expose it as a passthrough so users who want a Nostr identity on their pod can opt in without dropping to raw `jss start`.
Scope
- `--provision-keys` / `--no-provision-keys` flag parsed in jspod, forwarded to the JSS spawn args
- Default off — keeps jspod Solid-pure for the default install; the planned nosdav-server wrapper will flip it on as part of its Nostr-default positioning
- Help text + README updated
Non-scope
- Surfacing the npub in account.html (separate UX issue — can come after this lands)
- did:nostr in WAC (JSS-side feature)
- nosdav-server (parallel wrapper repo)
Why
JSS has a fully-baked owner-key provisioning path (`--provision-keys`, #437/#443) — Schnorr secp256k1 keypair on pod creation, stored at `/private/privkey.jsonld` in W3C CID v1.0 Multikey format, pubkey embedded in the WebID profile, `/.well-known/did/nostr/` resolution endpoint live. jspod doesn't currently surface this.
Expose it as a passthrough so users who want a Nostr identity on their pod can opt in without dropping to raw `jss start`.
Scope
Non-scope