Trigger Policy

I have made the decision to not put any warnings, trigger or otherwise, to the daily drabbles that appear on this blog. Please be aware that anything that shows up might be upsetting and proceed with caution. It is impossible for me to warn adequately as triggers are often too specific for a generalized warning to be useful.

Below is the outdated version of the Trigger Policy, which still basically holds true for anything that isn’t the daily drabbles, but which no longer really reflects all my personal views on the topic. Thank you for understanding. If you have suggestions or anything, feel free to email me or comment here.


I will try to warn adequately but still beware that what I write might upset you.

A trigger is defined here as something that sets off an unwanted or uncontrollable response in the mind. The geek feminism wiki has this to say about that:

[Trigger warnings] are designed to prevent people who have an extremely strong and damaging emotional response (for example, post-traumatic flashbacks or urges to harm themselves) to certain subjects from encountering them unaware. Having these responses is called “being triggered”.

I think that is a good definition.

On this blog I will be using trigger warnings to warn for the most upsetting things. For less upsetting things, that still need some tiptoeing around, I will be using the phrase ‘content warning‘.

For measure: a story about a species of snails that lamprey themselves to the sides of people and make them form emotional bonds with them would have a content warning for body horror and unpleasant, unwanted thought-patterns. A story where someone uses these snails to rape emotionally confused people, would have a trigger warning for rape and for the body horror and unwanted thought-patterns. Stories about suicide are generally highest tier of upsetting.

I can’t claim I will always know which warning would be best. If you think I should change a warning, or add a warning, contact me somehow (email, twitter, comments) and I will most likely fix this.


Further reading: