Alex on Nostr: Ideally you can add and remove multiple named keys. You can list keys. You can ...
Ideally you can add and remove multiple named keys. You can list keys. You can generate multiple bunker URIs for each key, and limit access to each with NIP-01 filters. Authorizations can be reviewed and revoked.
It would probably have new subcommands like `nak bunker add <name> <nsec>`, `nak bunker list`, `nak bunker uri <name>`, `nak bunker authorizations <name>`, `nak bunker revoke <id?>`.
All should accept a flag to the database file, but should default to a fixed filename in the current directory.
A JSON file would be fine. Ideally it could be encrypted with a password, but don't know how to overcome challenges with running it in systemd (especially with auto-restart) that way.
I am also not sure what happens to the regular `nak bunker` without any subcommand. It can continue to work like it does, or be removed in favor of subcommands.
It would probably have new subcommands like `nak bunker add <name> <nsec>`, `nak bunker list`, `nak bunker uri <name>`, `nak bunker authorizations <name>`, `nak bunker revoke <id?>`.
All should accept a flag to the database file, but should default to a fixed filename in the current directory.
A JSON file would be fine. Ideally it could be encrypted with a password, but don't know how to overcome challenges with running it in systemd (especially with auto-restart) that way.
I am also not sure what happens to the regular `nak bunker` without any subcommand. It can continue to work like it does, or be removed in favor of subcommands.