[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, pattern-matching product name in body (488): Testo Ultra this complement by user893328 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +3 more (788): www.supplementdiets.com/retro-vigor/ by niza roay on askubuntu.com
[ SmokeDetector | MS ] Url-only title, pattern-matching product name in body, potentially bad ns for domain in body, potentially bad ns for domain in title (200): sharktankpedia.com/ by Truld on askubuntu.com
amzn.to is whitelisted because many legitimate Amazon links are rewritten to use Stack Overflow's official amzn.to redirector (I believe there is a commission to SO for click-throughs)
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +5 more (788): dietproducts4u.com/365-keto-life/ by SherBorja on apple.SE
"I think if you ask this question from the university itself, it's better to have a quick and clear answer to you. Everyone here tells you his experience and his personal perspective, and maybe you become more confused." -- Google Translate
[ SmokeDetector | MS ] Url-only title, body starts with title and ends in url, link at end of body, potentially bad ns for domain in body, potentially bad ns for domain in title, +1 more (397): sharktankpedia.com/ by Peselaai on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, pattern-matching product name in body, +2 more (587): KetoFit Ca Reviews by aldpakad on apple.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, blacklisted website in body, body starts with title and ends in url, +3 more (681): Lutragen cream australia by alphaxfactor on meta.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, pattern-matching website in body, +3 more (594): Top Choices Of man power by florapharris on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, +2 more (493): You have to make sure you follow the by user963996 on superuser.com
right, but again, clearing it out to produce a consensus on posts which clearly did not have a consensus is counter-productive at least for some of our routines
having both TP and FP is clearly problematic, especially if you have an equal amount of both, but discarding one or the other is just sweeping the problem under the rug
I know I have some old scripts which just work incorrectly with conflicting feedback because I wasn't actively aware of these conflicts when I wrote them, but that's obviously a flaw with the scripts, not with the data
> Blacklisted website in answer, potentially problematic ns configuration in answer ---------- Body - Position 0-20: triangulartrades.com Body - Suspicious nameservers: all IP addresses for triangulartrades.com are in set {'50.7.112.85'}
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +6 more (887): evaherbalist.com/arora-shine/ by tumazari on wordpress.SE
@CalvT Your example there is R/A for what I care about
Don't really care how you flag it on site, but feedback here should probably be tp
The debates on that issue are super bizarre. It boils down to one side saying "this flag does exactly the right thing in this case" and the other side saying "yes but the name of the flag is wrong"
And the name of the flag isn't even wrong.
So my guidance is simple: Flag as you see fit, don't try to change mod's minds on that issue if they bring it up (you probably can't if I haven't yet)