Perhaps have a primary key, and then sub keys which allow you access across platform but not revealing your primary key.

A fine medium, protects your NSEC while allowing multiple sign in.

Sub keys could be revocable, or have read/write privileges enabled/disabled, and just be made to copy, or mirror content relayed from the primary key.

Might be helpful to multiple platform interaction for those who use multiple instances.

Reply to this note

Please Login to reply.

Discussion

Key revocation is one of the most complicated schemes one can build. It opens the door to attacks that don't exist today and now suddenly every client needs to worry about multiple keys. Nostr is suddenly not simple anymore.

So you'll have it done by mid month?

No, I don't think I like any idea that involves key revocations.

😂😂😂