-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EN] Use the 4MB client-side model for NSFW.js
#15
Comments
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
Feature request / Suggestion
We should do content-safety checks on the client-side too. This would instantly provide feedback to the contributor, instead of manual flags and mailed reports. Note that, we'll continue to do server-side checks.
Current behaviour
Currently, we do content safety checks only on the server-side.
Other details
See: https://github.com/infinitered/nsfwjs
Self-check
The text was updated successfully, but these errors were encountered: