Add legal indicators whitelist to gibberish detection#4679
Open
VaaishnaviS wants to merge 1 commit intoaboutcode-org:developfrom
Open
Add legal indicators whitelist to gibberish detection#4679VaaishnaviS wants to merge 1 commit intoaboutcode-org:developfrom
VaaishnaviS wants to merge 1 commit intoaboutcode-org:developfrom
Conversation
Signed-off-by: Vaishnavi S <vaishnavibabblu1@gmail.com>
VaaishnaviS
force-pushed
the
enhance-gibberish-detection-indicators
branch
from
64a53cc to
2ebca1f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #4676
Tasks
Run tests locally to check for errors.
I have implemented a whitelist-based "Safe Gate" for gibberish detection.
The Problem: The normalize() function was stripping non-alphanumeric characters like ©, (c), and @. This caused the Markov chain model to see only fragments of legal strings, leading to high "gibberish" scores.
The Fix: Added a COPYRIGHT_INDICATORS list that is checked before normalization occurs. If a match is found, the string is immediately flagged as "not gibberish," bypassing the math model entirely. This is more robust and faster for legal text.
Signed-off-by: VaaishnaviS vaishnavibabblu1@gmail.com