> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - audifab.com NS suspicious dns30.hichina.com.,dns29.hichina.com. Potentially bad ns for domain in title - audifab.com NS suspicious dns30.hichina.com.,dns29.hichina.com.
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if there are any operational notifications from Thomas Ward, which are usually pinned in the sidebar. If Cerberus is operational (i.e. use the !!/location command to see if it responds), then consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. @Makyen
@Cow That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow User blacklisted (276079 on ell.stackexchange.com).
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, potentially bad ip for hostname in body, potentially bad keyword in body, +1 more (269): Best Interior Designer In Noida by Studio Ezube on meta.SE
@VLAZ A normalized version, {{'09163469092'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number 09163-4690-92 to determine which entries on the number lists match that pattern, which would tell you: Matched by 0916-346-9092 on line 2197 of blacklisted_numbers.txt: 09163469092 found normalized
I have a userscript but doesn't quite fix it. It forces the per-page parameter which mostly works. But then the SE code still seems to omit the last page. I have to re-write the whole pagination logic...which I'm a bit too lazy to do.
