matrix-org / matrix-org/matrix.org
E2EE implementation guide mentions blocking devices but links to attachment encryption
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 616
- Forks
- 463
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 19
Description
The "Blocking / Verifying devices" section in https://matrix.org/docs/matrix-concepts/end-to-end-encryption mentions:
> It should be possible for a user to mark each device belonging to another user as 'Blocked' or 'Verified', through a process detailed [in the spec](https://matrix.org/docs/spec/client_server/r0.4.0.html#sending-encrypted-attachments).
The link points to the "Sending encrypted attachments" section of the spec, however, which seems totally unrelated. I'm actually not quite sure what "process" is meant here. As far as I understand, device verification has a concept of verified or not verified but not actively blocked?
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 Matrix end-to-end encryption guide and locate the “Blocking / Verifying devices” section. Compare its link with the referenced Client-Server API specification and determine which verification process the text intends to describe. Done means the link and wording accurately point readers to the relevant device-verification guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100