Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federated media multipart/mixed JSON object shouldn't be required to be empty #1952

Open
f0x52 opened this issue Sep 18, 2024 · 1 comment
Open
Labels
spec-bug Something which is in the spec, but is wrong

Comments

@f0x52
Copy link
Contributor

f0x52 commented Sep 18, 2024

Link to problem area:

and describes the media's metadata, if any. Currently, this will
always be an empty object.

https://spec.matrix.org/v1.11/server-server-api/#get_matrixfederationv1mediadownloadmediaid

Issue
MSC3916 point 4 describes the federated multipart/mixed media metadata JSON object as

No properties are yet specified for the JSON object to be returned. One possible use is described by matrix-org/matrix-spec-proposals#3911.

However the spec entry just says 'Currently, this always be an empty object.'

Expected behaviour
Either mention that there are currently no standard fields for the object in spec, or have an explanation similar to other areas in the spec where objects are allowed extending with keys that follow Java package naming convention.
afaik current server implementations already just parse the JSON object but don't enforce it to be empty.

@f0x52 f0x52 added the spec-bug Something which is in the spec, but is wrong label Sep 18, 2024
@turt2live
Copy link
Member

does "Currently" not imply it could become non-empty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec-bug Something which is in the spec, but is wrong
Projects
None yet
Development

No branches or pull requests

2 participants