« first day (1710 days earlier)      last day (2108 days later) » 

12:12 AM
fp by Nisse Engström
 
12:49 AM
!!/watch cryptodatadownload\.com
 
@Makyen 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.
 
@Catija so awesome!! When did that happen?
 
Today.
 
I take it that you applied to it a few months back when they posted? (I think @Andy was talking about it)
 
Congrats! I hope you enjoy your time with them.
 
12:54 AM
Most diamonds created in charcoal at once :P
 
@Catija A remote job will make it even more convenient for you to take care of Bennett and his upcoming brother
 
@WELZ I did. :) The whole process took a while. :) But I'm happy to join the Team.
 
1:29 AM
[ SmokeDetector | MS ] Shortened url in body: Retrieve the original URL from Twitter's short URL (t.co link) by Mals on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body: Obat Herbal Telinga Berair by obattelinga on meta.SE
 
2:19 AM
tpu- by Makyen
 
2:29 AM
!!/test rumahjellygamat.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 1-20: rumahjellygamat.com
Body - Position 1-20: rumahjellygamat.com
Username - Position 1-20: rumahjellygamat.com
 
!!/test ahlinyaobatmaag
 
> Would not be caught as a post, title or username.
 
!!/test ahlinyaobatmaag.com
 
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Title - Position 1-20: ahlinyaobatmaag.com
Title - ahlinyaobatmaag.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com.
Body - Position 1-20: ahlinyaobatmaag.com
Post - ahlinyaobatmaag.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com.
Username - Position 1-20: ahlinyaobatmaag.com
 
2:32 AM
!!/watch qncjellygamat20\.blogspot
 
@TetsuyaYamamoto Added qncjellygamat20\.blogspot to watchlist
Restart: API quota is 17868.
 
2:45 AM
tp- by Makyen
 
@SmokeDetector Undisclosed affiliation, but it's just the user putting in a signature. I submitted an edit.
 
!!/test umbsstudio.com
 
> Would not be caught as a post, title or username.
 
!!/watch umbsstudio\.com
 
2:55 AM
@TetsuyaYamamoto Added umbsstudio\.com to watchlist
CI on 1f3db44 succeeded. Message contains 'autopull', pulling...
Restart: API quota is 17744.
 
!!/watch oneoffjobs\.com
 
@Makyen Added oneoffjobs\.com to watchlist
 
!!/test australianwritings.com.au
 
> Pattern-matching website in body, pattern-matching website in title
----------
Title - Position 6-22: alianwritings.co
Body - Position 6-22: alianwritings.co
CI on bc5cdbc succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at rev bc5cdbc (SmokeDetector: Auto watch of oneoffjobs\.com by Makyen --autopull) (running on teward/Solar Flare)
Restart: API quota is 17734.
tp by Tetsuya Yamamoto on How does SCR work [MS]
 
!!/watch australianwritings\.com\.au
 
3:01 AM
@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.
tp by Tetsuya Yamamoto on Creating USB Disk from bootable CD [MS]
tp by Tetsuya Yamamoto on What is a "15-hit kiss"? [MS]
 
@TetsuyaYamamoto Just going ahead and doing !!/watch without !!/test beforehand is usually equivalent to doing one after the other. The only time it's not is for non-trivial regexes, where you would need to run separate test cases to see if the base thing your testing for is detected. There are also a couple of edge cases, but for most simple things, like domains, it's just easier to go ahead and !!/watch.
 
3:31 AM
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, potentially bad keyword in body, +2 more: mumybear.com/super-keto/ by user46986 on rpg.SE
tpu- by Tetsuya Yamamoto
 
3:54 AM
[ SmokeDetector | MS ] Potentially bad keyword in body: grab all .mp4 links from webpage by php by shadmehr vasighi on stackoverflow.com
fp- by Tetsuya Yamamoto
 
@SmokeDetector why
@SmokeDetector Redacted the link, but still an unclear Q.
 
sd poof
!!/watch-force pornhd\.com
 
@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.
 
But you didn't catch it, SD.
 
@Makyen Added pornhd\.com to watchlist
CI on b7c4f22 succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at rev b7c4f22 (SmokeDetector: Auto watch of pornhd\.com by Makyen --autopull) (running on teward/Solar Flare)
Restart: API quota is 17466.
 
4:27 AM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body: Intensacut Forskolin review by ugrw on superuser.com
tpu- by Shree
 
4:45 AM
[ SmokeDetector | MS ] Link at end of answer: how do i setup a node for my altcoin? by David Designer on bitcoin.SE
tpu- by Makyen
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, potentially bad ns for domain in body, +1 more: Rapid Tone Canada Weight Loss by tracyealko on graphicdesign.SE
 
!!/watch coinigraphy\.com
 
@Makyen Added coinigraphy\.com to watchlist
tpu- by Makyen
[ SmokeDetector ] SmokeDetector started at rev a905f8e (SmokeDetector: Auto watch of coinigraphy\.com by Makyen --autopull) (running on teward/Solar Flare)
Restart: API quota is 17223.
[ SmokeDetector | MS ] Url in title, pattern-matching website in body, pattern-matching website in title, potentially bad ns for domain in body, potentially bad ns for domain in title, +2 more: www.usafitnessguide.com/keto-nurturing/ by neilminer on graphicdesign.SE
tpu- by Makyen
tp by Nisse Engström on how do i setup a node for my altcoin? [MS]
tp by Nisse Engström on Rapid Tone Canada Weight Loss [MS]
tp by Nisse Engström
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more: Intensacut Forskolin pills reviews by user926893 on superuser.com
tpu- by Makyen
tp by Nisse Engström
 
5:05 AM
[ SmokeDetector | MS ] Blacklisted website in body, link at end of body, pattern-matching website in body, repeated url at end of long post: Hidden Answers To male power Revealed by user852853 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, link following arrow in title, +4 more: OFFICIAL TRAIL@>>>>wellnessfeeds.com/rapid-tone-canada/ by Dhshjjbdjj Xf on askubuntu.com
 
@SmokeDetector tpu-
@SmokeDetector tpu-
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more: Intensacut Forskolin price by hollavertor on askubuntu.com
[ SmokeDetector | MS ] Url in title, pattern-matching website in body, pattern-matching website in title, potentially bad ns for domain in body, potentially bad ns for domain in title, +2 more: www.usafitnessguide.com/keto-nurturing/ by user125069 on graphicdesign.SE
tpu- by suraj on Intensacut Forskolin price [MS]
tpu- by suraj
 
5:25 AM
@EriktheOutgolfer Realisticly speaking, the cases where this error is going to come into play are mostly going to be borderline
 
[ SmokeDetector | MS ] Potentially bad keyword in body: Solve the Algebraic Question? by padmesh gupta on mathoverflow.net (@FrenzyLi)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more: What Do You Benefits Crazy Bulk ? by clementrawhite on meta.SE
 
5:42 AM
!!/watch padmesh\W?gupta
 
@WELZ Added padmesh\W?gupta to watchlist
[ SmokeDetector ] SmokeDetector started at rev e38764a (SmokeDetector: Auto watch of padmesh\W?gupta by WELZ --autopull) (running on teward/Solar Flare)
Restart: API quota is 16891.
 
5:57 AM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more: Intensacut Forskolin a scam by pqsw on superuser.com
[ SmokeDetector | MS ] Bad keyword in title, potentially bad keyword in body: software testing courses in chennai by suvathi 018 on stackoverflow.com
tpu- by WELZ on Intensacut Forskolin a scam [MS]
tpu- by WELZ
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, pattern-matching product name in body, +5 more: Total Tone Diet : supplementstruera.com/total-tone-diet/ by doresndson on askubuntu.com
tpu- by Shree
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in username, blacklisted user: Solve the Algebraic Question? ✏️ by padmesh gupta on mathoverflow.net (@FrenzyLi)
tpu- by WELZ
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more: Intensacut Forskolin return policy by user926907 on superuser.com
 
6:17 AM
!!/watch zuaneducation\.com
 
tpu- by Tetsuya Yamamoto
@TetsuyaYamamoto 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.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body: Inspect scope of anonymous function ✏️ by J. Doe on stackoverflow.com
tp- by Tetsuya Yamamoto
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected: R X-axis Date Labels using plot() by Noobs on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body: Uploading a file on non input type="file" by KJ1 on stackoverflow.com
fp- by iBug
 
6:50 AM
[ SmokeDetector | MS ] Link at end of answer: MySQL Server Installing Taking too long by ShawnR on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin purchase by user926921 on superuser.com
tpu- by iBug
fp- by iBug
 
7:04 AM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin pills ingredients by nicolejavers on askubuntu.com
tpu- by iBug
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, repeated url at end of long post: PureFit StellaTrim is really works? by nemdeclina on superuser.com
tpu- by iBug
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching product name in body, pattern-matching website in body, +2 more: Super Keto Diet Weight Loss Formula That Reduces Fat by user852894 on askubuntu.com
tpu- by iBug
 
!!/blacklist-keyword purefit\W?stellatrim
 
@iBug Blacklisted purefit\W?stellatrim
Restart: API quota is 16271.
[ SmokeDetector | MS ] Potentially bad keyword in answer: how to generate ethereum qr code address with amount? by Tera on stackoverflow.com
fp- by iBug
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body: t is the first treatment approved by user852900 on askubuntu.com
tpu- by Tetsuya Yamamoto
 
!!/watch Alpha\W?Titan\W?Testo
 
@Glorfindel Added Alpha\W?Titan\W?Testo to watchlist
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad ns for domain in body, potentially bad ns for domain in title, +2 more: supplentforhealthylifestyle.org/rapid-tone-canada/ by berklase on english.SE
tpu- by iBug
tpu- by Tetsuya Yamamoto
[ SmokeDetector | MS ] Pattern-matching website in body: RevenueCat Unity, error: EntryPointNotFoundException: _RCSetupPurchases by Pikachu on stackoverflow.com
Restart: API quota is 16214.
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user: How to fix this SQL Server Management Studio error? by shivguptag on stackoverflow.com
[ SmokeDetector | MS ] Pattern-matching website in body: RevenueCat Unity, error: EntryPointNotFoundException: _RCSetupPurchases by Pikachu on stackoverflow.com
 
7:20 AM
@SmokeDetector ig
 
fp- by Glorfindel
 
What is ig? o_O
 
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, potentially bad keyword in body, potentially bad keyword in title: Super Keto And a very good supply by noruwa12 on askubuntu.com
 
@ByteCommander ignore
 
tpu- by iBug
 
7:21 AM
ah, sure.
thanks
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin weight loss price by vurw on superuser.com
tpu- by iBug
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more: www.garciniacambogialean.com/nutralite-keto by Utmacksmay90 on drupal.SE
tpu- by iBug
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, potentially bad ns for domain in body: Prodiet Plus How Prodiet Plus by user125070 on graphicdesign.SE
tpu- by iBug
 
7:38 AM
@Undo I have an idea though. What if a post gets 2+ TP feedbacks quickly (and was not autoflagged) that MS could choose to cast some additional autoflags on it?
I would need to pull stats on that, but it seems to me that a double whammy of incorrect classification should be really rare with the low rate of invalid feedback everyone got.
 
Feels much like sockpuppetry to me.
 
We're already doing more then that
Unless you find fully automated sockpuppetry to be more acceptable
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin risks by user926934 on superuser.com
tpu- by Mithrandir
Restart: API quota is 16002.
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +2 more: www.bluesupplement.com/stella-trim/ by ayonalol n159 on rpg.SE
tpu- by iBug
[ SmokeDetector | MS ] Bad keyword in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, potentially bad ns for domain in body, +2 more: Conclusion people looking for to try by alicecarol6 on askubuntu.com
tpu- by PeterJ
[ SmokeDetector | MS ] Potentially bad keyword in answer: What movies like Amélie (2001)? by K. Noviews on movies.SE (@AJ)
tpu- by iBug
 
8:02 AM
[ SmokeDetector | MS ] Potentially bad keyword in username: Read html with Beautifulsoup and find typical data by Gangil Seo on stackoverflow.com
fp- by iBug
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body: Diseases that specifically attack the cardiovascular by user852900 on superuser.com
tpu- by Glorfindel
 
@SmokeDetector f
 
@SmokeDetector ig
 
@SmokeDetector ig
 
8:10 AM
fp- by iBug
 
8:26 AM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin on amazon by zoereichert on askubuntu.com
tpu- by Glorfindel
[ SmokeDetector | MS ] Username similar to website in answer: Would Diaspar survive if Earth was destroyed? by Diaspar on scifi.SE (@Mithrandir)
[ SmokeDetector | MS ] Potentially bad keyword in answer: How to check whether an email id exists or not? by sici on stackoverflow.com
tpu- by Glorfindel
[ SmokeDetector | MS ] Bad keyword in answer, link at end of answer: Is this a good structure for my website? by user309744 on codereview.SE
tpu- by Glorfindel
 
!!/watch telsamedia\.com
 
@Glorfindel Added telsamedia\.com to watchlist
Restart: API quota is 15559.
 
[ SmokeDetector | MS ] Potentially bad keyword in answer: Radio buttons Responsive Web Design by user309744 on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user: Can I use a header tag in footer inside section? by user309744 on codereview.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user: SEO Keyword Counter by user309744 on codereview.SE
 
@SmokeDetector tpu-
 
8:34 AM
 
@SmokeDetector tpu-
 
@SmokeDetector tpu-
 
@SmokeDetector k
 
8:35 AM
tpu- by Makyen
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad pattern in url body, blacklisted username, blacklisted website in body, +1 more: This supplement increases sexual vigor to the zenith by filipjuriya on 3dprinting.SE
tpu- by Makyen
 
!!/notify 13848 rpg.stackexchange.com
 
@doppelgreener You'll now get pings from me if I report a post on rpg.stackexchange.com, in room 13848 on chat.stackexchange.com
 
doppelgreener has upgraded to triplegreener
quadruplegreener, dare we dream?
:p
 
> Url in title
----------
Title - Position 1-37: https://codereview.stackexchange.com
 
[ SmokeDetector | MS ] Blacklisted user: Do HTML tags make a difference? by user309744 on codereview.SE
 
kk...
 
@Vogel612 BTW: !!/report has been modified such that it does a !!/scan first. Thus, if you are sure you want something reported, even if not detected by SD as spam, then just go directly to !!/report.
 
@Makyen I'm aware 😀 thanks for the heads up.
 
fp- by doppelgreener
 
8:54 AM
That's just a low quality post, but given the # of spam answers they've posted already, I'd like to keep them blacklisted.
Better: nuked :)
 
[ SmokeDetector | MS ] Bad keyword in title, potentially bad keyword in body, potentially bad keyword in title: Where to Buy” Super Keto Diet: Reviews, Weight Loss Diet Pills Price by JefferAntho on drupal.SE
 
@SmokeDetector naa-
 
tpu- by bertieb
[ SmokeDetector | MS ] Link at end of body, link following arrow in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more: to expect excessively from something that regularly drives us to absolute frustrations by Dougedward on superuser.com
tpu- by doppelgreener
tp by Shree
[ SmokeDetector | MS ] Potentially bad keyword in body: How do I get and use the gitlab-ci-token in GitLab CI programmatically? by Chloe Bennett on stackoverflow.com
fp- by doppelgreener
 
why was that caught?
 
@SmokeDetector why
 
9:04 AM
@Magisch Body - Position 1146-1168: >>>> git push https://, Position 1573-1595: >>>> git push https://, Position 2010-2039: >>>> git push origin https://
 
what on earth is catching a git push command though
 
I think it's the same filter that catches visit here <link>
 
[ SmokeDetector | MS ] Link at end of body, link following arrow in body, pattern-matching website in body, repeated url at end of long post: Why Sleep Well Sleep Aid Is Famous In People? by mk2748969 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin on the doctors by user926938 on superuser.com
tpu- by PeterJ
 
9:08 AM
looks like an experimental expansion of link after arrow
 
