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

00:00
!!/blacklist-number- +51-1705-0255(?#NO NorAm)
!!/blacklist-number- +34-912-158-867
!!/blacklist-number- +1-806-853-5070
@Makyen A normalized version, {{'5117050255'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +51-1705-0255 to determine which entries on the number lists match that pattern, which would tell you: Matched by +51-1705-0255(?#NO NorAm) on line 4699 of watched_numbers.txt: +51-1705-0255 found verbatim
@beibichunai Welcome to Charcoal HQ, is there a particular problem or query you had?
00:01
!!/unnotify 11540 diy.stackexchange.com
@Anerdw I will no longer ping you if I report a post on diy.stackexchange.com, in room 11540 on chat.stackexchange.com.
@Spevacus @Rob Well, there's actually a brief time when it's possible. MS only checks for the sites a user is a moderator on once every 24 hours, so for the period of time from becoming a moderator to when MS updates, it is possible for a moderator's flags to be used. The process to update a specific user can also be triggered manually by an admin. I've done that for Rob, so MS has been updated.
00:22
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad keyword in body (60): What's the story behind Wallet Recovery?‭ by Veronica Dunnigan‭ on bitcoin.SE
!!/blacklist-number 1 (541) 901 3390
@Spevacus A normalized version, {{'15419013390', '5419013390'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +1(541)901-3390 to determine which entries on the number lists match that pattern, which would tell you: Matched by 1 (541) 901 3390 on line 4490 of watched_numbers.txt: 15419013390 found normalized; 5419013390 found normalized
@Rob Your flag conditions were manually disabled by @SmokeDetector: Total accuracy must be >= 99.75%.
@Rob Your flag conditions were manually disabled by @SmokeDetector: Total accuracy must be >= 99.75%.
Rob
Rob
01:11
OK, everything fixed. Thanks again all. Thanks @Makyen
!!/approve 13090
!!/approve 13093
API quota rolled over with 94190 requests remaining. Current quota: 99999.
stackoverflow: 1894
math: 663
superuser: 189
physics: 165
mathoverflow.net: 150
electronics: 143
askubuntu: 137
ru.stackoverflow: 120
stats: 94
philosophy: 78
tex: 75
salesforce: 74
diy: 72
law: 72
unix: 69
es.stackoverflow: 64
serverfault: 63
gis: 63
ell: 57
judaism: 53
english: 52
blender: 51
pt.stackoverflow: 39
scifi: 38
politics: 37
ethereum: 37
mathematica: 36
worldbuilding: 34
gaming: 33
dba: 32
academia: 31
hermeneutics: 31
aviation: 30
vi: 25
codegolf: 25
wordpress: 23
apple: 23
puzzling: 22
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): How to complain on PhonePe app? How to complain on PhonePe app?‭ by Ruvi Kumar‭ on askubuntu.com
!!/blacklist-number 9263951361(?#IS NorAm)
@Spevacus That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 926-395-1361 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 926-395-1361. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (73): How to complain on PhonePe app? How to complain on PhonePe app?‭ by Ruvi Kumar‭ on askubuntu.com
I... Don't think these are north american numbers. Someone may wish to do the opposite (No NorAm), or ask me to.
!!/bisect Delete this Post
@micsthepick Matched by delete[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>) on line 30282 of watched_keywords.txt
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad keyword in answer (96): Log rotation with compression?‭ by Anik Hassan‭ on superuser.com
tpu- feedback received on [MS] Log rotation with compression?‭
01:54
[ SmokeDetector | MS ] Bad keyword in body, phone number detected in body, potentially bad keyword in body, scam aimed at customers in body (266): How to change passanger name on Delta Airlines?‭ by Prashant Sharma‭ on apple.SE
!!/watch-number 1-877-776-1237
02:06
anyone have a tool for using a json export from MS to do some regex tuning?
I'd like to determine if changing the above to (?<!I'll\s|I\s|will\s)delete[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>) or something like would be beneficial
(of course that specific one isn't great, and I'm too frustrated with the slow speed of MS search)
i'm trying to write one right now lol
busy with other stuff so it might take a long time though. like weeks.
[ SmokeDetector | MS ] Blacklisted website in body (98): Who is the right writer?‭ by Rajeev kumar‭ on superuser.com
tpu- feedback received on [MS] Who is the right writer?‭
!!/watch- rajeeveducated\.blogspot\.com
@Anerdw The pattern is for a blogspot domain, but keeps the top level domain (TLD; e.g. .com). For Blogspot, we prefer the TLD to not be included in watchlist/blacklist entries. Append -force to the command word(s) if you really want to add the pattern you provided.
02:17
!!/watch- rajeeveducated
PR#13096 ("Anerdw: Watch rajeeveducated") opened by SmokeDetector
!!/watch rajeeveducated\.blogspot
@Anerdw We just drop the \.com in these.
!!/reject 13096 "Should have included \.blogspot"
02:18
@Anerdw Please provide an adequate reason for rejection that is at least 20 characters long. Use -force to ignore this requirement.
@Anerdw You self-closed pull request #13096.
am struggling to get notepad++ to run the above due to stack space
wait since when can you self-close PRs? nifty.
also probably will not be able to do what I want because of string encoding
Nice!
02:20
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (266): How can I complain to Ekart delivery?hhh‭ by Lalu Ansari‭ on stats.SE
My first, real, foray into Python nonsense. It was... Kinda fun, to be honest? I'm a bit of a C# snob (C snob?) and the syntax is kinda nice.
@Spevacus If you want to make it worse (better?), you can always try Bython
@Anerdw That's hilarious. I love it (and hate it)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Function for Cleaning Named Ranges from Excel ✏️‭ by JackyD‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): How can I stop my mobile nav hamburger menu from flashing?‭ by Hector Zeroni‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in title, potentially bad keyword in body, potentially bad keyword in title (100): How do I speak to a PhonePe executive?‭ by Kanahiya Kumar‭ on askubuntu.com
02:52
tpu- feedback received on [MS] How do I speak to a PhonePe executive?‭
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (73): How do I speak to a PhonePe executive?‭ by Kanahiya Kumar‭ on askubuntu.com
!!/blacklist-number- 09123815926
PR#13097 ("Fastnlight: Blacklist 09123815926") opened by SmokeDetector
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad keyword in answer, blacklisted user (162): How do I speak to a PhonePe executive?‭ by Kanahiya Kumar‭ on askubuntu.com
02:57
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.8): failure on eb7bb1a by SmokeDetector in the auto-blacklist-1725504827 branch for PR #13097
tpu- feedback received on [MS] How do I speak to a PhonePe executive?‭
@metasmoke fluke
@metasmoke [ SmokeDetector ] GitHub Action workflow build (3.12): failure on eb7bb1a by SmokeDetector in the auto-blacklist-1725504827 branch for PR #13097
Uh, did I somehow break the NS resolver?
!!/blacklist-number- +91)7003-682-511
Nah.
PR#13098 ("Fastnlight: Blacklist +91)7003-682-511") opened by SmokeDetector
02:59
!!/blacklist-number- +91)9883-7300-50
PR#13099 ("Fastnlight: Blacklist +91)9883-7300-50") opened by SmokeDetector
@micsthepick Performance on that will be improved by putting the look-behind after at least the first word, so delete(?<!I'll\sdelete)(?<!I\sdelete)(?<!will\sdelete)[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>).
@micsthepick The original delete[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>) is 203 Total / 76 TP (37.44% TP) / 92 FP / 25 NAA and took 26.7 s. Without optimization, it's 203 Total / 76 TP (37.44% TP) / 92 FP / 25 NAA and took 58.0 s.
@micsthepick Your proposed (?<!I'll\s|I\s|will\s)delete[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>) is 158 Total / 69 TP (43.67% TP) / 62 FP / 20 NAA and took 84.6 s. Because this does not start with a static character, the optimization that the bookmarklet linked below does can't be applied, so the non-optimized version of each of the following is also provided.
@micsthepick Putting the look-behind after the deletedelete(?<!I'll\sdelete)(?<!I\sdelete)(?<!will\sdelete)[\W_]*+this[\W_]*+post(?!(?:[^<]|<(?!\/?code>))*+<\/code>) is 158 Total / 69 TP (43.67% TP) / 62 FP / 20 NAA and took 37.0 s. Without optimization, it's 158 Total / 69 TP (43.67% TP) / 62 FP / 20 NAA and took 68.3 s.
@micsthepick If you're doing searches for blacklist and watchlist entries on MS, you may find the bookmarklets in Bookmarklets for searching MS for blacklisted expressions.
In particular, I use the bookmarklet here for searching for watch and keyword blacklist entries. When possible, that bookmarklet does some optimizations which notably reduce the time it takes to search for such entries (i.e., it puts the opening bookend in a lookbehind).
BTW: If you're doing a bunch of searches on MS, please only have at most two running at a time. Regex searches take significant compute resources. Having many running at the same time can slow things down for other people. By "running" it's from when you click "Search" or request the page with the search URL until you get a response.
Processing of the search does not stop if you close the tab while the search is running. If you close the tab, you won't know when it completes. So, if you make an error and request something that you don't actually want, leve the tab open until it actually finishes. I've had to do that many times.
!!/approve 13099
I'm comfortable to leaping to blacklist with this PhonePe (and related companies) nonsense. It's prolific enough, I think.
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 53d9e2a by SmokeDetector in the auto-blacklist-1725505154 branch
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on eb15e3f by SmokeDetector in the auto-blacklist-1725505178 branch
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on 53d9e2a by SmokeDetector in the auto-blacklist-1725505154 branch
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on eb15e3f by SmokeDetector in the auto-blacklist-1725505178 branch
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 49cf21e by SmokeDetector in the master branch
I recall a message from Makyen that (unless I'm not interpreting it correctly) gives us the all clear to go directly to blacklisting for these fake customer service numbers
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 6604b15 by SmokeDetector in the master branch
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on b517ca0 by SmokeDetector in the master branch
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on 6604b15 by SmokeDetector in the master branch
I'm not sure this qualifies as the "customer support" number spam wave, but it's definitely within what I would at this point consider to be a spam wave.
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on 49cf21e by SmokeDetector in the master branch
03:06
"How do I speak to phonepe" is asking for a customer support number
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on b517ca0 by SmokeDetector in the master branch
I guess this is a different wave than the one Makyen was referring to a while ago, but at this point, this specific case with phonepe and other companies is a wave
If these are the same folks their MO definitely changed a bit.
It's sufficiently different from the support number spam wave such that it's not the same definition, but, yes, there are enough of this one to call it a spam wave.
If it's the same people or not ¯\_(ツ)_/¯.
03:09
Looks like Makyen fixed the NS issue :)
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad keyword in body (99): How do MsgBoxes and GUIs work in autohotkey v2‭ by Lucas Hicken‭ on stackoverflow.com
[ SmokeDetector ] GitHub Actions: success on 6184381 by makyen in the master branch
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Lightest gauge strings for a 12-string acoustic?‭ by a deleted user on music.SE
[ SmokeDetector ] Blacklists reloaded at rev 6184381051 (Makyen: dctshosting.com NXDOMAIN) (running on teward/Cerberus)
@Makyen I haven't proposed anything yet :)
I'm simply poking around
why did i click that link. this is going to take another 84 seconds.
03:20
@Makyen preferably I'd do one search and export, and then from there I can do the required tweaking, and once I'm done run it again with proper benchmarking
@micsthepick Well, you proposed it as something that might be a possible proposal some time in the future. :)
heh, btw how are you calculating the search times?
@micsthepick Admins or developers have diagnostics showing page creation times, including what SQL queries are made and how long each of them took.
So, I'm cheating a bit, rather than using a stopwatch, which I used to do.
can you look at my two latest queries?
03:27
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to get money back from a wrong transaction in Google Pay?‭ by Hchd Jhjh‭ on askubuntu.com
(delete[\W_]*+this[\W_]*+post(?![\W_]*+if|[\W_]*+when|(?:[^<]|<(?!\/?code>))*+<\/code>) and the original query)
[ SmokeDetector | MS ] Bad keyword with email in answer, email in answer (164): How to claim funds in a multisig address from a money pool psbt?‭ by user157296‭ on bitcoin.SE
!!/report askubuntu.com/q/1525691 "Spam seed"
@Anerdw Post 1: Already recently reported [ MS ]
03:30
@Makyen or should I get out my stopwatch?
I see the original took 58.0 seconds according your message
@micsthepick Unfortunately, it looks like a stopwatch will be necessary, although the search may now be cached, so data, potentially,. Unfortunately, the admin/developer tool doesn't always work (randomly). It did not show a result for either an optimized or unoptimized attempt at the regex you provided. I can try again.
up to you, I have a physical stopwatch at hand, if that's easy
even if cached, we can do the original again and get a better comparison?
03:36
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Display a custom 3D model in a Mapbox map in Mobile Maps SDK‭ by Vishwajith Shettigar‭ on stackoverflow.com
@micsthepick Cached on the original was 217 ms.
hmm, that's not sounding very helpful
@Makyen I'll try the search again, and if it's <10 seconds I'll know something is up
@micsthepick Optimized: 47.4 s; non-optimized 62.8 s
waffles
@Makyen is there only a optimized or unoptimized version for the original that we know to be 58.0?
03:45
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (200): Phonepe wrong transaction refund‭ by Delep Sing‭ on askubuntu.com
[ SmokeDetector | MS ] Bad phone number in answer, potentially bad keyword in answer (101): Phonepe wrong transaction refund‭ by Delep Sing‭ on askubuntu.com
@micsthepick I'm not sure what you're asking. This message says the optimized original is 26.7 s and 58.0 s non-optimized.
I read only the rightmost part sorry!
@micsthepick Hmmm... I'm seeing an inconsistent 20.4 s when I re-ran this optimized just now, with a third attempt taking only milliseconds, so fully cached.
[ SmokeDetector | MS ] Pattern-matching website in answer, username similar to website in answer (150): Is there a site focused on digital tech innovation in healthcare?‭ by Care Assure‭ on meta.SE
03:58
!!/watch careassure\.com\.au
[ SmokeDetector | MS ] Link at beginning of body, potentially bad keyword in body, potentially bad keyword in title (48): Java Burn™ | Official store‭ by Health‭ on meta.SE
tpu- feedback received on [MS] Java Burn™ | Official store‭
tpu- feedback received on [MS] Java Burn™ | Official store‭
tpu- feedback received on [MS] Phonepe wrong transaction refund‭
You'd think at some point they'd just give up
that was up for like five seconds
04:05
They're delaying my bedtime by seconds, I tell you. Seconds!
Cow
Cow
@Spevacus rofl
@metasmoke deja vu there, I really thought I had seen "abundantiot" show up once in this context before
i was looking through unreviewed posts in MS search
btw i suppose it's possible that it was sneaky SEO? but it was self-deleted so i doubt it
[ SmokeDetector | MS ] Potentially bad keyword in body (1): KOL Lazada - Cách đăng ký nhanh và hiệu quả‭ by Antony Stein‭ on stackoverflow.com
!!/watch chatgptgratuit
!!/watch- chatgptgratuit\.org
!!/watch-number- 33 4 60892929
@SmokeDetector k
@Makyen 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.
@Makyen is it bad to leave out the org tld in this case?
!!/unwatch- chatgptgratuit
!!/watch- chatgptgratuit\.org
!!/watch- chatgptgratuit(?!\.org)
04:28
(I don't speak french)
actually, minor nit, and maybe this is just How We Do It and I'm wrong: chatgptgratuit(?!\.org) - should that be chatgptgratuit\.(?!org)
I mean, what you've done is essentially equivalent to what I did, so there's that
(minus the distinction between which rule so yeah)
I may have just rubber ducked my way into understanding what you just did.
@micsthepick Because it was actually used separately, we do want a watch that catches "chatgptgratuit", but we also want a watch that catches the domain. We have them separate, because they will, potentially, end up separate on the blacklisted keywords and blacklisted websites lists, but we don't want them detecting the same text.
yeah. I guess that figures
I need to catch up on the guidelines
Basically, it's easier to have them separate now, than have to separate them in the potential future when one or both need to move to the blacklists.
04:34
!!/coffee
@micsthepick brews a cup of affogato for @micsthepick
naa feedback received on [MS] Why did she choose O6G?‭
@micsthepick From an analysis POV, I'd expect this to be a bit faster than the baseline, as the short lookaheads will be evaluated first, eliminating some potential matches, prior to the longer, more computationally intensive "not in code" lookahead.
noice
regex is hard to analyse, even if you know it well.
@Cow metasmoke.erwaysoftware.com/review/posts/358023 - I'm clearing my queue of questions relating to puzzling.stackexchange.com - can I know a bit about why you marked as FP (not saying you were wrong)?
hmm, one one hand the current revision is fine, but technically this one is actually a bit spammy because it's not yet disclosed.
what was the rule: TP means that we'd want Smokey to detect a post if it was found in the state as published to MS?
Cow
Cow
04:51
@micsthepick sorry I dont remember 5 months back, but if you think it's not fp, then you should leave your take on it :)
Cow
Cow
05:04
@micsthepick yeah I dont think that is tp, I see no affiliation with the linked site
> If SmokeDetector was implemented as a system-level block, would we want to catch this type of activity?
@Cow although in the current revision, there's notice of affiliation
that's the actual question - and funnily enough my asnwer would be yes, we want people to catch that they have not expressed their affiliation and be told kindly.
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): How can I copmlain to Zomato?jhh‭ by Rani Khan‭ on stackoverflow.com
Cow
Cow
@lyxal oh did not check the site itself
05:06
tpu- feedback received on [MS] How can I copmlain to Zomato?jhh‭
I find myself often checking the actual site in cases like this where it's still up
Cow
Cow
sdc blacklist-number- 0760-2220-886
PR#13101 ("Cow: Blacklist 0760-2220-886") opened by SmokeDetector
tp feedback received on [MS] An Alien Lands - where?‭
Cow
Cow
@lyxal ah but they have disclosed it
yeah, that's what I meant
Cow
Cow
05:08
oh
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (73): How can I copmlain to Zomato?jhh‭ by Rani Khan‭ on stackoverflow.com
Cow
Cow
but it's fp IMO
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body, +2 more (294): What are the key benefits of enrolling in a digital marketing course at IPCS Global Calicut?‭ by nikz‭ on stackoverflow.com
05:10
@Cow in hindsight, it's tp in its original state, but at the time, I probably would have gone false positive as it wasn't immediately obvious there was affiliation
Cow
Cow
I can delete my feedback I dont mind
there, it's gone
I think it was correct to fp at the time, but it's also correct to tp now that more information has come to light
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body, blacklisted user (172): What Are the Steps for Booking Group Travel with JetBlue?‭ by Gracy Luis‭ on stackoverflow.com
Cow
Cow
@SmokeDetector k
!!/watch- jetblue[\W_]*+group[\W_]*+travel
05:13
PR#13102 ("lyxal: Watch jetblue[\W_]*+group[\W_]*+travel") opened by SmokeDetector
!!/watch-number- +1(860) 934-0441
PR#13103 ("lyxal: Watch +1(860) 934-0441") opened by SmokeDetector
mfw phone hack
Cow
Cow
05:17
@SmokeDetector @Dragonrage I would like to order this user as KFC :D
extra crisp
hmm, did the total number of reviewable items just jump significantly in MS?
Cow
Cow
it jumps a bit up and down, just refresh and it'll be back to normal
how much do you consider as significant?
Cow
Cow
dunno why
05:24
@Cow oops. too crispy. its gone
Cow
Cow
@Dragonrage uh coal for the grill I guess :D
@Dragonrage I'd say it changed by an OOM (halved) but I might misremember.
when i refreshed, it changed by about 400, but i hadnt reloaded that specific page in awhile
ok, maybe the first digit changed, and that made me think it's changed by an OOM
05:30
@cocomac User is blacklisted (27169488 on stackoverflow.com).
hmm, the more specific a plaintext string is by length, paradoxically the slower it runs in MS...
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, potentially bad keyword in body, potentially bad keyword in title (296): How do I complain to a PhonePe app? Call 9201320481‭ by Rk Srma‭ on askubuntu.com
teward/Cerberus: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 05af6d3ab5 (SmokeDetector: Auto watch of chatgptgratuit(?!\.org) by Makyen) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 98752.
Makyen/EC2-linux: Executing automatic scheduled reboot.
ArtOfCode/TRINITY: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, mostly non-latin body, mostly non-latin title, phone number detected in title, +2 more (446): Finger 𝑳𝒐𝒂𝒏 App 𝑪𝒖𝒔𝒕𝒐𝒎𝒆𝒓.Care 𝑯𝒆𝒍𝒑𝒍𝒊𝒏𝒆 Number =+(91) 9861071954 //9652586172 call‭ by khanr kumawj‭ on askubuntu.com
[ SmokeDetector ] SmokeDetector started in standby mode at rev 839550c (SmokeDetector: Auto watch of ssoidraj\.com by Spevacus) (running on ArtOfCode/TRINITY)
@SmokeDetector k
Cow
Cow
sdc test +919861071954
> Numbers-only title, phone number detected in title
----------
Numbers-only title - Position 0-13: +919861071954
Phone number detected in title - Phone number: 919861071954
[ SmokeDetector | MS ] Link at end of body, potentially bad keyword in body (99): Importance of Off Page SEO?‭ by Saad Khan‭ on meta.SE
05:48
tpu- feedback received on [MS] Importance of Off Page SEO?‭
Cow
Cow
sdc watch-number- 923285003226
PR#13104 ("Cow: Watch 923285003226") opened by SmokeDetector
!!/approve- 13104
naa feedback received on [MS] Block of characters with no spaces‭
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)
05:54
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body (144): How to Apply for a Dubai Visa as a Tajikistan Citizen: A Complete Guide‭ by Dubai E Visa Online‭ on travel.SE
[ SmokeDetector | MS ] Blacklisted website in answer, username similar to website in answer, blacklisted user (239): How to Apply for a Dubai Visa as a Tajikistan Citizen: A Complete Guide‭ by Dubai E Visa Online‭ on travel.SE
Cow
Cow
sdc blacklist-username- (?-i:^Dubai E Visa Online$)
PR#13105 ("Cow: Blacklist (?-i:^Dubai E Visa Online$)") opened by SmokeDetector
Cow
Cow
05:56
@SmokeDetector k
[ SmokeDetector | MS ] Link at end of answer, non-latin link in answer, potentially bad ns for domain in answer (139): Asking again on how to raise my living room floor‭ by 먹튀검증‭ on diy.SE
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body, blacklisted user (172): How to Make Group Travel Bookings with JetBlue Airlines?‭ by Gracy Luis‭ on superuser.com

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