@SurajRao out of curiosity, not that there's anything wrong with what you're doing, but you have privileges to run the allspam command. Is there a reason you don't? Again, this is not a complaint, I'm just curious.
@RyanM I had become a bit trigger happy with that command before.. So I tend to avoid the particular command. Maybe became overly cautious in this case.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-3: kys, Position 4-10: soyboy Potentially bad keyword in title - Position 0-3: kys, Position 4-10: soyboy Potentially bad keyword in username - Position 0-3: kys, Position 4-10: soyboy
@Mast Matched by ^.{1,15}?cream(?<!icecream)(?<!ice[\W_]cream)(?<!^bluescream)(?<!^bluscream)(?<!\bscream)(?<!^colorscream)(?<!\bhellscream)(?<!^wolfscream)(?<!^eyescream)(?<!^starscream)(?<!^olscream)(?<!^dreamcream)(?<!^stealthscream)(?<!^krispycream)(?<!^cameocream)(?<!^coffeewithcream)(?<!^soft cream)(?<!^handcream)(?<!^doughnut facecream)(?<!^don cream)(?<!^doncream)(?<!^Mayocream)(?<!^willcream)(?<!^bfdicream)(?<!^coder_scream)(?<!^confused_scream)(?<!^ice7cream)(?<!^iscream)(?<!^isecream)(?<!^mikacream)(?<!^paul cream)(?<!^sadscream)(?<!^spinescream)(?<!^sscream)(?<!^testscream)(?<!^whipcream)(?<!^whyscream)(?<!^SourCream)(?<!^Veep Cream)(?<!^crispyCream)(?<!^likescream)(?<!^peachesncream)(?<!^zack_cream)$(?#add additional exclusions as more legit users are detected) on line 4387 of watched_keywords.txt
But yeah in terms of "way too many FP" we've got model.fit and friends, the kill regexes (specifically, the inclusion of the word "kill"), and the buy-near-link regex. The first two catch almost nothing of value that's not otherwise caught. The buy-near-link regex is a problem because it does, but I wonder if we could tighten it (example: the link must not be to i.stack.imgur).
There are also domains that just are never spam that we keep detecting, some of which show up in that first link. I'm not sure why doc.qt.io isn't showing up in that, but it's also never spam.
Mysql2::Error: Unknown column 'posts.title' in 'field list': SELECT posts.title, posts.body, posts.user_link, posts.username FROM feedbacks WHERE feedbacks.is_invalidated = FALSE AND feedbacks.post_id = 276115 ORDER BY feedbacks.id DESC LIMIT 10 OFFSET 0
@user12986714 (cc @ArtOfCode) Your filter is bad. You are making a request to the /api/v2.0/feedbacks/post/:id endpoint. The available table for that endpoint is the feedbacks table. Your filter is requesting information from the posts table, which is unavailable. The endpoint returning an error is correct.
Your filter can only request data from the table(s) which are available to that endpoint. Any filter which requests data outside of the available table(s) will return an error (or at least should return an error).
