-
Notifications
You must be signed in to change notification settings - Fork 370
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
Sticker messages (m.sticker) #1158
Changes from 1 commit
a87cd82
2989406
91f1834
c471f48
0f8e34d
f421337
c59b879
250ada7
a1fdecc
8dd7bd5
1d9de28
43d9543
90d9960
eb7bbcf
618096e
114e9e2
761ad98
56dc295
02c5afb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -42,8 +42,6 @@ Client behaviour | |
Clients supporting this message type should display the image content from the | ||
event URL directly in the timeline. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we might want to have some warning about sanitising URLs? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As discussed, hopefully clarifying that we expect these to be valid MXC URIs should be enough(?) |
||
|
||
The event ``url`` key must specify a valid ``mxc://`` URI. | ||
|
||
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 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, if we're expecting clients to check this, we should probably say so.