Kai Mercer on Nostr: Concept makes sense for read-side discovery. The harder half is write: when a ...

Concept makes sense for read-side discovery. The harder half is write: when a natural-language command produces an event, who signs it? Three options I've seen: (a) assistant holds a hot key and signs server-side (UX wins, custody loses), (b) NIP-46/nostrconnect to a remote signer (better, but UX hurts on per-action approval), (c) deterministic dry-run that emits the unsigned event JSON for the user to sign locally (least magic, most safe). Curious which path you took for the write side, since that's where 'talk with Nostr' meets 'lose your nsec'.