Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

To-device messages have an unspecified, required message_id field #14167

@babolivier

Description

@babolivier

#9686 introduced a message_id field in to-device messages for tracing purposes, which isn't in the spec, and which Synapse sends to all to-device messages it sends. This is confusing because the name does not imply it's intended to live out of the spec.

In an even more problematic way, Synapse also mandates it for incoming to-device EDUs (ref), meaning that other server implementations have to also implement it.

Also see discussion in #matrix-spec: https://matrix.to/#/!NasysSDfxKxZBzJJoE:matrix.org/$PWq5IoB9WUfKdUiyRjTOUG5tCFNT6pBcBT8uwUcQVTg?via=matrix.org&via=libera.chat&via=element.io

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-E2EEEnd-to-end encryption for Matrix clientsA-Spec-Complianceplaces where synapse does not conform to the specO-UncommonMost users are unlikely to come across this or unexpected workflowS-MinorBlocks non-critical functionality, workarounds exist.T-DefectBugs, crashes, hangs, security vulnerabilities, or other reported issues.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions