@WELZ Basically an end of year celebration StackExchange does. You get hats for completing 'challenges'. Most (all?) requirements are unknown, and people figure out what needs to be done to get a hat.
Ten-second opinion poll: if I implemented link shortener resolution, from a security perspective, would y'all be happier if I did the resolution in-house with HEAD requests from requests, or used an external API?
In fact scratch that, from all perspectives not just security. I know what the answer is for security.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +1 more: Titanax Male Enhancement by jcore12 on astronomy.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: Excessive exercise by xeecurjgq on drupal.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, +2 more: Test X 360@Test X 360 by maujkro on askubuntu.com
> 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, pattern-matching website in title ---------- Title - Position 1-23: newsupplements2017.com Title - Position 4-22: supplements2017.co Title - newsupplements2017.com NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com. Body - Position 1-23: newsupplements2017.com Body - Position 4-22: supplements2017.co Post - newsupplements2017.com NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com.
(Okay, sarcasm aside) I was browsing through the badge list a while ago and got an eyeful of this:
I couldn't get them all in one screenshot, but these are the (spam) accounts I've seen so far (I suspect there are more, but they probably got pushed down the list by the time I had a look...
@Glorfindel The wiki page related to this isn't up to date. I'm not sure how big of a deal that is, but since there was an explicit comment about it in the code... github.com/Charcoal-SE/SmokeDetector/blob/…
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; use !!/watch-force if you really want to do that.
@angussidney I am aware of 23 code admins. Currently in this room: angussidney, Mithrandir, bwDraco, Suraj Rao, ArtOfCode, Glorfindel, Byte Commander, Ferrybig, Magisch. Not currently in this room: Thomas Ward, doppelgreener, tripleee, John Dvorak, Yvette Colomb, ProgramFOX, Ashish Ahuja, Henders, DavidPostill, Paul Stenne, Andy, Undo, quartata, NobodyNada.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, bad pattern in URL body, blacklisted website in body, +2 more: Vyalis Rx Male Enhancement by user78622 on diy.SE
@SurajRao That pattern looks like it's already caught by Bad ns for domain in body, Bad keyword in body, Bad keyword in answer, and Bad ns for domain in answer; use !!/watch-force if you really want to do that.
@RoryAlsop I already declined their flags, and presumably they wouldn't have cast them if not for Smokey's auto algorithm. So not sure if there's any point in a superping.
@ByteCommander I already did decline them, before even coming in here.
currently at 11/12 so only one FP so far, but the last TP was 17 days ago so we might consider removing it if we believe that there will be no further spam with this term
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +5 more: healthflyup.com/shred-fx/ by hatyweki on graphicdesign.SE
@Randal'Thor yeah, even if you did know they were autoflags, declining was the correct course of action. Although it is nice that people might get a chance to retract their flags, the way you handle flags shouldn't change just because Smokey is involved. People knew the risks when they set their settings so low.
@SurajRao That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; use !!/watch-force if you really want to do that.
@SmokeDetector regarding this: why is autoflagging enabled on such old posts? Autoflagging is only enabled (AFAIK) for posts which are still in their first revision (to prevent vandalism from being flagged). I think we can safely disable it for posts older than 24 hours, maybe even less.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 13-22: ebcoo.net Body - Position 13-22: ebcoo.net Username - Position 13-22: ebcoo.net
CI on d7de045 succeeded. Message contains 'autopull', pulling...
> Url in title, blacklisted website in body, blacklisted website in title ---------- Title - Position 92-110: nescomatrimony.com Title - Position 81-110: http://www.nescomatrimony.com Body - Position 92-110: nescomatrimony.com
(Okay, sarcasm aside) I was browsing through the badge list a while ago and got an eyeful of this:
I couldn't get them all in one screenshot, but these are the (spam) accounts I've seen so far (I suspect there are more, but they probably got pushed down the list by the time I had a look...
