teatwo's avatar
teatwo
_@studio.teatwo.dev
npub1xkym...5few
teatwo is derived from "T2". Author: https://api-docs-30b126.gitlab.io
teatwo's avatar
teatwo 10 months ago
Most of security features are imaginary futures, because they are designed to deal with incidents that haven't happened yet.
teatwo's avatar
teatwo 10 months ago
We are playing a role!
teatwo's avatar
teatwo 10 months ago
> 1. Everything is connected. > 2. Everyone knows everything, eventually. > 3. I know nothing. 🌏
teatwo's avatar
teatwo 10 months ago
Do you think NIP44 is practical for sharing secrets other than Nostr like Bitcoin private key? NIP44 can be used to share keys only between two parties, such as you and a client software in local, as a cipher key for encryption on the filesystem. The NIP44 encrypted secret is either decrypted in memory on the client machine and used by the client software, or may be sent encrypted to the other party on the network as a multisig such as an LSP or a delegated key to custodial service. NIP44, as designed, does not require uploading to a relay server. What you need are your NSEC key and the party's NPUB key. If you have access to the relay server, you can get a directory of public keys, but that's not required. #asknostr
teatwo's avatar
teatwo 10 months ago
Grug doesn't like debug. Therefore he is going to lean towards code design and environment that is highly debuggable during running. image