Como muchos de ustedes notaron (o no), de alguna forma algún profesor en algún lado decidió dar de tarea a sus alumnos que publicaran una pregunta sin sentido en el sitio...
Aunque tenemos identificadas varias de las mismas (por ejemplo: Como programar una secuencia en python) algunas otras, pasa...
[ SmokeDetector | MS ] No whitespace in title, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body (168): consideringconsidering by pronewsreviews on meta.SE (@Ollie)
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (4): mobile app development services by Jhonth Smith on meta.SE (@Ollie)
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in link text in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body, +1 more (267): buy instagram followers canada by buzzsocial on worldbuilding.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +4 more (494): Viking-XL-Keto-BHB by HealthX on meta.SE (@Ollie)
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@SmokeDetector tpu- 3rd instance of undisclosed affiliation. User was previously warned (I think). Profile name has recently been changed, and so affiliation is no longer obvious. Custom flagged.
@Rob I already get these VMware advisories. VMware port 443 is only accessible from one section of my network - where my computer sits. No other systems other than the VMware infra itself (which can't be reached directly via the systems on them as VMs) are exposed to that port, so there is no actual risk of attack in this case. I intentionally separate my network hardcore for this purpose ;)
(vmkernel and management ports don't even touch the same net VLANs as the actual stuff, and everything's isolated anyways to have to pass through the pfSense before it can even get out to the VMware management net)
no need to share the VMware advisories with me as I already get them ;)
@RyanM Given that you're wanting this to start at the beginning of the tested text, it would be much better to just start the pattern with the ^<p>, rather than use a lookbehind after finding a p>.
@Makyen I had assumed that wouldn't be a word boundary, but I guess the start of the string is always a word boundary regardless of whether or not it's followed by a word character? I guess I can remove the end lookahead too, then, and simplify the whole thing to ^<p>[\W_]*+(?:(?:lol(?:ol)*+|lmao|rofl)[\W_]*){3,}[\W_]*</p>$
@RyanM You are correct in your belief that the start and end of the string, in the regex version we use, is not, necessarily, considered to be a word boundary. In order to accommodate that, and account for testing for the beginning and end of the string, the watched and blacklisted keywords use more complex bookending, which is (?is)(?:^|\b|(?w:\b))(?:{})(?:\b|(?w:\b)|$). Please see PR #2322 for a bit more detail.
