context warning setting neglected on replies

Two bugs with the content warnings:

1) it's undocumented how to post without a content warning. (the answer is to simply type "cw" with no args)

2) if you type "cw" without args, there is a response saying that the next action will not have a content warning. But if you reply to a msg with a cw, then the user's setting is ignored & the reply mirrors the content warning of the source message.

Note that the web app allows users to reply to a CW'd msg and remove the CW in the reply.

Tags: Open

Comments

Yeah, we need to differentiate between "keep using the CW in replies" and "explicitly no CW"...

– Alex Schroeder 2020-04-14 20:16 UTC


This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.