Jump in the discussion.

No email address required.

"Trigger warning" is now considered harmful language. Instead they suggest using "content note" for the following reason:

The phrase can cause stress about what's to follow. Additionally, one can never know what may or may not trigger a particular person.

Genuine 🤡🌎 shit.

Jump in the discussion.

No email address required.

Dramapilled DEI-chads

Jump in the discussion.

No email address required.

Trigger warning: trigger warning.

Jump in the discussion.

No email address required.

I remember An article posted to Reddit about how trigger warnings were ineffective because it would put the person in a hot state before reading the “triggering” post.

I like that their solution is just changing the warning label lol


:#marseyastronaut:

Jump in the discussion.

No email address required.

trigger warnings were ineffective because it would put the person in a hot state before reading the “triggering” post.

The idea of a trigger warning is that, if you have PTSD due to being in a gunfight etc, you read the trigger warning that the video/essay/etc is going to contain references to gunfighting or the sights and sounds of a gunfight and you don't watch it.

You're not meant to read the warning, decide that it applies to you and then read the fricking post anyway. That's pretty dumb.

I dislike the way trigger warnings have been ridiculed so much, they do have a purpose. Some people - especially veterans - really do get triggered though by the things they see and hear, especially if they have genuine PTSD.

Jump in the discussion.

No email address required.

I can get behind this. 'Trigger warning' is just irritating wording, 'content note' is a much better term and I think more similar to what was used before.

Some people really do get triggered though by the things they read, especially if they have genuine PTSD. I hate the way it's been ridiculed by overuse.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.