I like this for sure. You sound very familiar with nak. Can I ask you as customer service for software that you didn't egent write?
Say that I have nsec 01 and nsec 02 and I want to alternate between the two (not mulsig, each key signs different events).
Is there a way to alternate between the keys without raw dogging it on my shell? Say:
~> nak blossom --server blossom.azzamo.net --sec 01 upload image.png
{"sha256":"38c51756f3e9fedf039488a1f6e513286f6743194e7a7f25effdc84a0ee4c2cf","url":"
"}
~> nak blossom --server blossom.azzamo.net --sec 02 delete 38c51756f3e9fedf039488a1f6e513286f6743194e7a7f25effdc84a0ee4c2cf
(Should fail ad nsec 02 can't delete nsec 01 blobs).
Is there a way that I can store my nsecs somewhere and alternate between nsec01 and nsec02 using their pubkeys, etc?
You can use environment variables maybe? $NOSTR_SECRET_KEY is used by default by nak if nothing is specified, but you could just use arbitrary environment variables while constructing your commands.
Thanks for coming to the rescue Fiatjaf. This is better for sure, and now that you mentioned it... It was on the README the entire time 🤣 (apologies for wasting your time).
It would be awesome if we could use nak --connect '[bunker url]' multiple times and then reference the nsecs by npub or index though. I understand that I can just set bunker urls (or nsec for all that matters) in env variables, but for most purposes this isn't much safer than just rawdogging the Bunker urls or nsecs directly.
The examples in the readme had me 😵💫 feels like i missed a prereq. Or maybe i shouldnt start things before bed
Thread collapsed
Thread collapsed
Thread collapsed
it seems fiat answered this already. i learnt a new thing as well!
Thread collapsed