tal on Nostr: Fascinating! is the code publicly available? My concern is it's aimed more towards ...
Fascinating! is the code publicly available?
My concern is it's aimed more towards power-users with dedicated hardware running the nsecbunker daemon.
I've been envisioning something simpler to kick things off: a "Vault data" event kind ({vault_key -> encrypted_data}), which can be stored on public relays. Apps could then pull all npub's vault keys and request continuous read/write permissions for specific keys through an extension.
This approach eliminates the reliance on the browser's local storage as the "long-term" memory for personal data, as everything can be restored from the vault.
It's a basic idea in need of more thought
My concern is it's aimed more towards power-users with dedicated hardware running the nsecbunker daemon.
I've been envisioning something simpler to kick things off: a "Vault data" event kind ({vault_key -> encrypted_data}), which can be stored on public relays. Apps could then pull all npub's vault keys and request continuous read/write permissions for specific keys through an extension.
This approach eliminates the reliance on the browser's local storage as the "long-term" memory for personal data, as everything can be restored from the vault.
It's a basic idea in need of more thought