matrix-org / matrix-org/matrix.org
E2EE implementation guide doesn't cover `sender_device_keys` from MSC4147
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 616
- Forks
- 463
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 19
Description
The `sender_device_keys` property was introduced in [MSC4147](https://github.com/matrix-org/matrix-spec-proposals/pull/4147) and added to Matrix 1.15 via https://github.com/matrix-org/matrix-spec/pull/2122 (with a lot of help from @richvdh). Handling the property is currently not mentioned in the "m.olm.v1.curve25519-aes-sha2" section of https://matrix.org/docs/matrix-concepts/end-to-end-encryption.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the End-to-end encryption guide and find the “m.olm.v1.curve25519-aes-sha2” section. Compare its handling guidance with MSC4147 and the Matrix 1.15 specification, then document the `sender_device_keys` property and verify that the documentation build passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100