« first day (2459 days earlier)      last day (1354 days later) » 

6:01 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Intersection observer not working on mobil with 2 sections by Cyril on stackoverflow.com
 
@tripleee If you're thinking (?:mother)?f(?:\W*[au])+[ck]+(?<!fa(?:[ck][ac]))(?:er|ed|ing?)?s?, that doesn't seem to work. It catches a lot more than it should and a lot more than the original. Actually makes it worse.
 
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body (96): Moving characters for fitness app by Lamis on stackapps.com
fp- feedback received on Moving characters for fitness app [MS]
fp- feedback received
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, potentially bad keyword in answer (172): Apple Transport Security by sarah maria on stackoverflow.com
tpu- feedback received
 
6:21 PM
sdc blacklist-number +2348143581382
 
@Mast That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; append -force if you really want to do that.
 
@SmokeDetector why
 
Bad keyword in answer - Position 127-223: love him so much. i was really going too depressed and a friend directed me to this spell caster, Position 790-803: 2348143581382
Bad keyword in answer - Position 905-911: HERPES
Bad keyword in answer - Position 905-911: HERPES
Bad keyword with email in answer - Obfuscated email babatundesolutioncentre1@gmail. com
Potentially bad keyword in answer - Position 224-233: Dr. Tunde, Position 687-711: babatundesolutioncentre1, Position 712-722: gmail. com
 
Ah, it's hidden at the end of the first line.
I missed that, too.
 
I know it's there, but I'm wondering why it shouldn't be on the dedicated list for numbers.
That's what that list is for, right?
blacklisted_numbers
 
6:31 PM
@Mast Because it's in a large swath of numbers were blacklisted years prior to the existence of the numbers list. There's hundreds of numbers that need to be reorganized. That particular detection should be moved into a new blacklisted patterns detection and the individual numbers placed on the blacklisted numbers list.
 
user435118
@Makyen In line with that, we should probably check the watchlist for domains that haven’t been used for a long time to improve scan speed
 
teward/Osiris: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev bc83caa (SmokeDetector: Auto watch of topspying\.com by tripleee) (running on teward/Osiris, Python 3.6.9)
Restart: API quota is 9657.
[ SmokeDetector | MS ] Offensive body detected, offensive title detected, potentially bad keyword in username (96): Is replika.ai FASCIST? by Anthony Dwayne Chapelle on ai.SE
tpu- feedback received
 
There goes the troll again.
 
@Daniil We could, but if scan speed is the issue we're addressing, then we should focus on the regexes which actually take significant time first. The ones which just a small incremental amount of time, while there are certainly a lot of them, and removing some would be a good idea, don't get us much, except by removing them in bulk. However, removing them in bulk means we're not really evaluating them.
We have had times when a keywords has returned to being active years after the last time it was observed. It's really hard to guess what those might be prior to them happning.
 
But for starters it would help if we split them up?
Or is it better to leave them be?
 
6:43 PM
@Mast you want [ck]|ac not [ck][ac] in the negative assertion
 
@Mast I'm not sure what you're asking wrt. "split them up"
 
> That particular detection should be moved into a new blacklisted patterns detection and the individual numbers placed on the blacklisted numbers list.
 
That's what I'm referring to.
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): What's the deal with X25519 Support in Chrome/Firefox? ✏️ by Jim Landy on security.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Calypso with quantum espresso for nanoparticles by Shafayet Rahat on mattermodeling.SE
 
6:48 PM
@Mast Basically, there are some organizational issues that were created along with the creation of the watch/blacklisted numbers lists. Those have never been fully resolved, because things basically work the way they are and everyone has had other things they consider a higher priority.
 
iBug/Coral: Executing automatic scheduled reboot.
 
@Makyen I understand, it's not particularly a matter of a couple quick fixes to get it sorted.
Every time I'm trying to help out with the small stuff I get stumped.
 
