Perspective API

tankerkiller125

I've discovered a bug related to approving post after they've been marked as toxic by perspective. It does not affect normal approvals. I'm currently working on figuring out how to fix it and I'll release a patch as soon as I have it fixed.

010101

tankerkiller125 ❤️ - But, I can’t install it. Composer says my forum doesn’t meet the minimum version requirements. But, I have beta 10.

datitisev

010101 Looks like the extension also requires any version of flarum/approvals (^0.1.0) and version ^0.1.0-beta.9 of flarum/flags.

tankerkiller125

010101 Can you post the console log?

010101

tankerkiller125 It doesn’t even attempt to install it. Composer immediately says:

No errors were logged. I don’t know if this is it but, some other extensions’ composer.json files don’t include the minimum stability beta line.

datitisev I have these with the correct versions activated.

if it’s just me that’s cool. Could just be something with my installation.

tankerkiller125

010101 if you try composer install tank/perspective 0.1.0 does that work?

datitisev

010101 See why you can't install it with composer why-not tank/perspectivee

EDIT: This might only work for packages that are already installed and cannot be updated due to requirements.

UntrustableRus

I hope to install this in a few hours. Hopefully the above problems are fixed so i can make sure it works.

UntrustableRus

Could you include some more instructions on how to do the google api part

tankerkiller125

UntrustableRus You'll want to go to https://console.developers.google.com/apis/ and then from there you'll need to go to the API library and search for Perspective. Once you've found it you'll need to enable the API and then under credentials you'll need to create an API key. Copy and past the API key into the settings modal and select the options you want and set your threshold.

tankerkiller125

datitisev I have a feeling it's the composer cache, I've discovered that composer won't always detect that a released version of a packages is available. So composer may be thinking that the package is still in a dev-master state because of the cache.

datitisev

tankerkiller125 Oh yeah, I've had that happen before as well.

010101

tankerkiller125 That’s what it was. Composer cache. Thanks!

[deleted]

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.

tankerkiller125

[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.

tankerkiller125

Update 0.1.1

This update fixes some minor issues and addresses the concern about Google storing discussion data ([deleted])

Changelog

Fixed approval issue (only on content marked by perspective)
Added a Do Not Store option. This will inform Google not to store submitted post

tankerkiller125

Update 0.1.2

This update fixes 500 error caused by 0.1.1 when creating post

Changelog

Fixed Perspective API causing 500 error due to bad JSON data

010101

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 🧐.

tankerkiller125

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.

010101

tankerkiller125 Cool. I thought about that... the fact that just one curse word might not trigger it.

tankerkiller125

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