Skip to content

Conversation

@skbeh
Copy link
Contributor

@skbeh skbeh commented Aug 19, 2024

This prevents spammers from using visual identical unicode characters to bypass detection.

This prevents spammers from using visual identical unicode characters
to bypass detection.
@4drian3d
Copy link
Owner

The only thing that worries me is the possible overhead of using the Normalizer class in all chat and command executions, in your other pull request everything is perfect since it is behind a configuration option, but here, even though you drop the use of equalsIgnoreCase for an equals, I don't know how much pressure it can take to use the Normalizer

@4drian3d 4drian3d added the enhancement New feature or request label Aug 19, 2024
@skbeh
Copy link
Contributor Author

skbeh commented Aug 20, 2024

According to https://unicode-org.github.io/icu-perf/results/ustrperf/TestNames_Latin/, normalizing a character would take no longer than tens of nanoseconds. As a message can have a maximum of 256 characters, it would not have much impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants