@ArtOfCode Quick Q for you. This answer appeared, and I originally marked it as tpu, as it appeared to be from an unregistered/garbage user. My R&A flag was marked as helpful from the mods, but there was some disagreement to naa there. I believe this should have been marked as tpu for SmokeDetector's filters.
It's weird that the letters on my keyboard are uppercase but I actually have to press a different button to get them to appear uppercase on the screen. I've never really thought about that before. Maybe I've got too much time on my hands today...
@EriktheOutgolfer Although, apparently a lot of motorway signs are written in lowercase because apparently lowercase letters easier to read at a glance.
@Henders well, we usually learn the uppercase alphabet seconds before or at the same time as the lowercase one, and an uppercase letter is obviously more representative of itself ;-)
> The decision was taken to use lower-case words with initial capitals instead of the all-capital practice that was most common up to that time. The idea was that this created more distinct word spaces, which could therefore be read more quickly and from a greater distance.
@EriktheOutgolfer 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.
It looks like GitHub is working now, but the deploy and master branches are on different commits. It doesn't look like MS is going to automatically fix that. So, someone with write access to the SD GitHub repo will need to set the deploy branch to the same commit as master. It also looks like Circle CI and travis aren't working on the repo at the moment.
OTOH, it looks like GitHub is not quite up. Status as of an hour ago: "Background jobs remain paused as we near completion of validation of data consistency."
I had gotten the feeling that was the case. There's also the incident report, but it has just slightly more information (i.e. specifically that webhooks are affected).
@ArtOfCode Sorry to put you through the process of fixing the repo when GitHub wasn't actually up. Hopefully it will be up before someone changes the watch/blacklists, so you don't have to do it twice.
@EriktheOutgolfer That pattern looks like it's already caught by Potentially bad asn for hostname in answer and Potentially bad asn for hostname in body; append -force if you really want to do that.
[2018-10-18 17:17:50] WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. [2018-10-18 17:18:20] WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. [2018-10-18 17:18:50] WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. [2018-10-18 17:19:20] WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets.
Changing the emojis is just a record in the db, and removing usernames and the other UI fun with html comments is pretty easy as well, so if you want to fork my repo, I can run on that fork.
@TetsuyaYamamoto 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.
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@TetsuyaYamamoto 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.
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 6-20: supplement.com Body - Position 6-20: supplement.com
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 0-24: supplementcyclopedia.com Body - Position 0-24: supplementcyclopedia.com
@ArtOfCode Although this is super subjective -- I really don't see SE implementing anything like it. CE5000 also wasn't meant to make any concrete changes, just to figure out how large the problem is.
Aye, but the thought was that if we can get data, we can give it to regex wizards - we know SE can exclude based on regexes already, so if we can come up with a regex, that's basically a ready-made patch