7:11 PM
@Mast You're doing well. We appreciate the help. Sometimes, what looks like a little problem is the tip of an iceberg, which may, or may not, be something you want to deal with.
 
@Makyen I'm willing, but I'm not a developer (anymore). I do have limited regex experience, but it still looks like black-magic at times and I'm very familiar with how out-of-hand legacy projects can get.
So there will be problems that I'm more than happy to do some legwork for, yet I tend to bite off more than I can chew :-)
I have some leave coming up, got some experiments with flowcharts on my to-do list. Might have some time to actually understand Smokey :-)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): A single pci-e connector on my gpu is bent by Snoop Doop on superuser.com
fp- feedback received
 
@Mast If you want to work on SD, I'm sure your help will be appreciated.
 
@Makyen I'll give it a shot at least, but I'm tired of overpromising and underachieving. We'll see what comes out.
 
7:20 PM
fp- feedback received
 
user435118
@Makyen How about we have 2 versions of SD running? One as-is, one with cleared lists, when new stuff gets caught on the current one, add it to the new one accordingly. Then shut the current lists down after 6 months?
 
user435118
This could help us organise the number lists and improve any regexes we have
 
@SmokeDetector f"acked is the start of an f-string, not offensive.
 
user435118
We could keep some of the rude regexes as-is to not rewrite them
 
[ SmokeDetector | MS ] Post is mostly images (13): Download Pic Form HTML by Tamir Eliyahu on stackoverflow.com
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
7:31 PM
@Daniil Why? What actual problem are you trying to solve?
 
user435118
@Makyen Inefficient regexes, obsolete [watch/black](list) items
 
@Daniil What actual problem are they causing?
 
user435118
@Makyen Messy regex items, slower scan time
 
@Daniil How are those causing a problem? Are the SD instances unable to keep up with scanning?
 
user435118
@Makyen There’s probably a backlog most of the time
 
7:37 PM
I'd guess increasing total amount of hits while increasing the TP/FP ratio is of higher concern.
 
user435118
@SmokeDetector Not a lot of images at all, this is happening too much now
 
user435118
sdc bisect Shiv Gupta
 
@Daniil Matched by (?-i:^Shiv Gupta$) on line 346 of blacklisted_usernames.txt
 
user435118
@SmokeDetector fpu-
 
7:41 PM
sdc alive
 
@Mast Of course
 
sdc bisect Shiv Gupta
 
@Mast Matched by (?-i:^Shiv Gupta$) on line 346 of blacklisted_usernames.txt
 
@Daniil It's going to take more than that.
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, blacklisted user (72): Cannot connect MySQL Workbench to MySQL server by Angel Torre on askubuntu.com
tpu- feedback received
 
user435118
7:48 PM
@Mast ?
 
@Daniil To get that user from the blacklist.
That was the goal with fpu-, right?
 
@Mast That's what fpu does, yes
 
So that's what I said, it's going to take more than that.
 
user435118
@Mast What do you mean?
 
blacklisted_usernames.txt, line 346. That's what you need to modify to get what you want, right?
 
user435118
7:52 PM
I made that specific user exempt, I don’t want to remove the username from detection
 
