-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate the sender_key
and device_id
on Megolm events
#1101
Conversation
MSC: matrix-org/matrix-spec-proposals#3700 ([Markdown](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3700-deprecate-sender-key.md)) The language around `m.room.encrypted` is a bit awkward because *technically* you can use the event to represent non-Megolm events, however that's considered an edge case at this time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall! However I don't see a change here corresponding to this paragraph in MSC3700:
When clients receive an encrypted event with an unknown session they will need to send a key request to all clients, rather than the device specified by
sender_key
anddevice_id
. This is the current behaviour used by Element clients.
and am failing to find an existing paragraph in the spec that mentions this.
@anoadragon453 please take another look |
…epoints rather than bytes (matrix-org/matrix-spec#1101)
MSC: matrix-org/matrix-spec-proposals#3700 (Markdown)
The language around
m.room.encrypted
is a bit awkward because technically you can use the event to represent non-Megolm events, however that's considered an edge case at this time.Preview: https://pr1101--matrix-spec-previews.netlify.app