« first day (3105 days earlier)      last day (715 days later) » 

1:00 PM
@SmokeDetector naa- that is...probably a typo
 
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in title, phone number detected in title, potentially bad keyword in title (287): ᵓOINbase 1-(855)-225-42o6 CoinBaSe *#SUPport NUMber ✏️‭ by ajdgdi1314‭ on stackoverflow.com
 
@RyanM Unless it's a euphemism for lazy programmers :-p
 
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in title, phone number detected in title, scam aimed at customers in title (386): Dial NORTON Technical [1847-(3O6)-9989] Support Phone Number‭ by fawidir‭ on stackoverflow.com
 
1:08 PM
@RyanM agreed, or on second thought, maybe they just wanted advice from a specific audience??
 
@JeffSchaller the gays are known for adding color to things...
This would be more apt if my avatar had its standard plumage :-p
 
New question coming to a site near you?!?
 
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (386): coinbase customer +1+855.225+(42-06) service number‭ by tyctpg2‭ on serverfault.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (383): Binance (Helpdesk) Number +l.844::424::l(275)+ customer-care-number‭ by carleeawj‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Question about Enigma's rotors turnover‭ by Damien‭ on crypto.SE
 
@SmokeDetector Video uploaded today, literally says "No views" which I've never even seen before.
 
@metasmoke @RyanM I saw "I have a full setup for " and figured that for disclosure (so NAA vs spam flag)
@RyanM literally never seen ...
 
ha.
 
1:25 PM
(the double irony of "literal" and "seen" combined with zero views)
 
@JeffSchaller yeaaaahhh maybe. They have a bit of a history, though.
 
back to my cave...
 
I'm sticking with "it's spammy"
but NAA's arguably not wrong
 
@RyanM I did hover over the "tp" option for a bit
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Blank page proxy-mode‭ by ga1935‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Emergency Landing Scenario Evaluation‭ by Ahsan‭ on aviation.SE (@Federico)
 
1:27 PM
fp feedback received on [MS] Blank page proxy-mode
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in title, phone number detected in title, potentially bad keyword in body (381): 1(712)*986*6680coinbase support number‭ by jacob1155‭ on stackoverflow.com
 
tpu- feedback received on [MS] 1(712)*986*6680coinbase support number
 
@SmokeDetector I wonder if we can tweak Ryan's "login" regex of login(?<=\w login)(?=</a>) so that it skips image "links"?
 
1:32 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Why does my .NET rest API return a list with extra childproperty instead of [..]?‭ by robert‭ on stackoverflow.com
 
erm, probably not worth it
fp text: <a href="https://i.stack.imgur.com/something.png" rel="nofollow noreferrer">Error after try login</a>
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Mapping Server Recommendation (Arcgis/Geoserver etc)‭ by blades‭ on softwarerecs.SE
 
stackoverflow.com/questions/72305621/… really long one.. may take smokey some time
reported
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in body, phone number detected in title, +3 more (658): Quickbooks Enterprise Support +1(808‒900‒3847) Helpline ✏️‭ by binixi7511‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in body, phone number detected in title, +3 more (658): Quickbooks Enterprise Support +1(808‒900‒3847) Helpline ✏️‭ by binixi7511‭ on stackoverflow.com
 
1:43 PM
sd 2k
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title (288): +1(712)-986-6680 coinbase customer support‭ by Austin Cedric‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): CentOS 7 to Windows, can list smb shares but cannot mount‭ by vindalooman‭ on superuser.com (@Ollie)
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Extend default MaterialUI components‭ by Artiom Shinkaruk‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in title, phone number detected in title, potentially bad keyword in body, scam aimed at customers in title (383): Quickbooks Enterprise Support +1(808‒900‒3847) telPhone Number Official ✏️‭ by vesexe4878‭ on stackoverflow.com
[ SmokeDetector | MS ] Mostly punctuation marks in answer (36): How to add toAlternatingCase custom method to String class in JavaScript?‭ by ekat‭ on stackoverflow.com
teward/Osiris: Executing automatic scheduled reboot.
 
[ SmokeDetector ] SmokeDetector started at rev 0987f1d79 (SmokeDetector: Auto watch of digitaloperate\.com by Makyen) (running on teward/Osiris, Python 3.8.10)
 
Restart: API quota is 23426.
[ SmokeDetector | MS ] Bad keyword in body (94): Escaped characters appearing when appending to HTML element‭ by brondibur‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +2 more (482): Coinbase Support number 1833(543)23`02 Coinbase customer Wallet Support‭ by wayolak746‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, potentially bad keyword in body (295): coinbase_customer_care_ number (833) 5432-302_support_phone_number_usa‭ by latec63633‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body (94): optionMenu does not appear in window tkinter‭ by joobs‭ on stackoverflow.com
 
stackoverflow.com/a/72305784/4826457 link only?.. (Cant find affiliation)
 
@SurajRao yeah, think so. Couldn't find any either.
 
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 4dd95f541 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.8.5)
 
2:08 PM
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (383): Uphold_Support_1 (888) 89O-2621 Phone_Number || 103 Charles St, New York, NY 10014‭ by upholdservicenumbeoi‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Duplicate Meta Tags Website error‭ by RossWerner‭ on webmasters.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how do I fix npm install failing mac - newly installed node & npm‭ by Simon Hall‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (289): Uphold_Support_Number 1 (888) 89O-2621 || 398 Broome St, New York, NY 10013‭ by askservicenumber‭ on stackoverflow.com
 
2:16 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): How to force npm to use different node-gyp version when installing packages?‭ by Shirin Kaul‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (289): Uphold Customer_Support_Number 1 (888) 89O-2621 || 425 Grand St Suite 1, New York, NY 10002‭ by customerservicennumber‭ on stackoverflow.com
 
2:32 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how do i add this codepen as a background for my html page?‭ by turbo‭ on stackoverflow.com
 
sd why
 
@richardec [:61168961] Potentially bad keyword in body - Position 643-660: depositphotos.com
 
2:43 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): WPF - Can't add Listbox Item to Listbox (Beginner)‭ by JustinThns‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Link at beginning of answer (35): Can we use ObjectiveC and Swift code together in Flutter?‭ by Sky‭ on stackoverflow.com
 
2:59 PM
[ SmokeDetector | MS ] Username similar to website in answer (68): Change animated wait pointer for a static one - Ubuntu MATE‭ by NoMachine‭ on askubuntu.com
 
3 hours ago, by tripleee
@SmokeDetector still up (MS)
 
@tripleee Gone.
 
finally! thanks
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Animated footer in React‭ by Tanvi Patel‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad phone number in title, phone number detected in title (188): Pythonquiry_QUICKBOOKS_ DESKTOP_ SUPPORT_+ 1-(808)-400 1842_Enterprice_Number‭ by Linus Scott‭ on stackoverflow.com
 
3:13 PM
[ SmokeDetector | MS ] Bad phone number in title, phone number detected in title, potentially bad keyword in title (189): JavaScript_QUICKBOOKS_DESKTOP_SUPPORT + 1-{(808)-4oo 1842} NUMBER?‭ by Scott Stark‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): maps.googleapis.com/maps/api/mapsjs/gen_204?csp_test=true 403 (Forbidden)‭ by Alexis Mejias‭ on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted user (71): How to set background color for an icon button?‭ by Hammad Pervez‭ on stackoverflow.com
[ SmokeDetector | MS ] Link at end of answer (61): Redirect all WordPress posts and pages to homepage‭ by Suman kumar‭ on stackoverflow.com
 
3:26 PM
sdc watch- thevesign\.com
 
[ SmokeDetector ] Blacklists reloaded at rev a4e997431 (SmokeDetector: Auto watch of thevesign\.com by Ollie) (running on teward/Osiris)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +1 more (481): Best Guide on Coinbase Support @1 (( 858)) ((480 7417** Phone Number‭ by user19154861‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Link at end of answer (61): Strategy to migrate data from Oracle Database to MongoDB‭ by Ali fereidouni‭ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in answer, mostly punctuation marks in answer (124): ¿Cómo puedo unir 3 tablas SQL?‭ by el jijijija‭ on es.stackoverflow.com
 
@metasmoke fp instead of naa? @DavidP
 
3:42 PM
@SmokeDetector Can a Spanish speaker check if this is rude? Machine translation suggests it is with "don't say meriyein blowjobs".
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body (194): coinbase customer referral API?‭ by nccojy3333‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (480): Gem1ni1 CoinbASE (18(55)2254206) CusTomer Support NuMBER HELplinE ✏️‭ by nccojy3333‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Luncheon meat detected, no whitespace in answer (137): Not printing what I wrote inside the brackets in Python3‭ by mmm‭ on stackoverflow.com
 
3:51 PM
@SmokeDetector tpu- Even if this isn't rude (getting there, though) it looks very much like trolling.
 
4:03 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Android Detect Nearby Device (Covid-19 app)‭ by Adam Haynes‭ on stackoverflow.com
 
sdc watch everythingfor420\.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How i can "create my own API" for a website‭ by HGStyle‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): StableSwap invariant and price computation‭ by loyd.f‭ on ethereum.SE
 
4:12 PM
sd y
sd why
 
@richardec [:61169856] Potentially bad keyword in body - Position 573-583: gemini.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (480): COINBASE SUpport +1(833)-(543)-(2302) COINBASE CUSTOMER support number‭ by letefow852‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Allow Woocommerce shop manager to assign a role when creating a user‭ by koji‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): How to install magento 2.4 on ubuntu?‭ by Fatima Elmoussaoui‭ on stackoverflow.com
 
naa- feedback received on [MS] How to install magento 2.4 on ubuntu?
 
4:37 PM
sdc reject 6996 "From my POV this shouldn't be on the blacklist. At least half of the 12 hits in MS are actual FPs; some of the titles make them look like low-quality questions that use this pattern as filler text. We can keep it on the watchlist for now to catch the more troll-ish of the posts, then remove or blacklist when it becomes necessary."
 
@Ollie Closed pull request #6996.
 
sdc watch use[\W_]*+angle[\W_]*+brackets[\W_]*+to[\W_]*+force[\W_]*+linking
 
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add the pattern you entered.
 
ah.
 
[ SmokeDetector | MS ] Mostly punctuation marks in answer (36): Steam UI not launching after upgrading from Ubuntu 20.04 to 22.04‭ by Bushida‭ on askubuntu.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Chrome download window stuck at full screen‭ by Billy Gravel‭ on askubuntu.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): BUGS - Ubuntu 22.04 LTS‭ by Billy Gravel‭ on askubuntu.com
 
4:57 PM
naa- feedback received on [MS] BUGS - Ubuntu 22.04 LTS
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Помогите достать субтитры из видео на сайте‭ by Dendrit‭ on ru.stackoverflow.com (@Nicknamegoeshere)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to understand Bionomial Theroem and the Recursion Rule? ✏️‭ by Gojilla‭ on datascience.SE
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Different choices for each guild slash command using discord js‭ by p-destri‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Telegram bot API: get message id to forward it‭ by Said Assassi‭ on stackoverflow.com
 
5:37 PM
sdc blacklist-website- seplite\.com
 
[ SmokeDetector ] Blacklists reloaded at rev e19bf7adf (SmokeDetector: Auto blacklist of seplite\.com by Ollie) (running on teward/Osiris)
[ SmokeDetector | MS ] Few unique characters in answer (88): How to save Viewport3D as Image File? ✏️‭ by okoca‭ on stackoverflow.com
 
tp- feedback received on [MS] How to save Viewport3D as Image File?
 
[ SmokeDetector | MS ] Few unique characters in answer (88): How to crop image or rectangle ✏️‭ by okoca‭ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in answer (88): How to get multiple bitmaps from camera ✏️‭ by okoca‭ on stackoverflow.com
[ SmokeDetector | MS ] Pattern-matching website in answer (77): How to get multiple bitmaps from camera ✏️‭ by okoca‭ on stackoverflow.com
[ SmokeDetector | MS ] Link at end of answer (61): Do binance trades happen on the blockchain?‭ by frankiefab100‭ on ethereum.SE
 
@SmokeDetector tpu- Second time vandalizing after a mod rolled it back and left two comments. Might need a lock.
 
@Ollie user is now cooling off :)
 
5:44 PM
Oh, they've been suspended. Never mind.
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in body, phone number detected in title, scam aimed at customers in body, +1 more (563): HP Technical Support +1-847-3O6-9989 Number‭ by vojedi15‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in body, phone number detected in title, scam aimed at customers in body, +1 more (563): HP Tech Support +1847-3O6-9989 Number‭ by toyabo82‭ on stackoverflow.com
 
tpu- feedback received on [MS] HP Tech Support +1847-3O6-9989 Number
 
5:57 PM
sdc report stackoverflow.com/a/72308909/4657412 "Plagiarised from existing answer with helpful spam link added"
 
sdc watch- mytikkit\.com
 
[ SmokeDetector ] Blacklists reloaded at rev 351085705 (SmokeDetector: Auto watch of mytikkit\.com by Ollie) (running on teward/Osiris)
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Full Page loader‭ by Fangles‭ on stackoverflow.com
 
fp- feedback received on [MS] Full Page loader
 
6:10 PM
[ SmokeDetector | MS ] Blacklisted user (71): Youtube Unlimited Video‭ by cxvaron‭ on stackoverflow.com
[ SmokeDetector | MS ] Manually reported question (93): Security patch developers, what can go wrong?‭ by Kim Crawley‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad ns for domain in answer, link at end of answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (141): Opening .jar files with `pkexec` and using Desktop Entries to run commands‭ by Muhammad Javed‭ on askubuntu.com
 
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, repeating characters in body (257): Нужно чтобы сообщение сначала проверялось есть ли оно в канале, если есть то не отправлять, если нету - то отправить ✏️‭ by user500972‭ on ru.stackoverflow.com (@Nicknamegoeshere)
 
6:29 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): unable to import PySimpleGUI‭ by Levi Montgomery‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Is it possible to use a custom domain name for a sway.com site?‭ by Bruce‭ on webmasters.SE
 
sd why
 
@richardec [:61170851] Potentially bad keyword in answer - Position 169-183: ?utm_campaign=, Position 203-227: utm_source=stackexchange
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): How to redirect Thank you cloud page to URL based on response‭ by Liam‭ on salesforce.SE
 
6:45 PM
@SmokeDetector Hah, that's a clever thing to watch.
 
sdc watch cloak\.ist
 
fp- feedback received on [MS] unable to import PySimpleGUI
 
[ SmokeDetector | MS ] Link at beginning of answer (35): How to refresh the view when global variable change‭ by eghnacr‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +2 more (482): Coinbase support Number ++1 833┅5432302 Coinbase Phone Number Customer Support Number US‭ by giyipi8956‭ on stackoverflow.com
 
6:51 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body (2): How to copycat single post page from old theme to new one?‭ by noxext‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Few unique characters in answer, luncheon meat detected, no whitespace in answer, repeating characters in answer (304): How to Use data-image-src="../assets/images/about.jpg" in Vue‭ by Malcolm Parkinson Student‭ on stackoverflow.com
 
7:06 PM
 
sdc watch readme\.security
 
Makyen/EC2-linux: Executing automatic scheduled reboot.
API quota rolled over with 16745 requests remaining. Current quota: 39999.
stackoverflow: 9212
math: 2494
ru.stackoverflow: 987
es.stackoverflow: 599
physics: 575
electronics: 493
askubuntu: 484
superuser: 424
tex: 394
unix: 362
stats: 327
gis: 300
pt.stackoverflow: 268
salesforce: 267
serverfault: 238
blender: 233
ell: 213
mathoverflow.net: 200
codegolf: 193
ethereum: 177
english: 154
worldbuilding: 152
scifi: 152
mathematica: 142
datascience: 140
rpg: 137
dba: 135
diy: 134
apple: 118
wordpress: 117
workplace: 113
codereview: 112
cs: 95
academia: 91
magento: 82
politics: 82
 
7:13 PM
@richardec I thought you were using FIRE. If you're not aware of it, FIRE will display the why data, with some extra formatting, if you hover the mouse over the post title in the popup.
@SmokeDetector Not surprisingly, increasing the queue depth for SO resulted in about half the number of requests. However, there were numerous reports of SD not catching the initial version of the quickly edited support number spam.
!!/stats
 
@Makyen Posts scanned: 18847, Q(8975), A(9872); Scan time: 32491.57; Posts per second: 0.58; Grace period edits: 2119; Unchanged posts: 514992, Q(253639), A(261353); No post lock: 2820; Errors: 0; Max scan time: 114.17; Max scan time post: codereview.stackexchange.com/276691; Post processing lock: 9.17; Check unchanged: 17.74; Scan question: 27868.49; Scan answer: 4519.37
 
So I'm working on resolving this issue (tl;dr: If you attempt to watch a keyword that is already proposed in a PR via a watch or blacklist command, we want to send a warning and require -force to override, so that we don't end up having a hanging PR that's unapproved). One issue I'm running into is that this will end up adding about 3 more requests to the GitHub API.
The first is to grab currently-open PRs and check if they were created by a user in chat, the second is to verify the file changed would be the same if the user proposing the new watch/blacklist submitted it, and the third is to grab the diff to ensure the proposed patterns are the exact same (only want to stop a user if a proposed pattern, to the letter, is already proposed)
My question is: Is this an unacceptable number of API requests to add onto the watch process, or is that still okay? (i.e. is it alright to add those requests to an already high-request command?)
 
@Makyen ah, neat! I'll use that instead of sd why
 
(Oh, also, those requests are recursive: If there are multiple Watch-PRs open, it'll have to request the diffs for all of them if the files changed are the same)
 
@Spevacus If you're going to stop it and require -force, it would probably be better to run it through the same check, at the least the "there's already an entry catching this" one, that is/are used when the !!/watch and/or !!/blacklist-* command is issued.
 
7:26 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): React Native signed build crash immediately after open on device‭ by Marcos Oliveira‭ on stackoverflow.com
 
@Makyen I may not be reading this right but I'm not sure what you're saying. What I've currently done is added this check at the same stage as the normal "check for force" stage, alongside the normal "Check if already caught" stages. Is that what you're referring to? (Sorry I'm not sure I'm following you here)
 
@Spevacus Hmmm... I thought we were adding to the !!/approve process, where we're already interacting with the GitHub API and looking at a specific PR.
OTOH, I guess it would be possible to cache a bunch of that data, so you don't need to do most of the interactions past the first !!/watch/!!/blacklist-* after a reboot. You'd still need some, but you'd already know a significant amount of information. Admittedly, I haven't looked specifically at what the GitHub API is giving you.
 
Ah, I see.
@Makyen Currently I can't grab everything that I need in one API GET request. I can get a list of open PRs and check if they were created using the chat-command (SmokeDetector user is the author and it has a METASMOKE-BLACKLIST html comment in it) but I can't see what files were changed in the same call. I need to toss out another to ensure that, if the watch/blacklist goes through, they would be modifying the same file.
This is an afterthought check, I originally just had it check if any PRs currently propose the about-to-be-added pattern
 
I guess it wouldn't be unreasonable to do it in the !!/watch process, assuming it doesn't cost a bunch of time/network every single time someone does a !!/watch, as those are fairly common, whereas !!/approve is fairly rare.
 
Yeah. That's really my main concern. I'm unsure how much network load it would add to the watch lifecycle.
 
7:33 PM
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Mapbox with Flask not rendering certain images‭ by KCW‭ on stackoverflow.com
 
Really it should still be fairly quick. Most of the time, it would just be grabbing a json of the currently open PRs and quickly ignoring them since they weren't made using a chat command, and moving on.
 
@Spevacus Well.... you could just wing it and assume that the SD instance is the only one which would have created a PR since the first !!/watch/BL after booting. If you assume that, then the instance already knows what PRs are active and exactly what each change is (i.e. it created them, so it could just remember).
 
That's true. I'm relying too much on performing a request rather than the fact that these changes are made on the actual Smokey filesystem, it's not like I can't just look at those.
Er, well, the cache. W/e.
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Adjuntar archivo en script para enviar correo en Python ✏️‭ by Roberto Rivera‭ on es.stackoverflow.com
 
You could just get the PR data once at the first !!/watch/BL after boot (or put getting it in a Task in the boot process, if needed). Then just keep a record of what that instance submitted as PRs.
 
7:38 PM
That's probably a better way to go about it. Thanks for the idea :D
I think I'll shoot for that, then.
Do you have a recommendation of where to store that info in memory?
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How do I convert an user input only if its a certain variable?‭ by BigWillie‭ on stackoverflow.com
 
While it would be nice to have things checked at the !!/watch stage, the primary goal is to prevent the !!/approve breaking CI testing, which tends to cascade into breaking it on multiple commits prior to things being corrected.
 
Hm. You know, it may very well be simpler to resolve this at the !!/approve stage. My original goal was to ensure PR submitters didn't get their potentially-good PRs overlooked, but the change is more about ensuring things aren't broken than ensuring PRs get looked at.
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): meta tags errors in sites audit‭ by RossWerner‭ on stackoverflow.com
 
7:44 PM
@Spevacus That's going to depend on where you're accessing it. In general, it will be used in chatcommands.py, but it may need to be an entry in GlobalVars. You will need a threading.Lock() for all accesses to whatever store you use. While you can store the data to disk, initially it doesn't seem like something where it costs all that much to re-retrieve the data from GitHub upon reboot.
@Spevacus Yes, ideally, good PRs wouldn't be usurped by someone else entering something. But, the primary goal is to not have !!/approve break things.
 
Roger. I'll probably switch focus to performing an "already caught" detection at the !!/approve stage. It'd be less changes overall and I might get the chance to refactor the portion that checks if a pattern is already covered in do_blacklist.
The difficulty, now, appears to be ensuring I don't break all that you've done in the numbers section of that code, since you do have some logic in there to ensure normalized numbers aren't already on the watch/blacklisted numbers lists before being added.
 
teward/Osiris: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev c4d12dea7 (SmokeDetector: Auto watch of readme\.security by cigien) (running on teward/Osiris, Python 3.8.10)
Restart: API quota is 39250.
[ SmokeDetector | MS ] Linked punctuation in body (22): Timer doesn't stop at green color ✏️‭ by Motanu Jora‭ on stackoverflow.com
 
fp- feedback received on [MS] Timer doesn't stop at green color
 
7:55 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Web adress is greyed out in wordpress app in settings ✏️‭ by Kirah‭ on stackoverflow.com
 
8:06 PM
[ SmokeDetector | MS ] Luncheon meat detected (41): Post request results in 414 Request URI Too Long Error ✏️‭ by George‭ on stackoverflow.com
 
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 4dd95f541 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.8.5)
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Formatting issues with SVG images in CSS‭ by La1sum‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): What to do if neural network always performs poorly even after addressing overfitting?‭ by Maxim Lyuzin‭ on stackoverflow.com
 
8:40 PM
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Mapbox with Flask not rendering certain images ✏️‭ by KCW‭ on stackoverflow.com
 
9:14 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): can anyone help me to submit cisco packet tracer exam?‭ by Jinan‭ on stackoverflow.com
[ SmokeDetector | MS ] No whitespace in title (70): swapExactTokensForTokensSupportingFeeOnTransferTokens‭ by Emrah‭ on ethereum.SE
 
9:32 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Move an folder outside the current folder‭ by user1597152‭ on askubuntu.com
[ SmokeDetector | MS ] Link at beginning of answer (35): How to generate pem from jwk in go‭ by David Sharnoff‭ on stackoverflow.com
 
9:52 PM
[ SmokeDetector | MS ] Bad keyword in answer, link at beginning of answer, link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (185): Are there any free command line based zip utility?‭ by rico alvaro‭ on superuser.com (@Ollie)
 
!!/watch loginptbola\.com
 
10:07 PM
PR#7003 ("Don't re-request posts when post processing conflict for some sites (e.g. SO)") opened by makyen
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Minecraft javascript error‭ by hanry robert‭ on stackoverflow.com
 
tp feedback received on [MS] Minecraft javascript error
 
!!/watch hackadviserpro
 
10:31 PM
[ SmokeDetector | MS ] Link at end of answer (61): SMS provider for Node‭ by Eman Resu‭ on stackoverflow.com
 
tpu- feedback received on [MS] SMS provider for Node
 
sdc watch- floppysend\.com
 

« first day (3105 days earlier)      last day (715 days later) »