That's really neat! I just want to clarify a few things - it seems like the nsecBunkerClient has to stay online and listens out for "note signature requests", right? And then, it approves these requests based on a certain set of rules? Where are these rules stored? Do you have plans to evolve it for more complex rule sets? (for example, "a specific npub is authorized to post on my behalf for the next hour only and a max of 5 notes")
However, I think what I'm searching for is slightly different. I'm envisioning something like a private vault (think Amazon's style, but implemented on nostr relays). My application would then ask the extension for read/write permissions for a specific key in this encrypted vault. After a user logs in with nostr, the app could ask for access to some of the user's private data, pending the user's approval.
Down the line, this could be integrated with nsecBunkerClient. In this scenario, you could allow another npub access to your private vault. The client would manage the decryption and encryption for that user, following a set of specified rules.
tal /
npub1ww…yxmjl
2023-05-31 12:22:27
in reply to nevent1q…m450
Author Public Key
npub1ww82xmhhfv4vszlm8zrmgp3hclwd7a82dmkh83cckuvnxyaep7dsnyxmjlPublished at
2023-05-31 12:22:27Event JSON
{
"id": "c1a22600ac71d81b042980cb186fe3dd4e08f69d024fbabffb0c35185a94c343",
"pubkey": "738ea36ef74b2ac80bfb3887b40637c7dcdf74ea6eed73c718b7193313b90f9b",
"created_at": 1685528547,
"kind": 1,
"tags": [
[
"e",
"e1a66c02ed3148cbef99df96c2a7934ff3132e47d4bf3fe1de3ccc088a0617d5",
"",
"root"
],
[
"e",
"f962bc5a1d03d6dae84e0e50784b2574a399a6d9f26b3b98491defb800318669",
"",
"reply"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"p",
"e4a1d3500841adb6734875d65c45e17b94d4d35db4d128dd288ca381f9bdcc90"
],
[
"p",
"f8b7656588856e324914bcd91beb12f27f10775304cdd140bc6f431b0d0328c2"
]
],
"content": "That's really neat! I just want to clarify a few things - it seems like the nsecBunkerClient has to stay online and listens out for \"note signature requests\", right? And then, it approves these requests based on a certain set of rules? Where are these rules stored? Do you have plans to evolve it for more complex rule sets? (for example, \"a specific npub is authorized to post on my behalf for the next hour only and a max of 5 notes\")\n\nHowever, I think what I'm searching for is slightly different. I'm envisioning something like a private vault (think Amazon's style, but implemented on nostr relays). My application would then ask the extension for read/write permissions for a specific key in this encrypted vault. After a user logs in with nostr, the app could ask for access to some of the user's private data, pending the user's approval.\n\nDown the line, this could be integrated with nsecBunkerClient. In this scenario, you could allow another npub access to your private vault. The client would manage the decryption and encryption for that user, following a set of specified rules.",
"sig": "3dc0822caa51f5af1ae53ff4af2a2aa0ab4316acc566a3d376dda82ba87e805fbbc13877e8aa62e5d732784b33eaab2855f46b2f0b162bb4ddcfeba5f7d62d83"
}