The fpu- list (whatever it's called) overrules the blacklisted_usernames file?
Like a negative look-behind, effectively, excluding it from the found results?
 
8:04 PM
@Mast Blacklists don't apply to whitelisted users
 
That's the word I was looking for, thank you.
Although there's no whitelist_usernames file, so I'm not sure where they're stored.
 
iBug/Sandy: Executing automatic scheduled reboot.
 
@Daniil have a look at the scan rates reported on metasmoke, that'll tell you
 
user435118
@ArtOfCode How will they tell me?
 
@Daniil if posts per day < scan capacity per day, we're good
if not, we got problems
 
8:37 PM
fp- feedback received
fp- feedback received on NodeJS Invalid_grant gaxios.js:85:23 [MS]
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Problema nas fontes do site hospedado by Renillson Santos on pt.stackoverflow.com
 
user435118
@ArtOfCode Where’s scan capacity per day?
 
fp- feedback received
 
8:54 PM
that's per second
so multiply by 86400
 
@Mast The user whitelist (along with the user blacklist, information about recent reports and chat messages, !!/notify preferences, and more) is stored in a local pickle (so it's not uploaded to GH or MS, and it isn't synced to other SD instances).
 
@ArtOfCode So, we stay under 50% at all times, even just before the reset?
 
@Mast I think that's API quota you're looking at, which is the number of requests SD is allowed to make to the Stack Exchange API. In this case, however, we're instead talking about the percentage of available CPU power our regexes are consuming.
 
not available CPU power either
just the number of posts we can scan per second
 
@ArtOfCode isn't that CPU-bound?
 
8:58 PM
yes and no
couldn't tell you precisely what the bottleneck is, but it doesn't tend to run at 100% CPU
 
@NobodyNada Only that? It's never synced to (semi-)permanent storage?
def add_whitelisted_user(user):
    if user in GlobalVars.whitelisted_users or user is None:
        return
    GlobalVars.whitelisted_users.add(user)
    _dump_pickle("whitelistedUsers.p", GlobalVars.whitelisted_users)
That indeed only puts it 'in memory'.
 
@Mast It saves it to the file whitelistedUsers.p
 
Yes, but is that read by the next instance on boot or whiped on shutdown?
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Is there an "art" term for this kind of palette? by Richard Klassen on graphicdesign.SE
 
@Mast It's loaded on startup, but it doesn't sync across instances of SmokeDetector running on different machines
it survives reboots, but not failovers
 
9:02 PM
Ah, ok.
 
"Instance" in CHQ generally means a single machine running a single checkout of SmokeDetector; even if you reboot it's technically still the same instance
(See metasmoke.erwaysoftware.com/status for the list of all instances)
 
And multiple instances (multiple 'servers') can be running at the same time.
Which leads to very interesting effects sometimes.
 
That's correct. Normally we keep one instance active and the rest in standby, but if two instances end up active then they will both respond to commands
 
It looks like Osiris is doing most of the heavy lifting lately.
Naturally the blacklisting/whitelisting is all explained in the docs, but it only makes sense after you've got your nose smashed into it.
> The user-blacklist and user-whitelist are maintained per SmokeDetector instance. The SmokeDetector instances do not share these lists between themselves. Thus, if the SmokeDetector instance is switched, the new instance will only have a record of the entries on these lists which were added/removed while that instance was active.
 
@Mast Yep. It's best to stay on one "primary" instance (because the pickles won't sync), and we usually use Thomas's instances because his infrastructure is very reliable, powerful, and well-maintained
 
user435118
9:09 PM
@ArtOfCode That’s a massive issue. We need to get that capacity up urgently
 
@Daniil Hm?
 
@Daniil unless I'm missing something, it looks like capacity is about ~150k posts/day, while we're currently scanning ~100k posts per day
Which...might be an issue eventually, as we keep adding more regexes, but we seem to be in decent shape for now
Especially since overall activity on the SE network is trending downwards IIRC
 
bear in mind also that IIRC that's per-thread
 
Daily graph has a peak on 104479 (July 21), we've been doing fine as far as the graph goes back.
 
@ArtOfCode Interesting, didn't realize we were multithreaded, but glancing through the code, that looks right
 
