[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, blacklisted website in body, link at end of body, +2 more: Tyvexan male enhancement by Tryvexan on meta.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +1 more: Hermusa Natural Beauty by valeryford on meta.SE
As our devs continue to work on features like Talent and Channels (now called Teams), I've been anxiously looking for ways to increase engagement in our current Stack Exchange sites to help assure that development RETURNS to our Q&As… as soon as possible.
As the biz-dev folks spread the word abo...
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, +1 more: healthcareorder.com/max-peak-xl/ by yahnsudk on apple.SE
They all look like this. It's customary to submit a link to a "try online" link which is not uncommon to be on the person's own github - they often times use obscure selfmade languages to facilitate golfing
As mentioned, it's inappropriate to disable .github.io for SO wrt. "username similar to website *". Undisclosed promotion of your own GitHub project is certainly something that's not acceptable on SO.
@Magisch from the entire autoflagging discussion, I had the impression that for reports, the goal was no false negatives, and for autoflags no false positives. These are not autoflagged, so that's fine. And without the rule at all, one wouldn't have been caught. So there is at least some value in the rule.
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +1 more: growxlsite.com/ultra-t-booster/ by Ajjanahaiz on puzzling.SE (@Mithrandir @micsthepick)
@ByteCommander @Glorfindel @Mithrandir Due to an issue introduced into the MS API in the latest deployment, AIM will have some issues under some conditions. The expectation is that the MS API will be fixed.
Yes and no. The issue is that it is not able to obtain correct flagging information from the MS API. That will cause it to do various incorrect things, under some conditions. I have not bothered to take a close look at all the effects, as it's something that is expected to be fixed in the MS API, soon.
Background and History
The New Answers to Old Questions tool helps us to find all the answers added to questions which are more than 30 days old. However the issue with the tool is that it is not real time. There are requests on Stack Overflow Meta to not only make it real time but also to enh...
@Magisch Hmm. I could get behind that as long as it was just for GitHub domains. But that seems super specific for little benefit (6 false positives isn't really too bad)
I joined that room already, but I don't necessarily want to go through the whole log to determine the number of AU reports, in case you know a rough magnitude.
@Mithrandir btw, you can/should probably tell that story @ThomasWard as well, as he's an AU mod and room owner of the General Room. And @Zanna as owner of the lost Downboat is also already here.
Mith expressed their disappointment about Natty reports (potential NAA answers to 30+ days old questions) for AU get too few attention and we were talking about adding that bot to some AU rooms like e.g. the General Room or your Downboat.
Background and History
The New Answers to Old Questions tool helps us to find all the answers added to questions which are more than 30 days old. However the issue with the tool is that it is not real time. There are requests on Stack Overflow Meta to not only make it real time but also to enh...
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +1 more: NitroNemax Trial Reviews by thoraxin on askubuntu.com