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

Consent warnings #5550

Closed
SoniEx2 opened this issue Nov 9, 2017 · 9 comments
Closed

Consent warnings #5550

SoniEx2 opened this issue Nov 9, 2017 · 9 comments
Labels
A-Composer O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team

Comments

@SoniEx2
Copy link

SoniEx2 commented Nov 9, 2017

Description

I'd like a simple inline consent warnings mechanism. Implementation details TBD.

Some examples of how to display them:

my IRC client

[image description: my IRC client, showing lines "Soni | can matrix do this? [Hidden Text 1]" and "* | Hidden Text 1 > < (Copy and paste to expand)"]

mastodon (closed)
mastodon (open)

[image description: mastodon, showing a post with a consent warning. first image shows "cw example" followed by a "show more" button, second image shows "cw example" followed by a "show less" button and the text "hello world"]

(Note that in the IRC client case above, the client supports true inline CWs, and even multiple CWs per message, with text in between. For compatibility reasons it would be nice if we did so too, even if we only send "normal" CWs.)

@turt2live
Copy link
Member

(for the purposes of adding more keywords: this is also known as spoiler text)

@SoniEx2
Copy link
Author

SoniEx2 commented Nov 9, 2017

yeah but suicide notes are often considered too much for "spoiler text", while acceptable for consent warnings (I deal with those as part of a suicide help channel). they have slightly different perceived semantics and "consent warning" mostly includes spoilers, so it is a better choice.

@turt2live
Copy link
Member

The user-facing feature probably wouldn't have a label (it would just be something that says "click to reveal"). Just wanted to add more keywords to the ticket to avoid duplicates in the repository.

@SoniEx2
Copy link
Author

SoniEx2 commented Nov 9, 2017

that's dangerous UX for mental health channels...

and that's bad UX for spoilers, too. you'd have no idea what the spoilers are about until you spoil them.

@richvdh
Copy link
Member

richvdh commented Nov 9, 2017

https://github.com/matrix-org/matrix-doc/issues/604 is the spec issue for this fwiw

@uhoreg
Copy link
Member

uhoreg commented Aug 31, 2019

matrix-org/matrix-react-sdk#3018 implements spoilers, but only as an inline element so might not completely solve this issue

Edit: also does not seem to implement anything for actually sending spoilers yet

@SoniEx2
Copy link
Author

SoniEx2 commented Aug 31, 2019

inline element is the only proper way to solve this issue.

@SoniEx2 SoniEx2 changed the title Content warnings Consent warnings Aug 31, 2019
@shmerl
Copy link

shmerl commented Feb 9, 2021

I'd add that this should also apply to images, not just to text.

@kittykat kittykat added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround A-Composer and removed P3 Help Wanted Extra attention is needed labels Jan 31, 2022
@janogarcia janogarcia added the X-Needs-Product More input needed from the Product team label Jan 31, 2022
@robintown
Copy link
Member

The original request of this issue, inline spoilers, has been supported for some time, so I'm closing this. element-hq/element-meta#869 tracks having a nicer way to send them, and #18061 and https://github.com/vector-im/element-web/issues/18062 track support for non-inline content warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Composer O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team
Projects
None yet
Development

No branches or pull requests

10 participants