tp by Shree
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, link at end of body, +2 more: fitnessexpertadvice.com/rapidtone-canada/ by jameevan on drupal.SE
tpu- by Glorfindel
[ SmokeDetector | MS ] Bad keyword in link text in answer, pattern-matching website in answer, username similar to website in answer: SecurityGuard connections to database by United Guard Force India on stackoverflow.com
tpu- by rene
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, pattern-matching product name in body, potentially bad ns for domain in body, +3 more: Super Keto Dietfactforhealth.com/super-keto-diet/ by LanDavis on drupal.SE
 
@Mithrandir That's exactly what it is.
 
tpu- by PeterJ
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more: True Trim Forskolin before and after by rlrw on superuser.com
tpu- by PeterJ
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +2 more: *One Lite Forskolin put in be in harmony by user852936 on askubuntu.com
tpu- by PeterJ
tpu- by Mithrandir
 
@Makyen I have an idea. It would be nice if smokey reported an optional comment behind the line of regex that tripped a post
So you'd comment "Experimental expansion of link after arrow" after your line of regex and smokey would give that reasoning once someone asked why on a post holding it
 
@Magisch That would be convenient, doable by expanding the watched_keywords.txt file format. However, in the file, the comment needs to be before the regex, so that the regex isn't delimited, except by the tab at the start.
 
9:19 AM
@Makyen Ideally we'd have a short, reportable explaination before every watch/blacklist/regex that tells us on first glance what it's catching and why
This would eliminate the need for the authors of said regex to be around to know what their regex is doing
 
@Magisch That would be nice, but would be a significant increase in processing for SD. Currently all watchlist and blacklist items are merged into a single regex for testing. To do what you want, you would have to test each individually.
 
@Makyen Would you? You could run the post through the logic with 1by1 regexes when a "why" is requested, no?
 
To be fair, the individual tests are only needed for the tiny fraction of posts that actually match the big regex.
 
@Magisch We should be around to be looking at what our regexes are doing. Part of putting something on the watchlist is analyzing what the matches are.
 
Sure, but it'd be even better if everyone had a way to get that big picture quickly
 
9:23 AM
@Makyen true, but !!/watches are often FIRE & forget. Which is not a problem for the majority, the straightforward ones.
 
Well, I was already planning on putting that in FIRE, because I was getting tired of having to guess at decoding the why to see what reason the different matches actually were.
 
+1 for that
It'd be nice to benchmark how much slower individual matching vs 1 big regex would be
And if it'd even be worth separating out of if the performance diff is so small as to be unnoticable
 
The times that I've benchmarked it on other projects it's been significant, but it does a more thorough job of matching, because matches that are overlapping will individually match, rather than just match the largest.
 
I maintain that we could keep the current logic and implement a second "1 by 1" route that gets used when someone requests a why. That happens rarely enough that even if the processing takes like 1s (so 50x as long) it wouldn't really matter
Or maybe make a thorough-why command variant
 
!!/why-force
 
9:27 AM
@Glorfindel No such command 'why-force'.
 
@Glorfindel Yes, but at least for the complex ones, I feel a responsibility to revisit them to see what they are detecting and if they can be improved. Admittedly, I sometimes fall behind on doing that.
 
We should make an effort to differentiate our regexes and generate proper documentation as to why they're there anyways
right in the code so it's visible
 
Just having the actual matches be directly associated with the reason, rather than only reason-anonymously grouped in the why would be helpful.
@Magisch That would be nice, and Python has an explicit mode for regexes that permits documentation. It's just not used in findspam.py. I've certainly been considering looking into how much restructuring would be needed to gradually add it in.
 
@Makyen If you need some help on the dirty annoying work for that, hit me up
 
9:32 AM
You mean the mode that allows inline comments inside the regex pattern?
 
@Magisch If you're wanting to do it, you're welcome to do so. For me to do it I'd A) need to learn Python (but it's just yet another computer language) and set up an SD instance so I could test.
 
@Makyen Same here. I have no experience with python or hosting SD
 
running a Smokey instance isn't hard
 
