Have you written out the architecture anywhere yet? Would love to dive in and understand

I’m open to being convinced but what do we need this for? Is it just private DMs?

Nostr isn’t distributed. Here’s the difference https://www.hivenet.com/post/decentralized-or-distributed-whats-the-big-difference

But it’s the difference between a distributed and decentralised network. Distributed is P2P and it has even more trade offs than decentralised networks.

There are no free lunches

This feels like something fundamentally different from the Nostr protocol. Is that the goal?

I’m open to being convinced but P2P is a different model than client and relay. Is this just for a limited set of features?

I was thinking your password is your decryption key so that even if the place is hacked the service provider could never decrypt your nsec

But you can’t post or decrypt DMs with just an npub

Ima actually thinking about for more normal folks that think in username and password instead of private key and public key.

Create a way to allow them to give an email as username and set a password. Offer 2FA and a reset password flow.

Then they can get their npub and/or their nsec so they don’t have to store it themselves

Eventually the hope is that clients support “login with WhateverWeCallIt” so it’ll insert the nsec automatically into the client (and for clients that store it locally, store it locally)

Further down the line I’d imagine it would be a way for folks to set which clients they want to give what access so that we can give people a way to get rid of the annoying NIP 7 pop ups.

Mostly it is for folks that are less self-custody maxis, but still care about controlling what clients can do with their keys.

I mean for key storage of private keys. Thinking of an oauth type flow to log in to various clients without having to copy and paste the private key.

Any opinion on an end to end encrypted solution? So that even the service provider (custodian) can’t decrypt the keys?

I know it’s not perfect but the current ecosystem for managing keys isn’t smooth enough for everyday users and I’m wondering if there are any solutions on the horizon.

This week’s #NostrTechWeekly with a focus on search and discoverability.

Feedback is always welcome 😊 nostr:note1lx9mp2azn827nf769uft98v8ktexdklq4qzkgemfzxl2vegvq9vq6es2qx

I built https://relay.guide it has some different features but it's a relay explorer.

I use this every week now for #NostrTechWeekly I love it.

That’s the plan! Just need a free weekend 😂

Cool cool. I’m working on relay.guide to help people find and save relays so they can publish kind 10002 events for apps like yours!

Totally makes sense.

If you were gonna try to sense the user’s preferred relays would you pull from the user’s latest kind 3 event? Kind 10002? Or some other way?

Yup it’s at the bottom of the original post’s screenshot

Nice! Any chance you can tell me which relays the event get published to?

Where’s the Nostr calendar at? I’d love to try that

Coinbase finally integrating lightning? https://x.com/brian_armstrong/status/1701806701853507886?s=46 💪