|
Joined: Oct 2006
Posts: 49
journeyman
|
journeyman
Joined: Oct 2006
Posts: 49 |
I'm struggling trying to filter any badword that starts with "$" such at $hit. Anyone know how to filter this exact match?
Thanks,
Wayne
|
|
|
|
Joined: Jun 2006
Posts: 16,299 Likes: 116
|
Joined: Jun 2006
Posts: 16,299 Likes: 116 |
Without getting into the technical aspects, simply do:
|
|
|
|
Joined: Apr 2007
Posts: 3,940 Likes: 1
Former Developer
|
Former Developer
Joined: Apr 2007
Posts: 3,940 Likes: 1 |
which won't work. the censor code kinda cripples the regex in a sense by only NOT escaping (.+?) .. i've not understood why we do that, but it might be for: simplicity / safety..
|
|
|
|
Joined: Jun 2006
Posts: 16,299 Likes: 116
|
Joined: Jun 2006
Posts: 16,299 Likes: 116 |
yeh, simplicity sure, but we can't check stupid stuff like people trying to be l33t by doing $hit or: S H I T We should allow true regex, then we could actually have some fun with it ...
|
|
|
|
Joined: Apr 2007
Posts: 3,940 Likes: 1
Former Developer
|
Former Developer
Joined: Apr 2007
Posts: 3,940 Likes: 1 |
well, from a coding standpoint, the change is to actually do LESS code... so the key would be to find out the philosophy as to why not 1st i'm not sure where the history of the censor stands..
|
|
|
|
Joined: Jun 2006
Posts: 16,299 Likes: 116
|
Joined: Jun 2006
Posts: 16,299 Likes: 116 |
I'm sure it's to protect users (rather admin's) from themselves, but you'd think we could laxe it in this case (rather area) so that we can better make full use of the censor's potential.
|
|
|
|
Joined: Oct 2006
Posts: 49
journeyman
|
journeyman
Joined: Oct 2006
Posts: 49 |
Without getting into the technical aspects, simply do: This doesn't work
|
|
|
|
Joined: Dec 2006
Posts: 1,235
veteran
|
veteran
Joined: Dec 2006
Posts: 1,235 |
You could add (.*?)hit to the sensor. Not ideal but it's an alternative for now.
|
|
|
Bots
by Outdoorking - 04/13/2024 5:08 PM
|
|
|
|
|
|
2 members (Napalm, 1 invisible),
867
guests, and
189
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|