@ByteCommander Yes. It would work for what's in findspam.py, but something else would be needed for what's in the watch/black lists. However, the watch/blacklists could easily just have a field added prior to the regex which was the comment.
 
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +5 more: Rapid Tone Diet Weight loss by oraliadavis on meta.SE
tpu- by PeterJ
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more: funmuscle.com/one-lite-forskolin/ by Wountold1935 on drupal.SE
tpu- by Glorfindel
[ SmokeDetector | MS ] Potentially bad keyword in body: Uncontrolled ejaculation of semen while pooping by Sanjay on health.SE
fp- by Glorfindel
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +1 more: Stella Trim Ones that does not by yumieu12 on askubuntu.com
 
9:47 AM
@doppelgreener Just FYI: The regex explicitly excludes things that would be caught by the current "Link after arrow" reason. Part of that is requiring the distance to the end of the material being tested being longer than 200 characters. The excerpt from the post that you were testing was too short (and you had a copy-&-paste error in the regex). Here's a regex101 that shows the matches.
Having the expanded version in the watch is A) to catch posts that the current "Link after arrow" has been seen to be missing, but also, to a large extent, to get the data needed to determine what additional things should be excluded. This is an additional example that items in code format should be excluded, which is relatively easy to do, even in just a regex. I hadn't done so yet in order to get more data to know if there are things in code format that we need to detect.
 
tpu- by PeterJ
 
10:01 AM
@Makyen Ok, I see
I'm concerned that we can't really analyse the results of that regex unless we can also correspond captures to specific regexes, but that's a structural issue rather than an issue with that regex
 
[ SmokeDetector | MS ] Bad keyword in body: How Ubuntu help us? by Art Brediger on askubuntu.com
[ SmokeDetector | MS ] Link at end of answer: SQL Client for Amazon Redshift ✏️ by Selcuk Kiziltug on stackoverflow.com
tpu- by PeterJ on How Ubuntu help us? [MS]
naa- by kayess
 
@doppelgreener It's possible to do, on MS, by running (searching) the regex against the posts which were detected for "Potentially bad keyword in {}". It's a pain in the rear to have to go through it that way, but without more tooling... (e.g. I've using the JS Data Explorer, but the last time I tried it I crashed MS, so I'm not trying that method.) I'm considering modifying some stuff to be able to do testing locally, but I haven't gotten to it yet.
 
J F
To determine which watched keyword was matched, could we break them up groups of 100 or so that would each be run on posts that trip the whole regex so we’d only have to run a maximum of 468 + 102 = 570 checks instead of 4672?
Also, @Catija are you our new SE rep?
 
@JF If we're going to do something like that, then we might want to build regexes to be able to do a binary search. Frankly, how to do it is going to depend on performance, which we can play with once something's coded. It's also necessary to keep in mind that there might be matches from multiple entries.
 
fp- by doppelgreener
 
10:24 AM
@Makyen hah, that's part of the reason some things never get out of the watchlist, no? we're all guilty, right? :P
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +3 more: Total Tone Diet Do you know what by kevinerrill on askubuntu.com
 
@EriktheOutgolfer True, but I do personally feel responsible for the ones I put on the list.
 
tpu- by PeterJ
tp by Erik the Outgolfer
 
it's not like it's easy to analyze anyway
 
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, pattern-matching website in body, +2 more: You will constantly solicit and move by fisw on superuser.com
tpu- by Glorfindel
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad pattern in url body, blacklisted username, blacklisted website in body, +2 more: this object and it consists of of labile by tusanjuriya on askubuntu.com
 
10:40 AM
No, it's not. I've largely resigned to either struggling with the search interface, or having to build the tools (or modify existing tools) to do so. Part of the frustration is that regex searches are quite slow (e.g. a single regex search can take 10+ minutes. There have been significant performance improvements, but it's still frustrating. Before the improvements, my longest single regex search was 46 minutes and it blocked MS API traffic. Fortunately, searches no longer block MS API traffic.
 
tpu- by Makyen
 
10:54 AM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, link following arrow in title, +7 more: READ MORE@>>www.muscle4supplement.com/rapid-tone-shark-tank/ by Dhshjjbdjj Xf on askubuntu.com
tpu- by Shree
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, +3 more: maximum hard sporting events to carry out by user926993 on superuser.com
tpu- by Henders
 

« first day (1710 days earlier)      last day (2108 days later) »