I've added in the stubs for Private Data and Credentials, which will be stored on relays.
Shortly, I will be adding the details to the Private Data page and adding the info independently using the command line app.
I am also adding the 'owner' concept. Though a safebox has its own nsec, an owner can be designated for the safebox - another npub - that can be notified or challenged for privileged functions.
This is #nostr #safebox
Amethyst saves the Drafts on a Private Relay list users can set up. Would this service be the place for those things as well? They are all encrypted events. You, as the host, can't see what's inside of them.
It shouldn't be an issue. #nostr #safebox is pretty much a full-blown client now. I can implement whatever make sense.
Right now, I am getting ready to chow down on NIP-82 ! I also want to create an alternative for the EU state-sponsored wallets. It won't fly in the EU, but a sovereign payments-health-first wallet will fly in rest-of-world.
Side note: I don't think users like the name "Wallet" to host credentials or health data. Google and Apple are forcing the issue with their "Wallets" but I don't think it's going well.
Yeah, I am trying to get away from using the word 'wallet' though I catch myself using that term. I like the term 'safebox' because it evokes how the trust business was done over long distances and time before international banking and ledgers took over. Digitally, I want to return to that era.
BTW my backend api object is called 'acorn' which the users never see.
The home relay would be deployed as a private relay in a real service. I would need to give thought if there is any material distinction between drafts and private data. Something to think about!
I like this feature because I can save a draft on one device, and resume editing/posting on another. I've found it works very well.
