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

MSC3553: Extensible Events - Videos #3553

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Conversation

turt2live
Copy link
Member

@turt2live turt2live commented Dec 7, 2021

Rendered

Blocked by #1767
Blocked by #3551
Blocked by #3552

Preview: https://pr3553--matrix-org-previews.netlify.app

@turt2live turt2live changed the title Extensible Events - Videos MSC3553: Extensible Events - Videos Dec 7, 2021
@turt2live turt2live added kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal proposal-in-review labels Dec 7, 2021
},
"m.thumbnail": [ // optional
{
// A thumbnail is an m.file+m.image, or a small image
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// 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).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
Status: Scheduled - v1.10
Development

Successfully merging this pull request may close these issues.

2 participants