b07fe504ed
This is actually doing two things:
* creating `{fragments,modules}/index.md` turns the fragments and modules into
page resources, rather than pages in their own right. We have to update the
shortcodes to match.
* adding `headless: true` means that we don't render the pages.
The net effect is that we don't render pages like
https://spec.matrix.org/v1.4/rooms/fragments/v1-auth-rules/ and
https://spec.matrix.org/v1.4/client-server-api/modules/account_data/.
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
|
|
### Sticker Messages
|
|
|
|
This module allows users to send sticker messages in to rooms or direct
|
|
messaging sessions.
|
|
|
|
Sticker messages are specialised image messages that are displayed
|
|
without controls (e.g. no "download" link, or light-box view on click,
|
|
as would be displayed for for [m.image](#mimage) events).
|
|
|
|
Sticker messages are intended to provide simple "reaction" events in the
|
|
message timeline. The matrix client should provide some mechanism to
|
|
display the sticker "body" e.g. as a tooltip on hover, or in a modal
|
|
when the sticker image is clicked.
|
|
|
|
#### Events
|
|
|
|
Sticker events are received as a single `m.sticker` event in the
|
|
`timeline` section of a room, in a `/sync`.
|
|
|
|
{{% event event="m.sticker" %}}
|
|
|
|
#### Client behaviour
|
|
|
|
Clients supporting this message type should display the image content
|
|
from the event URL directly in the timeline.
|
|
|
|
A thumbnail image should be provided in the `info` object. This is
|
|
largely intended as a fallback for clients that do not fully support the
|
|
`m.sticker` event type. In most cases it is fine to set the thumbnail
|
|
URL to the same URL as the main event content.
|
|
|
|
It is recommended that sticker image content should be 512x512 pixels in
|
|
size or smaller. The dimensions of the image file should be twice the
|
|
intended display size specified in the `info` object in order to assist
|
|
rendering sharp images on higher DPI screens.
|