Conversation
turt2live
changed the title
turt2live
added
kind:core
| }, | ||
| "m.thumbnail": [ // optional | ||
| { | ||
| // A thumbnail is an m.file+m.image, or a small image |
There was a problem hiding this comment.
| // A thumbnail is an m.file+m.image, or a small image | |
| // A thumbnail is an m.file+m.image_details, or a small image |
| The above describes the minimum requirements for sending an `m.video` event. Senders can add additional | ||
| blocks, however as per the extensible events system, receivers which understand video events should not | ||
| honour them. Such examples might include an `m.audio` block for "audio-only" mode (podcasts, etc) or | ||
| an `m.image` to represent the video as a GIF (or similar). |
There was a problem hiding this comment.
You say that an m.image content block could be included to represent a GIF here, though m.image isn't a content block. Did you mean m.file? I'm not sure how that would not collide with the m.file for m.video though.
There was a problem hiding this comment.
The words:
An image fallback is not necessarily possible, despite all the required blocks being possible.
are below though, which also makes me question this paragraph.
github-project-automation
bot
moved this to Tracking for review
in Spec Core Team Workflow
| * `m.video_details` - Similar to `m.image_details` from MSC3552, optional information about the video. | ||
| `width` and `height` are required, while `duration` (length in seconds of the video) is optional. | ||
|
|
||
| Together with content blocks from other proposals, an `m.video` is described as: |
There was a problem hiding this comment.
this could also support m.alt_text from MSC3552 as an optional field. while an appropriate caption would be "Bee Movie (2007)", an a11y alt text would for example contain a short description/synopsis, while the file itself would have an accessible audio track and subs for blind and deaf viewers respectively.
| The newly introduced blocks are: | ||
|
|
||
| * `m.video_details` - Similar to `m.image_details` from MSC3552, optional information about the video. | ||
| `width` and `height` are required, while `duration` (length in seconds of the video) is optional. |
There was a problem hiding this comment.
It would be more suitable to have the duration in a higher granularity. I think milliseconds would be good.
4 participants
Rendered
Blocked by #1767
Blocked by #3551
Blocked by #3552
Preview: https://pr3553--matrix-org-previews.netlify.app