Don't send every DataMessage unsealed #268
Merged
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.
@Schmiddiii writes in Whisperfish Matrix channel:
I took a look at the code, and I arrived at the same conclusion, and developed a fix for the logic. So: the code previously made every
DataMessage
be sent identified/unsealed, whereas the intention is to use identified/unsealed sending for 1)EndSession
messages and 2) messages to other own devices.This has already received some real-world testing, and seems to work fine. As such, I was asked to make it a PR, so here it is!