added decryptContent method

[greenart7c3]

Currently we just have a generic decrypt method and users have no way to know what the client is trying to decrypt.

• NIP 07
• NIP 46
• NIP 55

[vitorpamplona]

I still think we should just reuse the existing methods and get signers to decrypt first, show the decrypted text to the user and then ask permission to return that text to the app. Users are not trying to control what the Signer sees. The permission to decrypt is irrelevant. They are trying to block what the requesting app can see.

Permission to send ".. something .." back is more relevant than permission to decrypt.

And since you already have the inner content, you can try to explain what the inner content is: list of tags, another event that has a kind and thus you can identify, just text, etc.

[greenart7c3]

Having the new method would be much easier to the user/signer for controlling what the app can see or not.
Parsing the decrypted content also makes building signers much harder and may introduce a lot of issues

[staab]

I don't mind this change, but it doesn't really cover gift wrapping, and the signer design space definitely hasn't been exhausted yet as Vitor points out.

[fiatjaf]

I still think we should just reuse the existing methods and get signers to decrypt first, show the decrypted text to the user and then ask permission to return that text to the app.

nos2x does this.