Add blinded community session encrypt encode/decode with Session Pro functions #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for blinded community messages in the new high-level API for encoding/decoding messages with Session Pro support. Prior to this, you'd have to manually decode a blinded community message with
decrypt_from_blinded_recipientbefore handing over the blob todecode_for_community.With this PR the manual decoding using
decrypt_from_blinded_recipientis removed and you can instead calldecode_for_community_inboxwhich under the hood, callsdecrypt_from_blinded_recipienton behalf of the caller.This function supports both new/old style messages where the Pro metadata is embedded in the content (the legacy path) and Pro metadata is embedded in the envelope (the modern path).