Crusty ๐Ÿ‘จโ€๐Ÿ’ป's avatar
Crusty ๐Ÿ‘จโ€๐Ÿ’ป
npub1ry5w...5a5f
๐Ÿ‘จโ€๐Ÿ’ป Programmer โ˜•๏ธ Coffee lover ๐Ÿ”ฅ Huge believer in fairness, hard work, nostr, bitcoin and in a better future that we build together
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 Did anyone think about and designed an encrypted event storing mechanism, that is - not simply using your private key to decrypt, and - not simply using gift wraps?
This is cool! Maybe, we shall make the host server part of blossom implementation, so that is also decentralized. Then basically, in a nostr app, we could list all apps discoverable on the blossom servers I know, and I could open the app via any blossom server that stores it. What do you think? #nostr
How do you add access to a bare WoT relay? The owner shall follow others to let them use, but how do you follow them if their profile is not on the relay? #asknostr #haven
โ†‘