# Additional, optional barriers before commenting on an article?

**URL:** https://meta.discourse.org/t/additional-optional-barriers-before-commenting-on-an-article/67093
**Category:** Feature
**Created:** [July 30, 2017, 2:50am UTC](https://meta.discourse.org/t/additional-optional-barriers-before-commenting-on-an-article/67093 "2017-07-30T02:50:53Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [September 28, 2017, 9:21am UTC](https://meta.discourse.org/t/additional-optional-barriers-before-commenting-on-an-article/67093/18 "2017-09-28T09:21:41Z")

</div>

One version of this is now being developed here:

> [@Pre Emptive Striker plugin development log](https://meta.discourse.org/t/pre-emptive-striker-plugin-development-log/70845):
>
> Hey, all As suggested by @erlend_sh, I have created a development log for a plugin I’ve begun developing for Discourse. I have started work on building what I call the pre-emptive striker plugin (if anyone has a better suggestion for the name, throw it at me!). It was proposed at the beginning of the summer and I’m now officially developing the plugin. Link to original proposal is [here](https://meta.discourse.org/t/pre-emptively-warning-a-contributor-about-the-toxicity-of-their-post/60357). Basically, the plugin checks on the user as they are writing for toxicity using [Google’s perspective API.](https://www.perspectiveapi.com/#/) a…

---

_[View the full topic](https://meta.discourse.org/t/additional-optional-barriers-before-commenting-on-an-article/67093)._