Any great nostr onboarding for apps that does not store the users nsec? I need it for a normie app. #asknostr

GM! ☕ Your time is your scarcest asset. Make this day count! 🤙

GM! ☕ E2EE event storing on nostr Expectations: - Encrypted data and metadata: Relay shall not know the metadata, nor the content stored - Each event has "unique" owner: Relay shall not be able to group data per owner - Each event encrypted with a unique key: Leaking an event encryption key shall not allow to decrypt all events stored - Event compromise: Leaking account privatekey shall not compromise event - Key offline policy: Event encryption keys shall not be stored on the internet - Owner exclusivity: Only owners shall be able to query their own encrypted notes What else is missing? Please give me a different view. #asknostr

#asknostr Who made @Zap Cooking ?

#asknostr Who would be interested in a private experience on nostr? Like private data storage, private social media (posts only shared with a certain group of people)

#asknostr Is nsec.app bunker working properly for someone?

@Derek Ross How do you collapse the context of Dork so it does not use that much tokens?

GM! ☕ Have a great week! #nostr

The more I think about nsec/privatekey security, the more I bend towards: - keyrotation and - delegation So an ideal scenario is: - You would have an offline keystorage. Can be an old phone with a secure enclave/trusted execution environment/secure element, that you wipe, and put in offline mode forever. - This would store your "master" key. - Then you create a delegated key for your current phone. (also in secure enclave) - Authorize this key with your other key. - Then you use your phone for signing is usual. The rotation can come in, by enabling delegated keys for a certain time only, then you create a new one. Rip this idea off please. #asknostr #nostr

Did youtube just banned in this momemt btcprague Jack Mallers presentation? #asknostr