You do not need to sign in with your private key to read notes. Private key is only needed when “writing”. That includes liking, commenting, boosting, etc.

The protocol is young and actively being worked on. The privacy and security risks are known and are being discussed.

The nostr protocol and associated clients we end up having when this hits a critical mass is likely to look very different to what we have and use today.

Reply to this note

Please Login to reply.

Discussion

Thanks for the reply.

I know it's young, and I'm only interested in being involved in some discussion/development.

I understand read access doesn't risk the user's profile. But my point is about securing a user's account when using a client with write access. This is important, and my suggestion is just one idea. I'm interested in what has already been discussed so far.

#[6] has a good writeup on Nostr Security and Privacy Tips worth reading.

https://ron.stoner.com/nostr_Security_and_Privacy/

For completness, here is another article on Nostr privacy worth reading by @1440000bytes on Twitter.

https://consentonchain.github.io/blog/posts/nostr-privacy/

I suppose all this to say the nostr protocol is finding it's feet and is being built before our very eyes.

What an exciting time to be alive with so much innovation around us to tinker with.

Thanks for linking my guide. I plan to expand it out as nostril grows and matures. Linking and feedback are greatly appreciated!