« first day (3910 days earlier)      last day (208 days later) » 

18:00
@SmokeDetector Undisclosed affiliation - afreetools.com/about-us
"I’m Rajshree Afre., a Web Specialist & Owner of aFreeTools"
Man, you beat me to it (ninja'd)
Cow
Cow
cannot load MS right now
@SmokeDetector k UA
@Cow Same
I think we crashed MS
Cow
Cow
we broke it
everyone looking at conditions
@SmokeDetector k
@Cow There's a lot of terminology for how Smokey works, so I'll try and give a big summary: Each post that's reported by SmokeDetector has a series of reasons why it was reported. Each of these reasons can be looked at in Metasmoke, and each of them have an associated weight. Weight is the rough approximation of how severe a given reason is for a post to be reported. Some reasons (such as blacklist reasons) have a higher weight because they're very frequently found in true-positive reports. The weight of all reasons a post was reported for is combined to assign a total weight to the report, and that weight is used to determine whether it should be autoflagged.
Cow
Cow
18:03
@Spevacus thanks, that makes sense to me
I'm going to stick with 1 simple condition: minimum weight: 200, 1 rep, ≥ 1 reason, all sites
!!/ms-status
@Fastnlight metasmoke is up. Current failure count: 1 (teward/Cerberus)
yup, even SD is having issues
Oop, looks like MS is back up
Does the accuracy have to be at least 99.75% in total, or each reason needs an accuracy of 99.75%?
18:05
@Fastnlight Your flagging conditions need to total out to be at least 99.75% accurate.
Thanks
@Fastnlight happened to me too...
That's ideal, I think, but I'm not sure.
Cow
Cow
whats a fast speedtest server in the US?
Thats why my conditions got disabled. They were individually above the limit, but together were below
18:10
!!/watch- afreetools\.com
@Cow speed.cloudflare.com is nice, or use a stolen borrowed speedtest custom like this one
@Starship It shouldn't matter. Manually-reported posts aren't autoflagged.
18:11
Ah, I see you're intent on editing your message more
!!/watch- personalisedhoodiesuk\.co\.uk
@NisseEngström That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
!!/watch mantracoach\.org
Cow
Cow
@Fastnlight fast download, not so fast upload for some reason
18:12
@Spevacus Oh, why?
Download is usually the more important one, unless you are the server host
However, both numbers are larger than mine
I got 300 down, 10 up
Cow
Cow
I got fiber 1 Gbit up and down
@Starship Because autoflags are meant to be performed autonomously. If they were able to be triggered manually by a user, it could just be considered sock-puppeteering.
18:14
[2024-08-01T18:14:42 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1578.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-01T18:15:49 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 66.4 seconds after connection; No heartbeats have been received on the current WebSocket.
tp feedback received on [MS] Podcast download possible?‭
Cow
Cow
@Fastnlight when I test vs a local Danish host provider
@Spevacus after preview it says: 99.536%
I used your first model
164 - 101 - 3
all sites though
should I remove SO?
Yep! Exclude SO.
Cow
Cow
roger that
tp feedback received on [MS] Can code dream?‭
Then you can make a condition just for SO that's more restrictive
Cow
Cow
18:21
nice thanks
good idea
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, pattern-matching email in answer, potentially bad keyword in answer (273): Program for Lucky Numbers (4, 7, 44, 47, 74, 77, 444, ...)‭ by Gavin Walton‭ on stackoverflow.com
Can someone watch this? www.stabilizertech.com from this post: meta.stackexchange.com/a/394478/323179
!!/watch- stabilizertech\.com
18:28
PR#12428 ("Fastnlight: Watch stabilizertech\.com") opened by SmokeDetector
@Spevacus my idea was that it couldn't be enough to trigger an autoflag on it's own, but in comvination with something else...
!!/approve 12428
!!/test odungaspelltemple
18:31
fp feedback received on [MS] Program MCU with ATTINY‭
> Bad keyword in body, bad keyword in title, bad keyword in username, numbers-only title, phone number detected in title, potentially bad keyword in body, potentially bad keyword in title
----------
Bad keyword in body - Position 1-14: 2348167159012
Bad keyword in title - Position 1-14: 2348167159012
Bad keyword in username - Position 1-14: 2348167159012
Numbers-only title - Position 0-14: +2348167159012
Phone number detected in title - Phone number: 2348167159012
Potentially bad keyword in body - +2348167159012 found verbatim
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on a92a654 by SmokeDetector in the auto-blacklist-1722536888 branch
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 0-17: odungaspelltemple
Potentially bad keyword in title - Position 0-17: odungaspelltemple
Potentially bad keyword in username - Position 0-17: odungaspelltemple
[2024-08-01T18:32:53 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1024.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-01T18:32:58 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4.9 seconds after connection; No heartbeats have been received on the current WebSocket.
!!/blacklist-keyword- bodungaspelltemple
PR#12429 ("Fastnlight: Blacklist bodungaspelltemple") opened by SmokeDetector
^^^ 6/0/0
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): What kind of a sensor does a arcade punch (boxing) machine have?‭ by StrikeResearch‭ on electronics.SE
18:36
fp feedback received on [MS] MP3 PLAYER buttons not working‭
[2024-08-01T18:37:05 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 246.5 seconds after connection; No heartbeats have been received on the current WebSocket.
@SmokeDetector tpu-
!!/watch- powerkube\.tech
@SmokeDetector tpu- Doesn't seem to be a coherent response to anything on the page.
18:39
@Fastnlight User is not blacklisted (22419228 on stackoverflow.com).
[2024-08-01T18:45:40 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 515.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector ] GitHub Actions: success on db7798c by gparyani in the patch-2 branch
18:54
[ SmokeDetector | MS ] Link at beginning of answer (38): Upgraded RDS Postgres and did not know DMS was not supported‭ by Farida‭ on stackoverflow.com
[2024-08-01T18:59:09 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 808.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-01T19:06:34 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 445.0 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Lattice QCD $SU(3)$ Pseudo Heat Bath Algorithm in Practice‭ by ThatMadBoffin‭ on physics.SE
[2024-08-01T19:08:25 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 111.0 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Url in title, potentially bad keyword in body, potentially bad keyword in title (96): Is this telegram link safe "t.me/sdasda868"?‭ by Mick‭ on security.SE
[2024-08-01T19:18:20 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 594.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body (121): How to manually import FacSet pricing file ✏️‭ by Tatiane Junia‭ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body, mostly punctuation marks in title (156): ... errro....... errro ✏️‭ by Tatiane Junia‭ on stackoverflow.com
19:28
sd 2v
@Makyen Can github.com/Charcoal-SE/SmokeDetector/pull/10018 be merged now that it's been tested?
@Fastnlight What searches did you do to get 6 TP here? I did metasmoke.erwaysoftware.com/… and metasmoke.erwaysoftware.com/… and got 0.
Huh, now it's showing zero
probably a caching issue
Cow
Cow
roflmao
Cow
Cow
ROFL
who made that omfg hahaha
There's more funny sites
Cow
Cow
I have no doubt
Cow
Cow
19:38
I love the internet
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Uncaught mysqli_sql_exception: You have an error in your SQL syntax;‭ by user378015‭ on es.stackoverflow.com
@Makyen sure, sounds good. I can chat with you about it when you have some free time if you like to explain what i was trying to do and why. either here or another chat room. ill be around most of the day
Cow
Cow
free time
I hope you have a few years :D
j/k
Cow
Cow
19:45
true
doesmakyenhavefreetime.com
should register that :D
makyentodolist.com should return HTTP error 413
Cow
Cow
ROFLMAO
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer (2): Will quick pickling using lactic acid instead of vinegar produce results more similar to lacto-fermented ones?‭ by ubu walker‭ on cooking.SE
Cow
Cow
@SmokeDetector f
19:48
now to figure out how to add a named capture group to my regex
well, actually 2 of them
(?<name>regex)
put the name in arrow brackets
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Maatwebsite Excel with Laravel 9 and PHP 8‭ by RIDWAN ADIO‭ on stackoverflow.com
eg: (?<myGroup>my[\W_]*+regex)
@Fastnlight ok, think i got that. then how do i reference the named capture group. is it \<myGroup>
19:53
yup
Actually, I think they are assigned numerical IDs
Network outage fixed, but doing the actual migration from VMware to Proxmox now for my sanity. Metasmoke DNS still impacted.
2
Cow
Cow
nooo
it's upstream from me so
ISP has to fix it
Cow
Cow
:(
@Fastnlight oh, apparently \k<myGroup> works.
why? no clue
19:57
Yup, here's a quick demo: regex101.com/r/KtMHfT/1
@Cow this is why i've been moving things away from my local network and to remote systems
also trying to save on some power usage costs heh
my systems suck too much power
Cow
Cow
understandable
power is expensive
ye with my rigs and my AC in this heatwave we're talking like $300+
because A/C is more power hungry than my rigs
Cow
Cow
damn
[2024-08-01T19:58:55 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2435.4 seconds after connection; No heartbeats have been received on the current WebSocket.
19:59
@Fastnlight note that you can't use numbered capture groups in SD, as all regexes in a given rule are chained together, so you can't know what number it would be
for the same reason, named capture groups need to be uniquely named
Good to know. Thanks
@RyanM guess i can use a GUID
though not being able to start with a number does limit the amount of available GUIDs a little bit
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if there are any operational notifications from Thomas Ward, which are usually pinned in the sidebar. If Thoth is operational (i.e. use the !!/location command to see if it responds), then consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. @Makyen
Restart: API quota is 99982.
!!/location
20:10
!!/standby makyen
Makyen/EC2-linux is switching to standby
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if there are any operational notifications from Thomas Ward, which are usually pinned in the sidebar. If Thoth is operational (i.e. use the !!/location command to see if it responds), then consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. @Makyen
Restart: API quota is 99964.
[2024-08-01T20:12:08 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 792.7 seconds after connection; No heartbeats have been received on the current WebSocket.
Warning: teward/Cerberus: Last 11 connection(s) to metasmoke failed. Setting metasmoke status to down.
Cow
Cow
sdc location
Cow
Cow
sdc standby teward
teward/Cerberus is switching to standby
20:14
I thought we were supposed to standby makyen
Cow
Cow
see comment from Thomas
he has connection problems
[ SmokeDetector | MS ] Bad ip for hostname in title, potentially bad keyword in title (101): Pre Sale on pinksale.finance‭ by Sggght‭ on solana.SE
[2024-08-01T20:22:05 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 635.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-01T20:23:30 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 721.3 seconds after connection; 420.4 seconds after heartbeat.
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): @media toma mal la altura‭ by Martín‭ on es.stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): @media toma mal la altura de la página ✏️‭ by Martín‭ on es.stackoverflow.com
Warning: teward/Cerberus: Last 11 connection(s) to metasmoke failed. Setting metasmoke status to down.
[2024-08-01T20:25:50 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 224.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Uncaught mysqli_sql_exception: You have an error in your SQL syntax; ✏️‭ by user378015‭ on es.stackoverflow.com
[2024-08-01T20:30:31 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 420.4 seconds after connection; No heartbeats have been received on the current WebSocket.
Yeah; MS /was/ working for me when I ran that, but the situation has apparently changed.
For me, metasmoke continues to work
@SmokeDetector v
20:42
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body (2): Yimusanfendi: Redefining Fashion with a Unique Blend of Tradition and Modernity‭ by our time guest‭ on stackoverflow.com
!!/watch- clickhints\.co\.uk
Ok, so the PR did open, but MS didn't send its usual message, so I'll do it for it
PR#12430 ("Fastnlight: Watch clickhints\.co\.uk") opened by SmokeDetector
sdc approve 12430
@RyanM Merged pull request #12430.
hmmmmm, that's not exactly the message I expected...
sdc location
!!/pull
[ SmokeDetector ] SmokeDetector started at rev 231d6be692 (SmokeDetector: Auto watch of powerkube\.tech by Nisse Engström) (running on Makyen/EC2-linux, Python 3.11.3)
Restart: API quota is 99717.
that's...almost the right commit...
We are 2 commits behind
!!/pull
20:56
Does it need another pull?
Maybe it's waiting for circleci?
It just finished, i'll try another pull
!!/pull
!!/gitstatus
20:58
@RyanM No such command 'gitstatsu'.
On branch deploy
Your branch is up to date with 'origin/deploy'.

Untracked files:
(use "git add <file>..." to include in what will be committed)
chatcommunicate_no_SE.py
config.normal
pickles_2024-03-25-mixed-time-values/
pickles_backup/
pickles_backup_2023_06_01/
pickles_save_2024-03-24-queue_problems/
rooms_custom_no_commands.yml
rooms_custom_no_stackexchange.yml
rooms_custom_no_stackexchange2.yml

nothing added to commit but untracked files present (use "git add" to track)
Ah, it's on a different branch
I could create a PR to merge master into deploy...
But I bet there's a better way to do that
The issue is... yeah, deploy is 2 commits behind master
I am not sure how that is managed, normally.
Maybe we should run !!/pull-sync-hard?
According to the docs:
"For use when other methods of resolving git issues fail. Uses a series of git commands to --force both the master and deploy branches to be on the same commit as origin/master and origin/deploy (normally, origin is set to Charcoal-SE/SmokeDetector on GitHub). An alias, !!/pull-sync-hard-reboot, will automatically reboot the SmokeDetector instance after syncing both branches to the origin. If you don't have it automatically reboot, it's recommended that you !!/reboot after executing this command in order to start using the current version of the files."
!!/pull-sync-hard-reboot
@Fastnlight You don't have blacklist manager privileges, which are required to run this command.
[2024-08-01T21:07:27 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 722.5 seconds after connection; 420.4 seconds after heartbeat.
[ SmokeDetector | MS ] Bad keyword with email in answer, email in answer, potentially bad keyword in answer (165): Why would anyone sell a Bitcoin miner instead of just mining themselves?‭ by Hassan ali‭ on bitcoin.SE
21:10
!!/blacklist-number- +1 605-900-9588
!!/watch- oluwawa[\W_]*+son(?#@gmail.com)
PR#12432 ("Fastnlight: Watch oluwawa[\W_]*+son(?#@gmail.com)") opened by SmokeDetector
MS?
You're back?
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer (2): HP T620 thin client: bizarre boot failure‭ by Babstar‭ on superuser.com
@Fastnlight Are you intending to watch a specific email here, or a pattern more generally?
21:12
@RyanM The email
Did I do it wrong?
PR#12431 ("Fastnlight: Blacklist +1 605-900-9588") opened by SmokeDetector
generally I think we've watched unique-enough-to-be-sketchy emails in the format exact\.username(?:@example\.com)?, rather than using [\W_]*+
got it, feel free to reject that PR
or if you want to forcibly include the domain, you could just do exact\.username@example\.com
Note, however, that dots in gmail emails are optional.
i.e, adding a dot to your gmail is still the same email
21:15
john.doe == johndoe == jo.hn.doe
For that concern, you could do exact\.?username
!!/watch- oluwawa\.?son(?:@gmail\.com)?
shoot, I forgot the optional dot
@SmokeDetector v
Ok, bin 12432 and 12433 please
21:17
!!/reject 12432 "by author request"
@RyanM Closed pull request #12432.
!!/reject 12433 "by author request"
@RyanM Closed pull request #12433.
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)
What IP do y'all have for MS? I can't resolve it.
21:20
135.148.96.213
hmm, i assume i would use positive lookahead for ensuring an open paren is followed by a close paren with exactly 3 characters between them
[2024-08-01T21:21:07 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1540.8 seconds after connection; No heartbeats have been received on the current WebSocket.
@Dragonrage What about \(.{3}\)
@Fastnlight thanks, appreciated, now I can access it again :D
21:22
now to inevitably forget that I did this and be unable to access it when its IP changes someday
right, now that I can actually see MS searches...
!!/approve 12434
aaand the branches are in sync again, yay
@Fastnlight well, i want to have an optional open paren, but if there is an open paren, it must be followed by a close paren with 3 digits inbetween
You've heard of DNS-over-HTTPS, now get ready for DNS-over-Stack-Exchange-Chat.
21:25
DNS-over-GitHub-Gist
@Dragonrage Wouldn't that just be this? (?:\(\d{3}\))?
it sounds like you're just describing an optional group
@RyanM the linguistic challenge of writing that message in a way that unambiguously conveys that the trailing question mark is part of the pattern, not the sentence.
@RyanM i think that looks about like what i want, and is basically what i had gotten to, but doesnt seem to be working as i intend it to
[2024-08-01T21:32:43 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 696.1 seconds after connection; No heartbeats have been received on the current WebSocket.
21:34
What about something like this? (?:(?:\(\d{3}\))|(?!\())
Either you have the (123), or you don't have an open parenthesis at all
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Do I have to marry my rapist?‭ by Liana Othman‭ on islam.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Mastubation and ghusl‭ by yh2309‭ on islam.SE
fp- feedback received on [MS] Mastubation and ghusl‭
[2024-08-01T21:37:41 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 1814.4 seconds after connection; 420.4 seconds after heartbeat.
[ SmokeDetector | MS ] Potentially bad asn for hostname in title (1): arXiv CS.AI and CS.CL endorsement‭ by Iheb Gafsi‭ on academia.SE
[2024-08-01T21:44:42 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 420.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Luncheon meat detected (40): gaussian elimination algorithm python‭ by Lukasz Mozdzierz‭ on stackoverflow.com
21:47
fp- feedback received on [MS] gaussian elimination algorithm python‭
[2024-08-01T21:49:01 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 258.8 seconds after connection; No heartbeats have been received on the current WebSocket.
@Fastnlight that seems close, but is excluding a few matches for some reason. not sure if im placing it in the wrong spot see my workboard
[2024-08-01T21:50:35 UTC]: Makyen/EC2-linux: main SE WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 3310.5 seconds after connection; 7.2 seconds after heartbeat.
[2024-08-01T21:51:42 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 161.6 seconds after connection; No heartbeats have been received on the current WebSocket.
22:04
update: my infra is still broken. ISP just finished replacing the ONT but it's still out. Because it's bene out for a few hours I'm also taking the time to migrate my stuff to Proxmox so i'm not forced to use VMWare forever
2
so, slowly migrating my stuff over
copying easily migrated/imported VMs first, then having to hook the disk to the device directly to do direct data copy (painfully!)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Como fazer um "campo flutuante" em um site ✏️‭ by Mateus Pozzebon‭ on pt.stackoverflow.com
[2024-08-01T22:13:44 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 1322.1 seconds after connection; 420.6 seconds after heartbeat.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body, potentially problematic ns configuration in body (3): Is paying for COT code or IRS Code for withdrawing money a scam? ✏️‭ by Marie‭ on money.SE
22:23
@Dragonrage I'm trying to trace it with the debugger, but I think it's in the right spot
@Fastnlight i think it might need to go after the +## section, but it also needs to be in a place to check the duplicate number section as well? maybe i need to move the country code section to the front?
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how connect solana to web3modal‭ by Adebayo Anuoluwa‭ on ethereum.SE
@SmokeDetector why
@Fastnlight Potentially bad keyword in body - Position 63-75: Trust Wallet
@SmokeDetector f
22:48
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body, potentially bad keyword in title (96): useful crypto recovery info‭ by Felix Stella‭ on money.SE
tpu- feedback received on [MS] useful crypto recovery info‭
[2024-08-01T22:50:06 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4642.8 seconds after connection; No heartbeats have been received on the current WebSocket.
!!/watch- yimusanfendi
@Dragonrage A GUID isn't necessary. We don't have billions of named capture groups. Given that we have very few of them, just using a name that describes what you're doing should be fine, and self-documenting. The issue is when people choose to use quite generic names like "name", "foo", "x", etc. It's not all that hard to search through the entries to see if the name you choose is used, and/or use a prefix to the name that's more or less is something only you would use.
23:02
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): NPV acceptable performance of investment‭ by Root Groves‭ on economics.SE
@Makyen this is where im at currently with the regex. working close to how I want it to. currently 83 results on MS, 78 TP
[2024-08-01T23:05:19 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 3095.0 seconds after connection; 420.4 seconds after heartbeat.
!!/watch- babajuma02(?:@gmail\.com)?
@Dragonrage Your flag conditions were manually disabled by @SmokeDetector: Total accuracy must be >= 99.75%.
23:09
!!/blacklist-number-force- +2348167159012
[2024-08-01T23:09:43 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1176.5 seconds after connection; No heartbeats have been received on the current WebSocket.
@Makyen That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
[2024-08-01T23:11:43 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 120.8 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Convert JSON array of key/value pairs into values with a comma seperator using jq‭ by Rao Komar‭ on stackoverflow.com
[2024-08-01T23:23:35 UTC]: Makyen/EC2-linux: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 1095.9 seconds after connection; 495.0 seconds after heartbeat.
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to stream trades from Binance web socket API in Node.js?‭ by Yasar Arafath‭ on stackoverflow.com
23:58
[2024-08-01T23:58:30 UTC]: Makyen/EC2-linux: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2806.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Resource Estimation with Stim ✏️‭ by Melisa Ege‭ on quantumcomputing.SE

« first day (3910 days earlier)      last day (208 days later) »