why would it be confusing? The point of delegate keys is to not give an app access to your private keys. Your client should request kinds that it needs to function, that includes kind0/3 and anything else. Your client will still show your root key everywhere, you never need to show the delegate key anywhere.

Why would this be confusing for the average user? They shouldn't even notice. Delegation enables key rotation and cold-storage root keys.

Reply to this note

Please Login to reply.

Discussion

One issue would be DMs, I haven't tested delegation with them and that would be potentially confusing if it's not handled well by the client.

I don't think handling dms would be much different than handling kind 1

you don't have root privkey to generate shared secret, it would have to be based on the delegate key. which means logging in with your root key you wouldn't be able to see any of the dms.

you are correct, hadn't thought about that

probably shouldn't enable DMs when using delegation until we figure out how to make that work seamlessly

so if you send a new kind 0 event from the delegate pubkey, that should be effectively considered the most recent kind 0 from the original pubkey?

might be useful to have relay filter to search author and tags for delegated pubkey? otherwise you will always need 2 filters right?