« first day (3949 days earlier)      last day (170 days later) » 

[ SmokeDetector | MS ] Potentially bad keyword in answer (1): The variance of the weighted median and optimal weights ✏️‭ by a deleted user on stats.SE
17:15
[ SmokeDetector | MS ] Potentially bad keyword in body (1): problema para mudar o tamanho da caixa de input‭ by JOAO PEDRO MATARELLI‭ on stackoverflow.com
17:31
@metasmoke Well that's a lot of exclusions. Nice work Makyen.
Thanks.
ArtOfCode/TRINITY: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev 839550c612 (SmokeDetector: Auto watch of ssoidraj\.com by Spevacus) (running on ArtOfCode/TRINITY)
Cow
Cow
:o
@Makyen omg that's amazing!
Thanks :)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Engine sounds worrying me after oil issues‭ by John Waiton‭ on mechanics.SE
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body (95): Most helpful content‭ by Hakim Muhammed‭ on stackoverflow.com
18:04
tpu- feedback received on [MS] Most helpful content‭
18:19
[ SmokeDetector | MS ] Phone number detected in body (99): ¿Cómo llamar al teléfono 24 horas de Copa Airlines?‭ by john dynamics‭ on travel.SE
!!/watch-number- +1-844-499-2095
PR#13177 ("Fastnlight: Watch +1-844-499-2095") opened by SmokeDetector
Cow
Cow
sdc blacklist-number- +1-844-499-2095
PR#13178 ("Cow: Blacklist +1-844-499-2095") opened by SmokeDetector
18:19
Actually, that should be blacklisted
(ninja'd by Cow)
!!/close-force- 13177
!!/approve 13178
Cow
Cow
ah
sorry :)
@Fastnlight try self-closing it?
Ninja'd :)
Cow
Cow
18:20
sdc blacklist-number- 1-800-359-2672
the other one
PR#13179 ("Cow: Blacklist 1-800-359-2672") opened by SmokeDetector
!!/approve 13179
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Apktool decompiles fine but can't recompile‭ by Pixel‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body, repeating characters in body (56): Does anyone have/know where I can find com.google.code.gson:gson:1.8.9‭ by Plasmacita‭ on stackoverflow.com
19:21
fp feedback received on [MS] Sistema de banimento PHP‭
[ SmokeDetector | MS ] Potentially bad keyword in body (1): SQL to JSON Need Bracket for Array that can have multiple rows‭ by Kyle‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Does Allah create daughters when happy? ✏️‭ by A K‭ on islam.SE
19:53
20:11
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How can I fix this node.js error when running Telegram bot?‭ by doyen‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ns for domain in body (2): Current Sensor Terminal Wiring ✏️‭ by paulgill28‭ on electronics.SE
20:47
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Banner de Rolagem Vertical‭ by Thiago Meirelles‭ on pt.stackoverflow.com
21:01
[ SmokeDetector | MS ] Bad phone number in body (100): El Telefono British Airways Chile !+56!‭ by Abhishek Kumar‭ on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword with email in body, bad phone number in body, bad phone number in title, pattern-matching email in body, +2 more (516): ░J░O░H░A░N░N░E░S░B░U░R░G░+27715451704░jOINILLUMINATI OPEN YOUR INVITATION TO THE WORLD",‭ by johny gava‭ on stackoverflow.com
how do those guys make their living - is it just phishing?
Side hustle, maybe. I was curious, so I googled the "Illuminati scam", basically bitdefender.com/blog/hotforsecurity/…
I guess all it takes is one person falling for it and losing their identity/money/etc. for the effort to be worth it.
Then again, having formerly dipped my feet into an MLM (and getting out), I know some people do make a living doing this, usually off the backs of others.
21:50
Oh man. My fiance's sister got sucked in one time. She started explaining the product she was selling, and I cut her off and asked "So it's a pyramid scheme, right?" and she explained "Well, no, not exactly. You see, I work side-along to my supplier who I report to" and I literally took a piece of paper and did the pyramid drawing. She came to her senses a few days later.
The usual excuse from the more experienced ones is, "Well, your boss earns more than you do, right? So it's the same thing."
I'm tempted to go back in and record every motivational meeting.
Oh, also once, they sent me a motivational audio file called, "There's something wrong with my brain," in which they literally said, "Brainwashing is good."
Well, obviously! Gotta wash away the wrongness!
Man, I wish I could go back and find that, but it's locked behind a authentication wall that I no longer have.
@Spevacus You joke, but that's how they spun it.
21:54
Sheesh
are smokey's regexes ignore-case by default?
It's a thousand little "micro-arguments" that drive a wedge between you and your friends and family.
Suuuuper culty
100% TP rate: reward[\W_]*+(?:of[\W_]*+)?(?:one[\W_]*+|a[\W_]*+)?million[\W_]*+dollars
@micsthepick Yes.
21:57
should I watch it? :^)
That type of spam is already picked up by a boatload of checks already, so I think it would be a bit of a wasted effort in this case.
@SmokeDetector fp-
22:14
@micsthepick Unless you care about the order of those short words, I'd consider reward[\W_]*+(?:(?:of|one|1|a)[\W_]*+)*+million[\W_]*+dollars as an alternative. It's not necessarily better, but I often find that type of formulation more convenient.
@Makyen [Note: in this case it's fine for the group quantifier to be possessive (?:)*+, but it would need to not be possessive if what was being looked for potentially overlapped the next portion of the regex. For example, adding "mi", which is the start of "million", and keeping it possessive, reward[\W_]*+(?:(?:of|one|1|a|mi)[\W_]*+)*+million[\W_]*+dollars, would result in it almost never matching, because the "mi" in the tested text would almost always already be consumed and never be available to match the "million", unless the text was "mi million", "mimillion", or similar.]
@micsthepick I'm not against it, but @Spevacus does have a point that the examples we have of that wording all already have a high weight. It would be a judgement call as to if you think that it might reasonably catch something that's not covered, yet.
teward/Cerberus: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ff38b48c20 (SmokeDetector: Merge pull request #13179 from Charcoal-SE/auto-blacklist-1725906057) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 90187.
@Makyen was kind of interested if anyone knew of a regex that was like it already
(I)
22:32
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (40): Где и как написать виджет для faceit.com для обс‭ by Yevhenii Turchak‭ on ru.stackoverflow.com
> Now, we know we urged users to never reply to such requests and immediately delete the messages, but, as curious professionals with a duty to inform, we figured we should try it ourselves. (Again, don’t try this at home)
of course...
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer (2): Damaged Shower Floor- Is it just a matter of replacing the tile or more?‭ by Joey McColm‭ on diy.SE
> The form required us to provide personally identifiable information that could allow the scammers to conduct identity theft crimes, this includes full name, date of birth, address, phone number, occupation, money worth, email address, marital status, age and a current photo.
not surprised one bit.
[ SmokeDetector | MS ] Link at beginning of answer (38): Distributed memory table in Clickhouse‭ by Vipin Gyanchandani‭ on stackoverflow.com
22:41
!!/watch- heliotile\.ca
[ SmokeDetector ] Blacklists reloaded at rev c77e10b690 (SmokeDetector: Auto watch of heliotile\.ca by Makyen) (running on teward/Cerberus)
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad keyword in body, potentially bad keyword in title, potentially problematic ns configuration in body (62): TRUST BITCOIN/CRYPTO RECOVERY EXPERT / VIRTUAL FUNDS RESURRECTION‭ by Daniel Hugh‭ on meta.SE
*.seodns.one - should watch or blacklist this ns?
22:59
PR#13180 ("Watch NS seodns.one.") opened by micsthepick
@micsthepick @tripleee handles almost all of the NS watching/blacklisting. Thus, they will be the one most able to tell you the criteria they have been using. In general, we put things on the appropriate watchlist for a while prior to blacklisting. This allows us to get better data as to if it's something that exists in FP posts, as the data on MS is heavily weighted towards TP posts, by orders of magnitude.
tis but a draft
Accidentally hit the Request button for a review from tripleee :P
hopefully it saves some time for tripleee, otherwise it's my time that I just wasted - and I learnt a thing or too anyways
[ SmokeDetector ] GitHub Actions: success on f1c9fc4 by micsthepick in the patch-3 branch
23:32
ArtOfCode/TRINITY: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev 839550c612 (SmokeDetector: Auto watch of ssoidraj\.com by Spevacus) (running on ArtOfCode/TRINITY)
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body (2): injection molding services‭ by Firstmold‭ on pt.stackoverflow.com
tpu- feedback received on [MS] injection molding services‭
23:55
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Edit the "New Contact" page‭ by Brian Lewis‭ on salesforce.SE
fp- feedback received on [MS] Edit the "New Contact" page‭
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)

« first day (3949 days earlier)      last day (170 days later) »