Integrate CleanSpeak for moderation

[trex]

This change implements an integration with CleanSpeak for content filtering and moderation.

For both the createThread and createPost resolvers, we make a call to CleanSpeak's /content/item/moderate API and check the result to see if the content is allowed or rejected. We set published and abusive variables on the Thread or Post, which determine if the Thread or Post may be retrieved from the database.

The filters in CleanSpeak are highly tuneable, so we can run tests and adjust in development before we deploy an initial moderation policy and go live.

[trex]

@moonquay do yo want to review this?

[moonquay]

Oh cool thanks @trex for doing that! I see there's now a 'moderator' file. I like having the 'published' and 'abusive' variables on posts. Should we have a variable in between, something like 'flagged' for those posts that have been flagged by users and need classification by a moderator?

[trex]

@moonquay you raise a good point. There are a few states that a post can have, and all of the ones that I can think of currently relate to a post being abusive:

• Post is created and does not trigger the content filter - publish immediately
• Post is created and triggers the content filter - do not publish
  • Moderator approves triggered post - publish post
  • Moderator does not approve triggered post - do not publish

So I don't think we need the published field, and can update the abusive field to have more than two states, we can achieve this by making abusive an enumerated type.

I will update the code based on this feedback. Thanks @moonquay

[trex]

@moonquay I pushed some changes to add a rich Moderation type to both Thread and Post. This will be flexible enough for the future if we want to track user moderation feedback, such as tracking abuse/spam reports from users and unpublishing if they cross some threshold.

[moonquay]

Hi Trevor, That looks great, I think that pull request should go through! I see the Hawthorn Code of Conduct is on the list of things to do. As I am still a newb with much of the more technical sides of the project, I will research standards of 'Codes of Conduct' to see present and forward-looking standards are. I was engrossed with hosting my friends, but I got further in running it on my machine. After 'npm start', a new window comes up in my Firefox that comes up with the error: ./node_modules/graphql-tag/src/index.js Module not found: Can't resolve 'graphql/language/parser' in '/home/moonkey/dev/hawthorn-client/node_modules/graphql-tag/src' *This error occurred during the build time and cannot be dismissed.* I had updated my files with $ git hub origin master but not sure how I am missing that module. Is that a part of npm? Thank you for guiding me along as I get my feet wet : D Thanks for all you do! See ya later, M

…

On Mon, Dec 16, 2019 at 11:12 PM trex ***@***.***> wrote: @moonquay <https://github.com/moonquay> I pushed some changes to add a rich Moderation type to both Thread and Post. This will be flexible enough for the future if we want to track user moderation feedback, such as tracking abuse/spam reports from users and unpublishing if they cross some threshold. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN6TUSOFPHUNVDQ5KAD4ZE3QZBUU5ANCNFSM4J2IS4PQ> .

[trex]

Monk! I'll merge that change shortly. I am going to add functionality to create groups prior to merging. I will pass the group name and description through the content filter like we do with posts and threads. I spoke with the people who run the Community Care Collective and many LGBTQ+ support groups about how they came to their Code of Conduct. They said it has been revised as a living document over the past 18 years of running support groups. They said we could use their Code of Conduct as a starting point. Do you want to conduct research and we can merge your findings with the Community Care Collective's Code of Conduct? Have you run `npm install`? All of the libraries a JavaScript project depends on are specified in the `package.json` file. Then you install can install them by running the `npm install` command from the command line when you are in the same directory as `package.json`. Note, people use `` (back-tick) style quotes to denote code, I tend to put the names of code files in back-tick quotes too because they are codey. You are welcome. I am happy to help you get your feet wet. Thank you for giving me the opportunity.

…

On Tue, Dec 17, 2019 at 8:58 AM moonquay ***@***.***> wrote: Hi Trevor, That looks great, I think that pull request should go through! I see the Hawthorn Code of Conduct is on the list of things to do. As I am still a newb with much of the more technical sides of the project, I will research standards of 'Codes of Conduct' to see present and forward-looking standards are. I was engrossed with hosting my friends, but I got further in running it on my machine. After 'npm start', a new window comes up in my Firefox that comes up with the error: ./node_modules/graphql-tag/src/index.js Module not found: Can't resolve 'graphql/language/parser' in '/home/moonkey/dev/hawthorn-client/node_modules/graphql-tag/src' *This error occurred during the build time and cannot be dismissed.* I had updated my files with $ git hub origin master but not sure how I am missing that module. Is that a part of npm? Thank you for guiding me along as I get my feet wet : D Thanks for all you do! See ya later, M On Mon, Dec 16, 2019 at 11:12 PM trex ***@***.***> wrote: > @moonquay <https://github.com/moonquay> I pushed some changes to add a > rich Moderation type to both Thread and Post. This will be flexible > enough for the future if we want to track user moderation feedback, such as > tracking abuse/spam reports from users and unpublishing if they cross some > threshold. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #2 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AN6TUSOFPHUNVDQ5KAD4ZE3QZBUU5ANCNFSM4J2IS4PQ > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB24CGMUP66DRET5CWEDQ3DQZDZJHANCNFSM4J2IS4PQ> .

-- *trevor smith* *pronouns: they/them/theirs* http://www.hawth.org/