[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (296): It will fill in as the best thing by fdgsdfh on graphicdesign.SE
@bertieb or they have an incentive structure where it doesn't matter whether the content stays up, or the boiler-room crew is not trained to measure whether their work actually achieves their goals
@Makyen @tripleee @double-beep I forgot to include the additional portions that reflect how the blacklist and watchlists are constructed. So, (?:\b|^)(?s:(?:^(?s).{0,200})\bbrain\W?power)(?:\b|$) more accurately reflects what the blacklist results have been.
@tripleee (bringing this discussion over from SOCVR, sorry for the long delay)
the pertinent question I think is whether the lookahead is contributing something meaningful
I'm guessing it's just legacy from before we had good conventions for these things
many of the really old rules to have a length constraint vaguely similar to this
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, +2 more (395): This tool is a herbal opti farms keto by Dognis196 on askubuntu.com
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@double-beep definitely looks promotional to me, do you think otherwise? no relation to the question (other than having the same broad topic i.e. Minecraft - which is typical for spammers)
@double-beep yeah, though even less sophisticated ... already back in the 90s spammers would look for people whose email address was used in a forum where e.g. dogs were being discussed and leap to the very tenuous conclusion that sending adverts for dog food to these would be okay
a lot of the blogspam is even less targeted, but harder to link to malicious intent until you have seen enough of the same tactic
Aside being registered a month ago, the common name is footballsupport.geniussport.com rather than *.stackexchange.com as with the rest of the certificates for the network (SO inclusive)
Either here or on any site's meta search for questions tagged faq or faq-proposed. Stack Overflow's can be found here and here.
These will give you most of the information you need.
As you've already discovered there is also the Tour and Help pages for each site linked to from the menu bar at t...
@Makyen The point was that a mod used it, but with the certificate being suspicious, I wasn't sure whether it was real or not. Validated by a CM though.
@Olivia Yeah, the domain threw me too. The first time I saw it was associated with the Teams' help pages. It's the direct link in the help drop-down on Teams pages.
Potentially bad keyword in answer - Position 0-12: <p><a href=" Username similar to website in answer - Username `PokerOCR` similar to *pokerocr* at position 23-31, ratio=1.0
[ SmokeDetector | MS ] Url in title, body starts with title and ends in url, link at end of body, pattern-matching website in body, pattern-matching website in title, +5 more (594): www.healthsuperclub.com/ripoplex/ by leonasalder on drupal.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, pattern-matching website in body, potentially bad keyword in body (165): Send message on email by dorinex98 on stackoverflow.com
@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@Makyen 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.