Skip to content

Commit

Permalink
MSC2705: Animated thumbnails for media (#2705)
Browse files Browse the repository at this point in the history
* Proposal to support animated thumbnails

* add implementation note

* Apply suggestions from code review

Co-authored-by: Alexey Rusakov <[email protected]>

* Clean up the MSC

* Appease the keepers of mimetypes

---------

Co-authored-by: Alexey Rusakov <[email protected]>
  • Loading branch information
turt2live and KitsuneRal committed Feb 11, 2024
1 parent 4b00da2 commit 1c38196
Showing 1 changed file with 52 additions and 0 deletions.
52 changes: 52 additions & 0 deletions proposals/2705-thumbnail-requirements.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
# MSC2705: Animated thumbnails

Users may already upload animated media to the media repository, such as gifs, webp images, and videos.
When this media is used in an event or avatar, many clients are stuck with a static thumbnail until
the user clicks on it to get the full, unedited, file. Some clients however would prefer to show an
animated thumbnail in certain conditions, like when the user is hovering over the message or avatar.

This proposal introduces a new query parameter to the [`GET /_matrix/media/v3/thumbnail`](https://spec.matrix.org/v1.9/client-server-api/#get_matrixmediav3thumbnailservernamemediaid)
endpoint, allowing clients to specifically request an animated thumbnail.

## Proposal

A new query parameter, `animated`, is added to the `/thumbnail` endpoint. It has the following behaviour:

* When `true`: the server SHOULD return an animated thumbnail if possible/supported.
* When `false`: the server MUST NOT return an animated thumbnail.
* When not provided: the server SHOULD NOT return an animated thumbnail.

The default case is a relaxed version of the `false` behaviour to allow server owners to customize the
default behaviour when their users' clients do not support requesting animated thumbnails.

Clients SHOULD respect a user's preference to [reduce motion](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion)
and request non-animated thumbnails in these cases.

The content types which are able to be animated is left as an implementation detail. The following
SHOULD be supported at a minimum, however:

* `image/gif`
* `image/png` or `image/apng` ("APNG" format)
* `image/webp`

The returned content type for an animated thumbnail is additionally left as an implementation detail,
though servers SHOULD use `image/webp` whenever possible.

When media cannot be animated, such as a PDF or JPEG, the server should return a thumbnail as though
`animated` was `false`.

## Alternatives

No significant alternatives.

## Security considerations

Server load could increase when the server tries to thumbnail a large file. Servers are expected to
mitigate this on their own by providing an option to disable the feature or limiting how/when
they will animate the media.

## Unstable prefix

While this proposal is not considered stable, `animated` is specified as `org.matrix.msc2705.animated`
on requests. No unstable endpoints are required due to backwards compatibility being built-in to the
proposal.

0 comments on commit 1c38196

Please sign in to comment.