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.
Alex Gleason 🐍🚬 /
npub1q3…cd26p
2024-10-21 19:14:44
in reply to nevent1q…7ra2
Author Public Key
npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26pPublished at
2024-10-21 19:14:44Event JSON
{
"id": "c3ee80096b9a5906225ee736f2d376907a84e0f7fb6d94c571d701a9e42287b0",
"pubkey": "0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd",
"created_at": 1729538084,
"kind": 1,
"tags": [
[
"e",
"e4f04dcd7cd221184d1d036c51720dd30690944aea35115aac33776f548f0c42",
"wss://gleasonator.dev/relay",
"root",
"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd"
],
[
"e",
"000001943546a97be1145a1f63489a4d68b987dd7ddf4012c2b71fa5c5cb3fac",
"wss://gleasonator.dev/relay",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"wss://gleasonator.dev/relay"
],
[
"p",
"7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"wss://gleasonator.dev/relay"
]
],
"content": "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.\n\nIt would probably have new subcommands like `nak bunker add \u003cname\u003e \u003cnsec\u003e`, `nak bunker list`, `nak bunker uri \u003cname\u003e`, `nak bunker authorizations \u003cname\u003e`, `nak bunker revoke \u003cid?\u003e`.\n\nAll should accept a flag to the database file, but should default to a fixed filename in the current directory.\n\nA 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.\n\nI 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.",
"sig": "16368b32d7605f3bd2dd64269d154509a88517f1a85d7b9af3bf7f16a4214b7603a8e65341a8315ed1dedd727822552c79d0222a21fab657dbaa9b9655ad4987"
}