Interesting to see how it works. 👍

I assume then that each app connection is seperate and can be authorised or disabled as needed.

I have wondered how a social media managers or allowing employees to post to company accounts would work on nostr without sharing the private key but I guess something like this could be used.

The next thing I would like to see is a way to salvage an identity if your nsec was compromised. Perhaps some way to set a fallback key for nostr such that if your nsec was compromised you could sign a certain message deactivating signing from the initial nsec (or simply broadcasting a message to relays to reject messages signed with old key) and allowing signing from a previously established fallback nsec. Perhaps this could be done in such a way to keep the publicly identifiabe npub the same as it was initially to allow continuity of identity while still having the fallback keys for all future signing and encryption.