You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently defining spam keywords are incredibly basic, and the most common issue is that they partially match. So if you wanted to catch the word ass and a user provides assistance, brass, grasshopper (and of course many more) are going to match due to the word being at the start, middle or end of a string.
Now we could provide settings to match whole words or not, but a more rich syntax would be ideal to define rules per-line in text. For example, you might want to make some rules like:
Exclude the word ass as a whole word
Exclude the word hamper anywhere in the text
Exclude words starting with, or ending with certain text
I'll see what options are out there as well, to build off ideas from others! It may very well be the case that we're over-complicating things and just need a whole-word or occurrence matching setting for keywords.
The text was updated successfully, but these errors were encountered:
Currently defining spam keywords are incredibly basic, and the most common issue is that they partially match. So if you wanted to catch the word
ass
and a user providesassistance
,brass
,grasshopper
(and of course many more) are going to match due to the word being at the start, middle or end of a string.Now we could provide settings to match whole words or not, but a more rich syntax would be ideal to define rules per-line in text. For example, you might want to make some rules like:
ass
as a whole wordhamper
anywhere in the textI'll see what options are out there as well, to build off ideas from others! It may very well be the case that we're over-complicating things and just need a whole-word or occurrence matching setting for keywords.
The text was updated successfully, but these errors were encountered: