@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.
@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.
@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.
@Makyen 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.
room topic changed to Charcoal HQ: Where diamonds are made, smoke is detected, and we break things by developing on production. 125k true positives and counting. For more information, see charcoal-se.org/about. Handy links: metasmoke.erwaysoftware.com, github.com/Charcoal-SE [dev-on-prod] [panic-driven-development] [plastic-knives] [programmatic-crowbars]
@Undo Yeah, it's my IP. The main token I was using was one I primarily use for (generally long-term) testing. The API keys were my testing one, and a variety from various different scripts. While the point in time that I think this actually triggered the lock-out would have been a bit higher usage from me, but not more than I've had on other occasions. There were no significant recent changes to the code on my machine wrt. fetching data from the SE API.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (497): Con as it suppresses thirst it could motive by user102470 on workplace.SE
@Undo We're at about 27 hours from when we know this was a problem on MS. That's not a good sign that this will reset/clear in the near future by itself. It may be time to contact SE to see what needs to happen to clear this up. The error message from SE says to contact them at team@stackoverflow.com "if you believe you have reached this page in error".
yeah. I really don't have time to deal with big DNS changes.
@Nick_Craver If you get a sec, can you un-block 54.236.78.156 from whatever HAProxy hell it got into? We found & fixed a backoff-respect issue 24ish hours ago, and it just isn't unblocking. Suspect it's because we're still trying to send the usual volume of reqs despite block.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title, +2 more (397): Keto Green Therefore, there are some factors by Keto Green on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword with email in body, email in body, pattern-matching email in body, potentially bad keyword in body (177): willianloanfirm6 by DE Fed on money.SE
[ SmokeDetector | MS ] Url in title, body starts with title and ends in url, link following arrow in body, potentially bad ns for domain in body, potentially bad ns for domain in title, +3 more (396): www.factsofhealth.info/opti-farms-keto/ by suvumuj on wordpress.SE
@Blue 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 for future reference, any admin can also delete comments if needed, so feel free to let one of us know if we're around and you think a comment was put there by mistake or something
@Nick_Craver If you get a sec, can you un-block 54.236.78.156 from whatever HAProxy hell it got into? We found & fixed a backoff-respect issue 24ish hours ago, and it just isn't unblocking. Suspect it's because we're still trying to send the usual volume of reqs despite block.
@SmokeDetector While this does resemble spam posted on a spam-seed question, the user is engaged in chat and appears more like a user that doesn't understand what's normal on the Stack Exchange Network, rather than someone who is intentionally spamming. So, while this may appropriately be marked as TP, it may, or may not, be something that people will want to flag as spam.