MSC4193: Spoilers on Media #4193
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| # MSC4193: Spoilers on Media | ||
| This proposal aims to enhance the protocol with more ways to make other users feel comfortable while using the protocol. | ||
| Background | ||
| Matrix includes a way to add a spoiler to text, which hides the text from visibility without explicit user interaction to show the hidden text. However, there is no official way to do this with images. | ||
|
There was a problem hiding this comment. The existing spoilers work on all message types that support
Since 1.10 images actually fall into that category, too, through their media captions. So with this proposal it's now possible to have an image itself be behind a spoiler with its caption behind another spoiler. This made me wonder if we'd need some form of UI guidance on how to treat this situation? For instance, should the spoilers be revealed together or separately? There was a problem hiding this comment. I'd say that spoilers should be done separately. There was a problem hiding this comment. I'd imagine most people would want to configure each separately, as the caption may tell people what is inside the image to help them know whether they want to view it? There was a problem hiding this comment. That sounds sensible and I think c1e9fb4 has addressed it accordingly. |
||
| ## Proposal | ||
| Some other chat protocols, like Discord or Telegram, offer a way to hide potentially sensitive or triggering images in a way that requires the user to explicitly interact with it to show the image. | ||
|
|
||
| In events with an image, there will be an optional `m.spoiler` field as a boolean. If true, then clients should show a blurred version of the image. If not present, it will be assumed to be false. There will also be a `m.spoiler.reason` field as a text value that will optionally display text for why the image has a spoiler. | ||
clokep marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ## Potential issues | ||
| A user with malicious intent may put something inappropriate in the reason field. | ||
| ## Alternatives | ||
| One alternative is the [Spoilerinator](https://codeberg.org/cf/spoilerinator) tool. | ||
|
There was a problem hiding this comment. I would just clarify what this alternative does and the limitations of it. From my brief look at it, it uses Matrix HTML to create an interactive/clickable dropdown to view the image. The limitation of this compared to the MSC would be that not all clients implement HTML, and HTML on mobile clients isn't very good. Additionally this requires a multi-step process of copying the media URL / MXC URI and running this external tool, and most likely doesn't work in encrypted rooms. There was a problem hiding this comment. I've added a note about the limitations. |
||
| ## Security considerations | ||
| None, hopefully. | ||
| ## Unstable prefix | ||
| Until this is stable, clients should use `org.matrix.msc4193.spoiler` and `org.matrix.msc4193.spoiler.reason`. | ||
|
There was a problem hiding this comment.
There was a problem hiding this comment. I've updated it to my Codeberg Pages site. There was a problem hiding this comment. Usually it is fine to use |
||
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.
Implementation requirements:
This comment was marked as duplicate.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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.
Cinny now both respects and supports sending spoilered images. (cinnyapp/cinny#2212)