Autoflagging and some other MS actions don't work right now. This will be the case for an unknown period of time, but probably less than 24 hours. More information: short version; long version
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching website in body, +3 more (587): healthjudges.com/beta-keto/ by gloriahatch on graphicdesign.SE
@SmokeDetector @Makyen I can't find the purpose of this ^ watch; it is like we are watching keto, so I am going to propose an unwatch and if we are fine, then we can just watch is without regex (i.e. keto)
@double-beep I am aware of 37 code admins. Currently in this room: Glorfindel, Makyen, Magisch, Mithrandir, John Dvorak, thesecretmaster, Suraj Rao, Ferrybig. Not currently in this room: iBug, doppelgreener, WELZ, CalvT, A J, quartata, NobodyNada, Thomas Ward, angussidney, K.Dᴀᴠɪs, tripleee, Zoe, Ashish Ahuja, ArtOfCode, Shree, Erik the Outgolfer, micsthepick, Byte Commander, ProgramFOX, paper1111, Henders, DavidPostill, Tetsuya Yamamoto, Andy, bertieb, bwDraco, Undo, Nisse Engström, Paul Stenne.
I had all the SD instances in standby pull the then-current version of the SD repo. This was done because a period of MS down time made it clear that they had not all gotten past the update that moved Socket Science to chat.SO. They will all now use chat.SO for Socket Science, but until their forced restarts get out of sync again, they will all restart in standby mode at about the same time, every six hours.
[ SmokeDetector | MS ] Email in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (206): Where from Buy App Instralls by roni alax on gamedev.SE
@double-beep 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.
@SmokeDetector This was reported because the OP had "bumped" their question, so when the OP just added some additional information in an NAA, the question was also detected as a blacklisted user.
@double-beep You sure they are gone? When I tried to go to the first one, my AV software blocked it as a phishing site.
Same with the second.
@double-beep Yes, I can, but I'd rather that you/we contact the person who reported the sites, @Mithrandir, to get an update from them, prior to me unilaterally closing the report.
Yeah, sorry. I'd assumed that because I'd flagged it as spam and it was only at -1 that nobody else had. However, it turns out that my spam flag from when it was initially reported on 2019-03-31 had aged away and I can't re-flag.
@Makyen Matched by https?://[^<>"'\s]+(?!<=[?/][A-Za-z][A-Za-z])-(uk|ca|fr|es|za|de|au|it|dk|br|nz|be|se|us|ch|nl|at|id|no|ie|sg|pt|hr|pl|mx|lt|lu|fi|kr)/(?=[<>"'\s]|$) on line 8942 of watched_keywords.txt
@Glorfindel Is Broken Image Repairer something that depends on MS and a call that MS might make to the SE API?
@Glorfindel I must admit I haven't tried the mobile view of MS. I almost always request the desktop version of sites when viewing them on mobile. Did it work previously?
@Glorfindel Hmm... OK. The script might not be obeying a backoff, but if it was the same issue (i.e. didn't obey backoff for enough times), then your IP address would have been blocked from the SE API for some significant period of time. That would make all userscripts which try to use the SE API fail.
I don't know whether your bot was already active on it, but this question isn't spam-killed after 7h, so I hope it's appropriate to try to generate some attention to it here: outdoors.stackexchange.com/questions/21930/…
If you are wondering why it takes so long: It's the weekend, TGO users are in the outdoors (or working :D) searchingForPretexts
We need to unwatch sites\.google\.com/site/ketotonedietblog and sites\.google\.com/site/rapidresultsketo as the websites are deleted (if any code admin is around...)
@SmokeDetector This is the second answer about that site that's been posted to that question. The first was in early February. It appears that it's by the same person as the earlier one, but with a different username, based on similarities in the usernames.
I'm not 100% clear on the delineation between SmokeDetector and MetaSmoke - is it that SmokeDetector picks up (detects) the bad posts, then MetaSmoke is simply a venue to look in more detail at what SmokeDetector has reported?
@Glorfindel Yeah, I'm not sure what's going on with SE. It appears they've tightened things up wrt. the SE API. I'm now blocked with a message similar to what MS is seeing. For accesses that use an SE API token, I'm seeing CORS errors. (cc @Undo)
