Skip NSFW classification if treshold is 0.0 #583
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
turt2live
reviewed
Mar 13, 2025
Member
should be fine without, I think |
Contributor
Author
|
Rebasing after #585 introduced a merge conflict. |
Signed-off-by: Rory& <root@rory.gay>
Signed-off-by: Rory& <root@rory.gay>
7701485 to
b2564d4
Compare
Contributor
Author
|
This should now pass CI in theory - linter is happy. |
Contributor
Author
|
Made a mirror branch to enable the |
H-Shay
reviewed
Mar 19, 2025
Co-authored-by: Shay <hillerys@element.io>
Contributor
Author
|
(Do you want me to squash the typo fix?) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to skip NSFW processing if the sensitivity is set to 0.0.
This saves resources, and makes redactions happen faster, allowing it to be used as a generic "disallow images" protection.
I wonder if a setting to opt out of this behavior should be included, even though one could set the sensitivity to 0.0002 to opt out?