* * * * *

  Musings on the intersectionality of trigger warnings and spoiler warnings

I was reading XXX XXXXXXXXX XXXXX XXXX XX XXXXXXX [Hold it right there! You
need a trigger warning for that link! –Editor] [Sigh. Fine. –Sean]

(TRIGGER WARNING: XXXXXXXXXX XXXXXXX XXXXXXX)  [STOP! SPOILER! Where's the
spoiler warning? –Editor] {Seriously? I was trying to give a trigger warning,
and now you want a spoiler warning as well? –Sean] [Yes. We can't just go X­
XXXXXXX X XXXXX XXXXXX! –Editor] [Isn't that a spoiler as well? You can't say
that if I can't say XXXXXXXXXX XXXXXXX XXXXXXX –Sean] [… –Editor] [Well? –
Sean] [Deep subject. But yes, you are correct. Carry on. –Editor]

**SPOILER WARNING:** The following trigger warning contains a spoiler for …

[Okay, so how I am supposed to do this? I need to both give a spoiler warning
and a trigger warning for the page, but the trigger warning contains a
spoiler. If you don't want to get spoiled, you could potentially get
triggered. But if I give the trigger warning, those who hate spoilers will
have the story ruined! What now, high and mighty editor? –Sean]

[Well, you are well and truly XXXXXX! –Editor]

[Trigger warning for the foul language, you XXXXXXX! –Sean]


Email author at [email protected]

You are viewing proxied material from gopher.conman.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.