My only concern with this extension is how much data is being sent into Google for analysis before the text is sent back. Any information sent to an external service for analysis could well be in scope for GDPR if there is identifiable information that is attributable to an individual.
[deleted] Google has a no store flag that will prevent them from storing the data. I will had a toggle for that in the next release.
Edit: Feature has been release, also this extension will NEVER send identifiable information to google. It only sends the contents of a post, never a user email, user id or any other information that would identify an individual user.
This update fixes some minor issues and addresses the concern about Google storing discussion data ([deleted])
This update fixes 500 error caused by 0.1.1 when creating post
tankerkiller125 That’s what it was. Composer cache. Thanks!
I’ll keep trying later but no success so far. And it could be Google’s fault, not this extension.
When I try to post with a F bomb it posts and doesn’t flag it. When I look at my G console it shows 45% errors.
It appears to be kind of working because in this screenshot you will see it is registering requests. Interesting 
.
010101 This is actually my fault for poor engineering/thinking. Currently the extension averages the values of the returned toxicity scores. In actuality it should probably use the max value, I discovered this issue myself when I was testing last night and it's addressed in the next release with a "Use Max Value" toggle. To get it to trigger with the current configuration it requires some pretty vulgar content.
tankerkiller125 Cool. I thought about that... the fact that just one curse word might not trigger it.
010101 If you only had the Profanity filter enabled it would trigger (or should) with just one word. But with multiple it currently doesn't, I'm finalizing the patch tonight after work and should have it released sometime around 7 EST
tankerkiller125 So a post laced with profanity will pass and a post with one word will be caught?
jordanjay29 Perspective has a different ML model for each toggle in this extension, so the toxic toggle returns a unique score, the profanity toggle returns it's own score, etc. Currently those scores are averaged out and then checked against the max value set in the settings. This means that a post with a single swear word won't get caught but a post with some very vulgar attacks/language would. The patch I'm pushing will resolve with with an additional toggle that will tell the code to compare whichever score is the maximum against the max allowed. This will allow a single swear word to get caught as well as vulgar content.
Edit: A full list of models can be found here (I did not include all of them in the extension) https://github.com/conversationai/perspectiveapi/blob/master/api_reference.md#production-and-experimental-models
This update solves the issue with the filters not being applied correctly
Currently, Perspective API has production TOXICITY and SEVERE_TOXICITY models in the following languages:
English (en)
Spanish (es)
French (fr)The following languages are those that are still being developed for production but ready for experimental use:
German (de)
Portuguese (pt)
Italian (it)
Csineneo I agree language support isn't that great, however languages are hard and Google has clearly taken the initiative and invested time and money into perspective and they clearly have a goal of supporting a wide number of languages, currently the extension uses the production toxicity models but I'm doing some research/testing comparing the experimental version to the production one. If their similar enough in English at least, I might switch in order to support more languages.
tankerkiller125 This seems to work well now. Really great extension!
@tankerkiller125 @Kyrne @Ralkage seems this isn't compatible with ReCache - can this be looked at, as it's a great extension.
[deleted] This extension only adds a listener to posting content and adds a little JS for the flags extension so I'm not entirely sure where the problem would be, currently it doesn't make financial sense for me to purchase ReCache however I'd be more than happy to work with @Kyrne and @Ralkage to get this resolved, I'll try reaching out to @Ralkage on discord later today when I get a chance.
tankerkiller125 Thanks. Some things on my install I notice (with or without recache actually)
@tankerkiller125 - A weird small, possibly very rare, bug... If I try to edit a post using a certain custom BBcode, Flarum gives me the oops error and the post will not post. If I deactivate this extension, I can post with my custom BBcode just fine. The custom BBcode looks like this: [preview="a url goes here"].
I'm thinking that the API or the code in this extension itself perhaps thinks something fishy is going on since I'm trying to post this weird BBcode, and it is just not sure how to handle it and so... oops error. Something like that.
010101 Unfortunately I'm unable to replicate the issue in my development environment, could you share the logs from the flarum log folder and any JS console errors that appear?
