With this plugin, you can detect and filter explicit, suggestive, adult, medical, NSFW or violent content within a JPEG, PNG8, PNG24, GIF, Animated GIF (first frame only), BMP, WEBP, RAW, ICO, PDF, TIFF image file that is provided as input.
You can use this plugin in a variety of use cases such as social media, online market places, and professional media. By using Google Vision to detect unsafe content, you can reduce the need for human review of unsafe content.
The plugin returns an explicit likeliness value for the Adult, Spoof, Medical, Violence and Racy content categories.
Hello, thanks to provide this plugin… looks exactly like what I need for my app… So my users have a profile page where they can upload their profile photo and their cover photo. Instead, to check the photo when the user uploads the photo I’m thinking to create a check/moderation page (where only I have access) where your plugin checks all my users uploaded photos and detect the ones with explicit content so I will be able to delete the profile of the user that has uploaded an explicit content photo… do you think I can do it? If so, any suggestion on how to do it?
Great to hear!
This plugin takes as input a JPEG, PNG8, PNG24, GIF, Animated GIF (first frame only), BMP, WEBP, RAW, ICO, PDF, TIFF image file from the Bubble.io picture uploader, or a Protocol-relative URLs (//server/image.jpg), or a HTTPS image URL (https://server/image.jpg).
So if your images URL meet this criteria, you can definitely use this plugin to build the logic you wish, such as going through all your existing profiles pictures to analyse them, tag them in your app database and build the internal page allowing you to validate each record.
If you need further assistance, feel free to DM us, so we can support you to implement your use-case
I copied the private key directly from the JSON file (CTRL+C) and pasted it (CTRL+V) in the private key plugin setting and am still getting the same error. I`m sorry- I dont know what i am doing wrong.
I haven’t heard from you @rogovtechnology following our discussion via DM. I assume the issue has been solved then and was due to a copy/paste error or wrong key.