user435118
9:38 PM
@NobodyNada It is, SE is dying :( is there a graph of overall activity on SE and the trend?
 
@Daniil If you don't mind only having yearly accuracy, Shog used to post 'A year in moderation' posts on all metas.
So you could take the 2019 and 2018 versions of the same site and see the difference in stats.
For SO:
And no, there's no 2017.
Not that I know of anyway.
Anyway, if you take those stats from a couple of sites, you have some network-wide yearly data that should provide enough datapoints to make an estimated guess about activity.
SU: 2019, 2018
Also, people have been thinking sites were dying for a long time.
This is from '10:
4
Q: Is Super User dying?

Thomas OwensThere are a number of exchanges that are stepping all over Super User: Web Applications, Electronic Gadgets (although rumor is that one isn't going to survive, but be replaced by more specific exchanges for Android combined with the Apple exchange), TeX, Unix & Linux, Apple are all in beta. There...

10 years later the site ain't dead yet and the user asking the question is a mod at Programmers.
 
9:53 PM
[ SmokeDetector | MS ] Bad keyword with email in body (57): 20.04 local repository not working for updates/installs by Acme Computer on askubuntu.com
 
^ That's an odd one.
 
fp- feedback received
 
@SmokeDetector icons-64x64@2.rar is hardly an e-mail address.
 
[ SmokeDetector | MS ] Link at beginning of answer (32): Где можно узнать "координаты" цвета? by Master_Sniffer on ru.stackoverflow.com
[ SmokeDetector | MS ] Misleading link (22): JS. Updating objects in an array (matching by value) by Kim Lopez on stackoverflow.com
fp- feedback received
 
10:23 PM
@Daniil Here's a random SEDE for Stack Overflow only
 
There's been no scan activity for 3 status pings. There may be a problem.
 
!!/commands
 
@NobodyNada I'm SmokeDetector, a bot that detects spam and offensive posts on the network and posts alerts to chat. A command list is available here.
 
Hmmm... Just in case:
!!/reboot
 
teward/Osiris: Goodbye, cruel world
 
10:24 PM
@Makyen darn, I wanted to check the queue status
 
[ SmokeDetector ] SmokeDetector started at rev bc83caa (SmokeDetector: Auto watch of topspying\.com by tripleee) (running on teward/Osiris, Python 3.6.9)
 
Maybe it still has something
 
Restart: API quota is 19983.
 
!!/queuestatus
 
codereview.stackexchange.com: 3
pt.stackoverflow.com: 5
tex.stackexchange.com: 3
ru.stackoverflow.com: 9
blender.stackexchange.com: 2
magento.stackexchange.com: 1
stats.stackexchange.com: 1
es.stackoverflow.com: 2
 
10:24 PM
@NobodyNada Ahhh... sorry about that.
 
@Makyen well, that's what I get for trying to edit a chat message and look up commands at the same time
I missed the editing deadline and didn't get to run the command :D
 
[ SmokeDetector | MS ] Mostly punctuation marks in answer, repeating characters in answer (116): КАК УДАЛИТЬ ВОПРОС? by pomidor on ru.stackoverflow.com
 
@NobodyNada @Daniil The rate of new questions leveled off around 2014 and has been declining since 2017 (the recent spike is not real; it's just the roomba)
@SmokeDetector naa- Google Transalte says it's "HOW TO REMOVE A QUESTION?"
 
Letting it sit and auto-reboot may have been the better choice. Although, it's fairly rare to go 3 minutes at this time of day/day of the week without any activity on SE.
 
user435118
10:38 PM
@NobodyNada It’s dying much faster than I thought
 
user435118
Seems like the whole word is dying to be honest
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): New pattern has been found in Prime Numbers? by Crazy Facts on math.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): So what exactly is RESERVE BATTERY LEVEL(IN %) in Dell ALIENWARE Laptop? by Strobe on superuser.com
 
10:58 PM
@SmokeDetector Well...that person's definitely come up with their own ideas about how computers work
Not to be confused with HORSE - CORN THEORY
 
@SmokeDetector naa- Borderline R/A, but contains some advice that at least appears to be relevant
 
fp- feedback received
 
11:45 PM
teward/Horus: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): My tensorflow-gpu install is not working on CNN's by brian samoukian on stackoverflow.com
fp- feedback received
[ SmokeDetector | MS ] Bad keyword in link text in body, body starts with title and ends in url, potentially bad keyword in body (168): english bulldog puppies for sale near me by bulldog breeders on stackoverflow.com
tpu- feedback received
 

« first day (2459 days earlier)      last day (1354 days later) »