@Shree 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.
@tripleee 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.
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body, potentially bad keyword in title (98): Global SEO, Local SEO by Radu on stackoverflow.com
@Machavity 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.
@curious The fp will also have SmokeDetector reply in chat confirming the feedback, the other two won't get a reply, but will apply the feedback. Other than that, they are all the same.
@robsiemb np. BTW: The process is a bit easier for us if you create an account on metasmoke, but it's not required. In addition, having an account on MS does allow for the possibility of using the userscripts for feedback and flagging.
@curious np. If you'd like, the feedback commands are listed here. The f is an alias for fp-. The aliases are listed in the section of that page just below the section I linked.
@robsiemb ╳ You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
You may also want to look at the userscripts we have available (GitHub), as they can be quite helpful, depending on how you want to participate. For viewing, feedback & flagging in chat, I find FIRE and AIM to be the ones I use the most.
For flagging through the userscripts, your metasmoke account needs to be write authenticated with SE, which, if you haven't already done so, can be done from the authentication page and doesn't require you to also sign up for autoflagging, although doing so is also a required step for signing up for autoflagging.
In addition, to enable manual flagging, the checkbox that says "Use my account to cast flags automatically" on this page also needs to be checked. If you have no entries in the "ID Site Count Flags Used Today" list at the bottom of that page, then autoflagging will still not be enabled, but manual flagging through the userscripts will be enabled.
Just so you know, we normally tell people when they are getting privileges that we practice the "ton of bricks" discipline method here: If you mess-up sufficiently, or consistently, we come down like a ton of bricks :-).
To quote ArtOfCode: "TL;DR: ton-of-bricks is mostly to say that we almost never need to enforce things because things enforce themselves through having a good community here. If it gets to the point that someone's enforcing something, something's gone badly wrong."
@robsiemb Yes, that was the issue (confirmed in message history). I wasn't aware/remembering that Chat would clean that up, but I'm not too surprised, as it probably just sends it as HTML, which would clean up the whitespace.
@robsiemb That clean-up a few seconds later is relatively common. My expectation is that Chat formats the message using JavaScript and inserts it in the DOM to make it visible. Then, when the message is received from the SE Chat backend that a message was added (i.e. just the normal "new message" notification), the content is replaced with what's been rendered into HTML by SE Chat's backend.
@tripleee At the point where EC2-Linux dropped out and Makyen/Windows got the failover signal, that EC2 instance on which EC2-Linux was running (and nothing else was running) had just started to experience a total of 15 minutes at 100% CPU. That 15 minutes of 100% CPU triggered an alarm I'd set which auto-rebooted the AWS EC2 instance. I don't have records of what happened beyond what might be in the !!/errorlogs, which I haven't checked, yet.
There's something, that we've seen a few times before, which causes SD instances to lock-up the CPU for extended periods of time (i.e. until rebooted). The problem appears to be caused by something common to the SD instances at the time (e.g. data received by the instance, SE chat issues, etc.), because the issue will affect SD instances one after the other as they are failed over to and become active. Killing and restarting the SD instance, or rebooting the machine,
results in the instance being alive again, but it may very shortly thereafter lock-up again, if whatever is causing the issue persists. Eventually (a few/several/many minutes), whatever is causing it goes away and SD instances which come active after that are fine.
As to my Windows instance: Shortly after my Windows instance became active, it appeared to have issues with DNS lookups. There are several "DNS error The DNS response does not contain an answer to the question:" notations in the log for domains such as drive.google.com, www.youtube.com, api.github.com, raw.githubusercontent.com, etc.
As to what happened around the time when my Windows instance disappeared, the debug log provides some information, but not a lot:
[xx:05:25.349] DNS error The DNS response does not contain an answer to the question: raw.githubusercontent.com. IN NS (duration: 0:00:00.038975)
[xx:05:25.349] dns_query: returning cached a value for raw.githubusercontent.com
[xx:05:25.350] ASN: IP 151.101.196.133 for hostname raw.githubusercontent.com
[xx:05:25.494] txt query duration: 0:00:00.142927
[xx:05:25.592] 151.101.196.133: Raw ASN lookup result: "54113 | 151.101.196.0/22 | US | arin | 2016-02-01"
[xx:07:22.245] Command received: !!/alive
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body (295): utation bionatrol cbd Real Esta by elsjmyyb on askubuntu.com
On these pages there no "Report" button or other flagging UI.
https://stackoverflow.com/cv/jumanji-the-next-level-movies-free-stream
