-
Notifications
You must be signed in to change notification settings - Fork 3
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
Marking messages as NSFW #108
Comments
i think it should more generally be able to spoiler || like this || since that works inline too. it would also be nice if there was a way in the syntax to add alt text so users may decide whether they want to reveal it |
Spoiler text is discussed in: #33 I think that this is slightly different in the sense that you don't necessarily want to spoiler-text the link, it's just that you want clients not to show the image directly. |
I think this should be called This also gives room to key values like |
## `+draft/rated` This lets users who post media mark their posts as "Not safe for work" to some degree, allowing other users to choose whether or not they want to see this post.
Rationale
Some GUI IRC clients now support image embedding. When users in a channel post an NSFW image, this image is shown without warning/opacity to the user, and there is no way to tell the client that the image is sensitive.
The goal is to add a simple attribute to channel & private messages that tell the clients that the message is NSFW/sensitive, that clients can then use to hide/hide embeds/add a warning/...
An example use case is a chat bot with a command that returns NSFW media: the bot knows in advance that the image is going to be NSFW when posting it. We could also imagine some future client integration where the user can mark the message as sensitive before sending it.
Implementation idea
Define a simple client-tag, e.g.
@+nsfw
, that clients can send in PRIVMSG and NOTICE messages. A message is NSFW/sensitive if it contains that tag.Relates to #33
The text was updated successfully, but these errors were encountered: