Add RoomAndToDeviceKeyTransport
#3185
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
toger5
added
the
PR-Improvement
46 tasks
toger5
force-pushed
the
toger5/test-with-room-and-to-device-transport
branch
from
0be3bf8 to
8c8a5e2
Compare
|
|
toger5
force-pushed
the
toger5/test-with-room-and-to-device-transport
branch
from
9299136 to
e0a5d89
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Warning: This enables the to-device transport developer flag by default with the reasoning, that it will autmatically fallback to room events and hence is backwards compatible.
Needs thorough testing.
This replaces the current dev option of to-device key sharing with a different option that starts with toDevice but will fallback to room events once another member sends a room event.