Missing `meta` properties for attachments via Mastodon API
What happened?
Sharkey's not including attachment metadata (specifically, image width and height) in the expected place in the JSON responses via the Mastodon API.
Discovered via https://github.com/pachli/pachli-android/issues/611
What did you expect to happen?
Fetch a status via the API that has media attachments, e.g., https://blahaj.zone/api/v1/statuses/9rvuh2aoi62s0z9a
Here's the first media attachment (an image):
"media_attachments": [
{
"id": "9rvuh32oi62s0z91",
"type": "image",
"url": "https://cdn.blahaj.zone/files/1cfabfe1-25a0-4c17-89b0-1ce5843a6000.png",
"remote_url": "https://cdn.blahaj.zone/files/1cfabfe1-25a0-4c17-89b0-1ce5843a6000.png",
"preview_url": "https://cdn.blahaj.zone/files/thumbnail-78d5e4cc-d5d8-4262-9f78-ee0f355d6b94.webp",
"text_url": "https://cdn.blahaj.zone/files/1cfabfe1-25a0-4c17-89b0-1ce5843a6000.png",
"meta": {
"width": 1920,
"height": 1080
},
"description": "PixelArt forest: At the center, a small cabin shaped like a teapot.To it's left a large tree and a well. On it's right, a character in a blue hood sits at a campfire. The background is many layers of trees, lit by an orange sky and sunrays",
"blurhash": "e8CsB8kV=^$g5Ao[ocRSjGj[02oc59S4$%~SofSfbYM}]qn%-nS3W;"
},
The width
and height
properties on the meta
block are a level too high in the structure. There should be an original
property, so it would look like this:
"meta": {
"original": {
"width": 1920,
"height": 1080
}
},
Ideally there would also be size
and aspect
properties, and a small
property with the same sub-properties for sizing preview images, like this:
"meta": {
"original": {
"width": 1200,
"height": 600,
"size": "1200x600",
"aspect": 2
},
"small": {
"width": 678,
"height": 339,
"size": "678x339",
"aspect": 2
}
},
Version
2024.2.0-beta.12
Instance
blahaj.zone
What type of issue is this?
server side
Contribution Guidelines By submitting this issue, you agree to follow our Contribution Guidelines
-
I agree to follow this project's Contribution Guidelines -
I have searched the issue tracker for similar issues, and this is not a duplicate.