Open MattGraz opened 7 years ago
similarly related would be a NSFW filter. I am particularly worried given the current "surface a random image from the DB" model of our expert labeling feature. I know I have seen at least one offensive image using it 👎
we should probably just start with a free tier on one of the many NSFW filter API's and then deal with better solution later
On Wed, Apr 26, 2017 at 9:09 PM, Matthew A Sochor notifications@github.com wrote:
similarly related would be a NSFW filter. I am particularly worried given the current "surface a random image from the DB" model of our expert labeling feature. I know I have seen at least one offensive image using it 👎
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/matthew-sochor/fish.io.ai/issues/57#issuecomment-297583402, or mute the thread https://github.com/notifications/unsubscribe-auth/AOeuWsUqdPg6DnIaaEOM2C5IeFUtHDqEks5rz-rbgaJpZM4M-rTL .
AWS has one, google, Clarify, indico, ect
On Wed, Apr 26, 2017 at 9:12 PM, Josiah Olson thenomemac@gmail.com wrote:
we should probably just start with a free tier on one of the many NSFW filter API's and then deal with better solution later
On Wed, Apr 26, 2017 at 9:09 PM, Matthew A Sochor < notifications@github.com> wrote:
similarly related would be a NSFW filter. I am particularly worried given the current "surface a random image from the DB" model of our expert labeling feature. I know I have seen at least one offensive image using it 👎
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/matthew-sochor/fish.io.ai/issues/57#issuecomment-297583402, or mute the thread https://github.com/notifications/unsubscribe-auth/AOeuWsUqdPg6DnIaaEOM2C5IeFUtHDqEks5rz-rbgaJpZM4M-rTL .
We want to make sure we are not adding noise to our data collection process. In present state, I can download an image from the internet and upload it to our site.
Although we do want to provide this type of functionality, we need to distinguish this type of use case from someone out on a lake fishing so we don't have a ton of "catches' that were uploaded from an office building/house being stored in our database.