Dig it! How does the data stay off my app tho? Don’t I still store data linked to a npub? What data do you store in the network?

"This is what freedom looks like." View quoted note →

Separation of concern allows you to independently verify, from your “signer app”, that your “social app” is not mungling events prior to posting. Separation of concern also allows this content to be posted to your “storage relays” of choice, and to be discovered consistently by anyone, from one of the interoperable “trust service” providers. All of which can operate independently from client “social apps”. This separation protects users from nefarious apps … and also protects apps and services from burdensome regulations that otherwise would allow “big social” to capture the market.

I like the concept, but I haven’t seen it in practice. Can you give me an example of an app that uses “storage relays”? Let’s say you have a health app that allows you to fill in doctors forms quickly with your stored personal details.. where would your private data be stored and how?

If you use Nostr, then you’ve seen this separation of concern already in action. The base protocol (NIP-01) specifies how “valid” events are signed by user private keys, and how a client may publish these events to any number of relays. NIP-05 and NIP-65 specifies how users may indicate their preferred read and write relays. NIP-44 specifies how any event may be encrypted (and decrypted) by signing apps (and extensions). Accordingly, most every Nostr client already allows end users to publish these immutable events to relays of their choosing, for storage and retrieval. An EHR app could simply allow encryption and decryption (of certain event content) by user private keys. Of course, details matter… but an identity and data lifecycle such as this could keep users in control at all times, and reduce exposure for client apps from certain data privacy regulations. View article →

Cool! How are you using that in your apps? I’m keen to figure it out practically 🤓

We will be publishing (in a few months) a more detailed legal framework and builders guide for “non-custodial social apps”. In the mean time, we are working on needed infrastructure projects that will help scale Nostr to millions of apps.

TrustR.ing

Sovereign Discovery and Recommendation Services for Nostr.

Hey @Max , @ManiMe and I would love to get in touch with you about Nostr4 / TrustR. I sent you a DM on Primal. Could you check it when you have a moment?

Hey @npub1san2...qjdd , @ManiMe and I tried to contact you regarding the above! Can you check your email? Thanks!

I played around some more and made this too

Now this is unexplored territory. Do you see that there are two audiences here? The heading text “What if no app could control the conversation” is Nostr’s familiar freedom refrain, targeted for users. The sub heading “social apps can operate independently on a network of shared users, with unrestricted access to engage directly … with every one of them.“ is a bit more nuanced. This statement lays out Nostr’s core value proposition for social tech companies, who may or may not be sold on freedom tech. But the statement in between (“this is Nostr’s promise”) doesn’t actually connect the header and sub header … because they are for different audiences. What would be a better header statement to sell Nostr as the social layer for apps? “What if …”

Nostr4

Nostr4

Nostr4 - Freedom for Social Apps

☝🏼 @Morgan Maksoud-Miller

There’s my favorite Mani!