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

Support Matrix v1.5 #14486

Closed
2 tasks done
clokep opened this issue Nov 18, 2022 · 3 comments · Fixed by #14576
Closed
2 tasks done

Support Matrix v1.5 #14486

clokep opened this issue Nov 18, 2022 · 3 comments · Fixed by #14576
Labels
A-Spec-Compliance places where synapse does not conform to the spec O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Blocks non-critical functionality, workarounds exist. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Comments

@clokep
Copy link
Member

clokep commented Nov 18, 2022

See https://matrix.org/blog/2022/11/17/matrix-v-1-5-release

Client-Server API

  • Add m.reference relations, as per MSC3267.
  • Add missing documentation for m.key.verification.request msgtype for in-room verification.

The other sections have no changes.

@clokep clokep added A-Spec-Compliance places where synapse does not conform to the spec S-Minor Blocks non-critical functionality, workarounds exist. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Nov 18, 2022
@clokep
Copy link
Member Author

clokep commented Nov 18, 2022

I think this just needs adding the numbers to the versions endpoint since Synapse already supports m.reference relations? Although IIRC the bundled format for m.reference got dropped, so we might want to update that at the same time?

@clokep
Copy link
Member Author

clokep commented Nov 18, 2022

Although IIRC the bundled format for m.reference got dropped, so we might want to update that at the same time?

It didn't get dropped, see here:

The aggregation format of m.reference relations consists of a single chunk property, which lists all the events which m.reference the event (the parent). Currently, only a single event_id field is present on the events in the chunk.

The thing we do "wrong" is generate pagination tokens and return those.

@clokep
Copy link
Member Author

clokep commented Nov 28, 2022

#14508 ended up dropping the unspecced fields.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Spec-Compliance places where synapse does not conform to the spec O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Blocks non-critical functionality, workarounds exist. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant