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

Spec compliance: Synapse creates m.room.power_levels without namespace for historical key #14930

Open
turt2live opened this issue Jan 27, 2023 · 2 comments
Labels
A-Spec-Compliance places where synapse does not conform to the spec O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@turt2live
Copy link
Member

  1. Create a new room
  2. Inspect m.room.power_levels content
  3. Note historical

This field is not in the spec and should be namespaced.

@H-Shay
Copy link
Contributor

H-Shay commented Jan 31, 2023

Dumb question but what does the verb "namespace" (as in "namespaced") entail here?

@H-Shay H-Shay added A-Spec-Compliance places where synapse does not conform to the spec T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Blocks non-critical functionality, workarounds exist. labels Jan 31, 2023
@turt2live
Copy link
Member Author

It'll usually be the MSC number which introduces it in org.matrix.msc1234 format (making the field org.matrix.msc1234.historical while unstable). Full grammar/details in the spec

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-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Development

No branches or pull requests

2 participants