Christopher Silsby (he/him)<p>Ran into a random <a href="https://hcommons.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WordPress</span></a> issue today. Ok, isn't really WordPress's fault, but a <a href="https://hcommons.social/tags/modsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>modsec</span></a> false positive. In trying to protect from <a href="https://hcommons.social/tags/SQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SQL</span></a> injections, our firewall sees WordPress posts as dangerous. So every once in a while, a professor assigns a post about or related to the topic of sleep. </p><p>This is a problem for modsec. It thinks anyone writing a parenthetical clause after talking about sleep (like this) is trying to hack our server. </p><p>But WordPress doesn't have a way to process the error code, and gives the students a wholly unhelpful error message. </p><p>Luckily, this has now happened about 3 or 4 times in the past 15 years. So I know to look out for it. And to recommend emdashes instead of parens. See, my dissertation writing IS useful in my EdTech job! <a href="https://hcommons.social/tags/EmdashPride" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EmdashPride</span></a> <a href="https://hcommons.social/tags/DigitalHumanities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalHumanities</span></a></p>