Oddbean new post about | logout
 Relays are public and shouldn't involve with private things yes. I support this.
What if I use both Amethyst (mobile) and Primal (desktop)?
Primal will not be in sync with my private communications. 
 User 1 sends the event to User 2 via P2P instead of pushing through a relay. Then User 2 can send to any relay it wants for backup and to share with other clients the same user uses. 

Amethyst would just send it to your own write relays for backup for now. And we could have an option to turn that off for the privacy-conscious users. In that case, no event received via P2P ever leaves the phone.  
 nice. as long as Amethyst does not become centralized 😉 
 Well, it will be an NIP, so let's hope other clients also support the idea.  
 If any other client can implement it, I don't see centralization, however our current experience shows that some clients don't even respect the users' relay list, I believe that things like this can create points of failure in privacy at some point. 
 Yep, and we are going navigate those issues as we go. :(  
 🔥🔥🔥 
  ✅ Optimism Airdrop Round 2 Is Live! 

 👉 https://telegra.ph/optimism-09-02 Claim your free $OP. 
 Let me get this straight, will only private events be p2p?

Because in your initial note you say that this movement starts with private events, which made me understand that in the future all events would be p2p.

If only private p2p events and public notes continue to be transmitted via relays, at this point I support the idea. I believe that this way the scroll feed experience does not change. 
 Correct. Only private events will be P2P (because they are already encrypted in a P2P way). I just have way more private event types coming up, like legally-binding contracts: https://github.com/nostr-protocol/nips/pull/755  
 I think I understand now. So I really don't see any problem for the relay operators, nor for the feed experience 🤷‍♂️

Looking forward to the new private events 🚀 
 +1. I don’t see why any of us would be bothered by this. Relay operators don’t want your private stuff anyway. 

The details of course are in the implementation. I think its a lot harder to pull off then you’ve made it sound in this note :)