« first day (3928 days earlier)      last day (112 days later) » 

[ SmokeDetector | MS ] Manually reported answer (93): What is a SHA1 fingerprint?‭ by Mudassar Javed‭ on stackoverflow.com (@Anerdw)
@SmokeDetector tpu-
[ SmokeDetector | MS ] Manually reported answer (93): Running flyway in docker-compose fails to connect to database‭ by Isabella‭ on stackoverflow.com (@Anerdw)
18:11
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body (2): why cannot i connect to watch TV when i moved to Germany?‭ by Abdelilah Kadiri‭ on travel.SE
This post is pretty suspicious: stackoverflow.com/a/78889115/20153035
@Starship Basically, there are concerns over your prior actions. I would need to look much closer to determine which portions of those concerns I can share (which is a different issue than looking at the concerns).
[ SmokeDetector | MS ] No whitespace in title (70): markerClusterOptions ✏️‭ by nibedan‭ on stackoverflow.com (@Anerdw)
fp- feedback received on [MS] markerClusterOptions‭
Cow
Cow
@Fastnlight not an answer at least
18:14
What's suspicious is that the domain was bought Aug 3, and many pages were updated a day or 2 ago
Cow
Cow
@Fastnlight report it with that info
I want some concrete evidence before doing that (if possible)
Cow
Cow
ah ok
Found it
18:18
[ SmokeDetector | MS ] Manually reported answer (93): Convert schedule in pdf to calendar file‭ by Sriram MK‭ on stackoverflow.com (@Anerdw)
@SmokeDetector 4 days ago, the DNS was moved to vercel (which is where this website is hosted). Many of the pages were added a couple days ago. There's no ways this user randomly found this brand new site
Cow
Cow
@Fastnlight lets see it! :D
omg you should become a detective!
remember to add as comment to MS
[ SmokeDetector ] GitHub Actions: success on 9b05340 by makyen in the master branch
[ SmokeDetector ] SmokeDetector started at rev 9b05340e54 (Makyen: Merge pull request #12755 from tripleee/anerdw-charcoal-privs) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 99048.
18:24
That took a long time to restart.
@Anerdw No, not a problem, but if you want it to be the same on metasmoke, then you will need to manually change it there too.
@Anerdw We've added you to the privilege list for SmokeDetector (SD) here in Charcoal HQ, which also applies to several other rooms. You should run the !!/amiprivileged command to verify. It would be a good idea to read through the Feedback Guidance, SmokeDetector wiki, and SmokeDetector commands (in particular feedback).
If you haven't already read it, there's an Introduction to Participating in Charcoal. You may have already seen that introduction and some of the other things linked here, but this wall of text puts several of them in one place.
You may also want to look at the userscripts we have available (GitHub), as they can be quite helpful, depending on how you want to participate. For viewing, feedback, and flagging in chat, I find FIRE and AIM to be the ones I use the most. I also find SIM (install) convenient.
For flagging through the userscripts, your metasmoke account needs to be write authenticated with SE, which, if you haven't already done so, can be done from the authentication page and doesn't require you to also sign up for autoflagging, although authenticating is also a required step for signing up for autoflagging.
In addition, to enable manual flagging through the userscripts, the checkbox that says "Allow metasmoke to raise flags for my account" on this page also needs to be checked. If you have no entries in the "ID Site Count Flags Used Today" list at the bottom of that page, then autoflagging will still not be enabled, but manual flagging through the userscripts will be enabled.
Just so you know, we normally tell people when they are getting privileges that we practice the "ton of bricks" discipline method here: If you mess-up sufficiently, or consistently, we come down like a ton of bricks :-).
To quote ArtOfCode: "TL;DR: ton-of-bricks is mostly to say that we almost never need to enforce things because things enforce themselves through having a good community here. If it gets to the point that someone's enforcing something, something's gone badly wrong."
Quoting NobodyNada [with a bit added]: "Note that 'mess up' doesn't mean 'make a mistake', it means 'do something intentionally irresponsible/antagonistic' [or consistently do something wrong and not change when it's, repeatedly, pointed out]. Charcoalers are generally quite friendly, forgiving of mistakes, and willing to help each other learn. We recognize that our systems and policies have quite the learning curve -- so don't be afraid of us :)"
Cow
Cow
@Anerdw welcome to the team
This tab just went from 0 to 10 unread messages in the span of 12ms
Cow
Cow
that's Makyen for ya
[ SmokeDetector | MS ] Manually reported answer (93): XNA game development kickstart ✏️‭ by mrmKDO‭ on stackoverflow.com (@Anerdw)
tpu- feedback received on [MS] XNA game development kickstart‭
Cow
Cow
18:27
sdc watch- kovendo\.com
PR#12774 ("Cow: Watch kovendo\.com") opened by SmokeDetector
!!/watch- Hulk24\.com
PR#12775 ("Fastnlight: Watch Hulk24\.com") opened by SmokeDetector
@Fastnlight 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 word(s) if you really want to add the pattern you provided.
Cow
Cow
@Fastnlight did you mean to link a discussion here?
Yes, I did
Cow
Cow
:D
Thanks for pointing that out
Cow
Cow
:)
18:32
@Makyen in here too would be nice since I might end up more involved, but the place I’m most likely to be lurking and seeing reports is the Tavern, so just that’s fine too. I didn’t realize they were distinct before I asked, but either way is good. Thanks.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Streamlit Deployment with Websocket Server‭ by TaskMaster‭ on stackoverflow.com (@Anerdw)
!!/approve 12775
!!/approve 12774
sdc watch- arjunmp\.com
18:39
@VLAZ 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 word(s) if you really want to add the pattern you provided.
@Makyen Thanks! I'll make sure to give all those sites a reread. Excited to help :)
@Cow thanks cow :)
!!/approve 12772
!!/approve 12765
18:43
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:43:53 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/1852781?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=superuser.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:44:20 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/476819?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=mathoverflow.net
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:44:34 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/136545?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=diy.stackexchange.com
Cow
Cow
:o
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:44:48 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.4/questions/49193?key=IAkbitmze4B8KpacUfLqkw((&filter=!scxINmJWAnjuckNJkP9YfbG196DrCj)DDXQjRKUGfp-QzZ3b1nRh1Qitw7)FdyW_)iLrL8TBxFYZ1&state=PublishedAndStagingGround&site=linguistics.stackexchange.com
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on d00b61c by SmokeDetector in the master branch
wait, does spamtracker do notifications for me? so i didn't need to do the command? that's embarrassing
!!/unnotify-all
@Anerdw I will no longer ping you anywhere when I report a post.
18:48
!!/approve 12766
> - Post 1: This does not look like spam
+ I hit an error while trying to run that command; run `!!/errorlogs` for details.
================== 1 failed, 354 passed
!!/approve 12770
!!/approve 12769
Cow
Cow
@SmokeDetector f
19:02
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ns for domain in answer, blacklisted user (167): Invert colors of an image in CSS or JavaScript‭ by Alex Oger‭ on stackoverflow.com
Cow
Cow
@SmokeDetector user has website in bio also
15 hits on URL on SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (75): journalctl: how to display colors in its output?‭ by Arbgit‭ on serverfault.com
@SmokeDetector tpu-
Cow
Cow
@SmokeDetector article 4 days old and username similar to website url
@SmokeDetector user also has website in bio
19:10
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on a87dd81 by makyen in the master branch
Cow
Cow
sdc watch- arbgit\.com
@Cow 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.
Cow
Cow
sdc test shadowhackr.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 0-15: shadowhackr.com
Potentially bad keyword in title - Position 0-15: shadowhackr.com
Potentially bad keyword in username - Position 0-15: shadowhackr.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (75): How to record screen with FFmpeg in macOS without getting this error: "Selected framerate is not supported by the device."‭ by Arbgit‭ on superuser.com
[ SmokeDetector ] GitHub Actions: success on 96223ed by makyen in the master branch
19:12
@SmokeDetector tpu-
@SmokeDetector And ChatGPT.
CI on a87dd81 succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at rev 96223edcb0 (Makyen: Move Jeremy Banks to Charcoal HQ) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 98637.
@Jeremy We've added you to the privilege list for SmokeDetector (SD) here in Charcoal HQ, which also applies to several other rooms, including The Tavern. You should run the !!/amiprivileged command to verify. It would be a good idea to read through the Feedback Guidance, SmokeDetector wiki, and SmokeDetector commands (in particular feedback).
If you haven't already read it, there's an Introduction to Participating in Charcoal. You may have already seen that introduction and some of the other things linked here, but this wall of text puts several of them in one place.
You may also want to look at the userscripts we have available (GitHub), as they can be quite helpful, depending on how you want to participate. For viewing, feedback, and flagging in chat, I find FIRE and AIM to be the ones I use the most. I also find SIM (install) convenient.
For flagging through the userscripts, your metasmoke account needs to be write authenticated with SE, which, if you haven't already done so, can be done from the authentication page and doesn't require you to also sign up for autoflagging, although authenticating is also a required step for signing up for autoflagging.
In addition, to enable manual flagging through the userscripts, the checkbox that says "Allow metasmoke to raise flags for my account" on this page also needs to be checked. If you have no entries in the "ID Site Count Flags Used Today" list at the bottom of that page, then autoflagging will still not be enabled, but manual flagging through the userscripts will be enabled.
Just so you know, we normally tell people when they are getting privileges that we practice the "ton of bricks" discipline method here: If you mess-up sufficiently, or consistently, we come down like a ton of bricks :-).
To quote ArtOfCode: "TL;DR: ton-of-bricks is mostly to say that we almost never need to enforce things because things enforce themselves through having a good community here. If it gets to the point that someone's enforcing something, something's gone badly wrong."
Quoting NobodyNada [with a bit added]: "Note that 'mess up' doesn't mean 'make a mistake', it means 'do something intentionally irresponsible/antagonistic' [or consistently do something wrong and not change when it's, repeatedly, pointed out]. Charcoalers are generally quite friendly, forgiving of mistakes, and willing to help each other learn. We recognize that our systems and policies have quite the learning curve -- so don't be afraid of us :)"
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Many elements are missing from find_elements using Selenium‭ by Shachar Weinmann‭ on stackoverflow.com
[ SmokeDetector ] GitHub Actions: success on a87dd81 by makyen in the master branch
@Zoe-Savethedatadump Hey, I realized a while back that your Boson bot that archives comments doesn't archive hover titles (i.e., [Link text](https://example.com "hover title")) in comments, because those are not in the onebox that the system generates.
Can you please modify the bot so it checks for hover titles in links, and posts them in text after the comment if any links contain them?
Speaking of which, do hover titles work in chat messages?
Yes. Yes they do
Until such time as comment oneboxing is fixed to incorporate hover titles, the bot should work around the omission.
Cow
Cow
19:35
works for me too
I ran into this because I was searching the Meta.SE comment archive for the text of a hover title I used in a now-deleted comment, but came back empty-handed because the system omitted it.
@Makyen I don't know whether to be heartened or slightly disturbed that that statement is still correct enough that I can be quoted on it five years later...
@ArtOfCode I'd say heartened. It means we still function like an informal social group like we always have
The flag-based-fraternity endures.
19:40
@ArtOfCode I'd definitely say "heartened". It means things are still working and haven't broken. :)
@ArtOfCode Speaking of which, what do you think of my two pending code changes (github.com/Charcoal-SE/SmokeDetector/pull/10018 and github.com/Charcoal-SE/SmokeDetector/pull/12205) to SmokeDetector? It's been a while since those have seen action, and @Spevacus was really kind to test them for me to make sure they work. I hope they can be actioned soon.
@gparyani I'd love to say I'm still familiar enough with Smokey's code that I can competently review changes, but... I don't think that's the case :)
@ArtOfCode Well, the code changes are on the more minor side, especially the latter one. They've also been tested, as I mentioned.
Design/philosophical feedback is also welcome. For instance, if there was a reason why back then the team deliberately decided not to put the type of watch/blacklist in PR titles.
The ideas seem reasonable enough. The code... I am not the reviewer you're looking for there :)
at this point I retain privileges on a mostly-emeritus basis
In fact, that kind of thing is why I opted to initially post that as an issue for discussion and submit the code change next.
19:45
I was sad to see that you've elected to hang up your SE hat. I hope you know that, while we haven't exactly interacted a whole lot, in the times we have, your insight has always left a lasting positive impression. This project, despite the bump in the road with the Strike, has endured the test of time. I hope it's been communicated to you, and the other founders/admins, how important it is to the network.
9
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (75): Many elements are missing from find_elements using Selenium‭ by Arbgit‭ on stackoverflow.com
I never really "hung up" my hat, so to speak... it more just fell off as I leaned further and further back. I didn't feel it necessary to leave with fanfare, but SE isn't a company I want to donate my time to. It does make me very happy to see Charcoal still doing so well, though :)
6
!!/blacklist-website- arbgit\.com
PR#12776 ("Fastnlight: Blacklist arbgit\.com") opened by SmokeDetector
19:48
!!/approve
@ArtOfCode Missing an argument.
for old times' sake :D
oh bollocks
(!!/approve 12776)
(Thanks!)
!!/approve 12776
Cow
Cow
rofl
:) Can you believe this guy wrote code for the project?
I can't :P
@ArtOfCode If you really wanted old times' sake, you'd have done the !!/approve command on the PR itself with PullApprove. ;)
I don't have time these days for anywhere near as much dev as I'd like - I'd love to still poke around here occasionally.
@Mithical I'll be honest I forgot that even existed... although I seem to recall I was the one to set that up? Whoops.
It's been a minute since I've seen it used. I still get e-mails from PullApprove about updates they've made, so I have to assume it still works, but I haven't tried it in forever.
19:56
sdc approve 12767
!!/approve 12767
Tried it on that one, but no dice. It's possible I was never set up with it.
19:58
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Unable to add more than 2 adsterra ad banner on Next.js 14 app‭ by Abid Ali‭ on stackoverflow.com
O.o tripleee is almost at 100k feedbacks
@Spevacus We disabled it a long time ago.
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Unable to add more than 2 adsterra ad banner on Next.js 14 app‭ by Professor‭ on stackoverflow.com
Fair 'nuff.
20:04
@Makyen Wellll.... a while ago, maybe not "a long time ago".
But, it's definitely disabled, not broken.
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): EVA DTS for vending machine ✏️‭ by Pedro Peña Villar‭ on stackoverflow.com
naa- feedback received on [MS] EVA DTS for vending machine‭
Affogato (), known in full in Italian as (gelato) affogato al caffè ('(ice cream) drowned in coffee'), is an Italian dessert comprising a scoop of plain milk-flavored (fior di latte) or vanilla gelato or ice cream topped with hot espresso. Some variations add a shot of amaretto, bicerin, Kahlúa, or other liqueur. == Varieties == Though restaurants and cafés in Italy categorize the affogato as a dessert, some restaurants and cafés outside of Italy categorize it as a beverage. Whether a dessert or beverage, restaurants and cafés usually serve the affogato in a tall glass with a narrow botto...
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ns for domain in answer, username similar to website in answer, blacklisted user (240): How to install Python3.12 within POP!_OS Flatpak VSCodium and change its python interpreter version to Python3.12?‭ by Arbgit‭ on stackoverflow.com
!!/blacklist-website- arbgit\.com
@Vickel That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Pandas and replacing Excel values incosistently‭ by audibleillustation‭ on stackoverflow.com
20:23
missed it... forgot again Ctrl F5
YES
love that site :)
20:36
@Vickel It's really not something to worry about. We have checks in place so that, for the most part, people don't need to think about it.
@Makyen one of the many things you have to have checks for when using distributed systems
Yep. :)
!!/amiprivileged
@Jeremy ╳ You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
in Tavern on the Meta on Meta Stack Exchange Chat, 14 secs ago, by SmokeDetector
@Jeremy ✓ You are a privileged user.
Worked in the Tavern, so that's good enough for me. Thanks!
20:44
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Xunit Skip Tests‭ by user26881681‭ on stackoverflow.com
@Makyen is there somewhere (maybe a private room or something) were you can share all of the concerns, as I can hardly improve upon what I don't know...
fp- feedback received on [MS] Xunit Skip Tests‭
@metasmoke It tries to solve the problem and identifies the method that should be called to do so. Doesn't provide example code, but neither does the question, so I'm personally willing to let it slide.
!!/reboot
teward/Cerberus: Goodbye, cruel world
[ SmokeDetector ] SmokeDetector started at rev e80265d0ca (SmokeDetector: Merge pull request #12767 from Charcoal-SE/auto-blacklist-1724078461) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 97826.
@Jeremy ╳ You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
20:56
@Jeremy The results here are unexpected. I'm currently unsure why that's the case.
@Jeremy Ahhh, found the problem. Your chat user ID on chat.SE had been changed from what MS had in its records for you. Those records were used to generate the configuration file for SD. It will be a moment for that to be corrected.
@Makyen github.com/Charcoal-SE/SmokeDetector/blob/master/… has the wrong chat.SE ID: it should be 355597, not ... ninja'd
@Makyen I think his users.yml entry is incorrect. If the comment is correct, his entry should be 851: [851, 355597, 134300, 1114] # Jeremy Banks . The stackexchange_chat_id is 1251 instead. -- Double ninja
hahaha
Look at us, on the ball.
Let it not be said we have any shortage of people ready to jump in and help solve problems :)
21:01
:)
@Makyen could you please see my message above
[ SmokeDetector | MS ] Manually reported answer (93): Change TLS version used by Python‭ by CEO GridMedix‭ on stackoverflow.com
[ SmokeDetector ] GitHub Actions: success on 73fbe80 by makyen in the master branch
tpu- feedback received on [MS] Change TLS version used by Python‭
naa- feedback received on [MS] Change TLS version used by Python‭
@SmokeDetector Glass half rude, half NAA. Unsure. I flagged as NAA fwiw.
[ SmokeDetector | MS ] Manually reported answer (93): Java event system/observer pattern‭ by Cyklon 73‭ on stackoverflow.com
21:07
tp- feedback received on [MS] Java event system/observer pattern‭
[ SmokeDetector ] Blacklists reloaded at rev 73fbe8065a (Makyen: Update Jeremy Bank's chat.SE ID) (running on teward/Cerberus)
@Jeremy ╳ You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
!!/reboot
teward/Cerberus: Goodbye, cruel world
[ SmokeDetector ] SmokeDetector started at rev 73fbe8065a (Makyen: Update Jeremy Bank's chat.SE ID) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 97670.
@SmokeDetector sigh reboot/reload blacklists logic failed.
@Jeremy ✓ You are a privileged user.
21:13
\o/
if at first you dont succeed, try, try again?
Yeah, but it reminded me that I have a rewrite of that logic that I need to test/complete. sigh, yet another thing :;
@Makyen when your todo list decreases linearly, but increases multiplicatively
I've let that one side because it was basically working, but clearly there are more holes in it than I remembered.
@Dragonrage :)
21:16
user image
6
@SmokeDetector seems to be a single case of undisclosed affiliation. though the url matches name of user. mod flagged
@Anerdw the answer is a link to the official docs... of course adding context around the link could be encouraged by a comment...
21:28
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev bff40c61e9 (tripleee: Blacklist IP 103.200.22.208) (running on Makyen/EC2-linux)
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)
Thanks for the fix!
21:47
np. Sorry for the inconvenience and multiple pings.
@Vickel I was initially considering NAA for some reason. Not sure how I forgot the guidelines that badly :P
@Anerdw IMO, a link to official documents, including a little info (like in this case), even short, never hurts. But it could obviously be improved from a mediocre to a good answer with a little comment. Anyway you are not compelled to leave such a comment.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body (2): Trouble Reprojecting Rotated Latitude-Longitude Grid to EPSG:4326 in GDAL‭ by Hundesa Siraj Mohammed‭ on stackoverflow.com
@Vickel I posted this comment - "Thanks for your contribution! Links to documentation are wonderful, but the most helpful (and upvoted) questions contain more than a link. If you want, you can edit your question to include more details about this method and how it should be used to solve this problem."
Does that seem appropriate?
21:57
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Resizing HTML element ✏️‭ by Jack‭ on stackoverflow.com
fp- feedback received on [MS] Resizing HTML element‭
@Anerdw I saw it, nice comment, thanks
@Anerdw here is a good read about How do I properly use the "Not an Answer" flag?
22:08
@Vickel thanks for the link. usually i'm better about this! temporary insanity i guess :)
!!/watch iFORCE[\W_]*+HACKER[\W_]*+RECOVERY
@Vickel You don't have blacklist manager privileges, but I've created PR#12777 for you.
PR#12777 ("Vickel: Watch iFORCE[\W_]*+HACKER[\W_]*+RECOVERY") opened by SmokeDetector
22:13
!!/test-q hacker recovery
> Would not be caught as a question.
hmm... couldn't "hacker recovery" eventually create some fp's? otherwise MS says 15,0,0
https://metasmoke.erwaysoftware.com/search?utf8=%E2%9C%93&body_is_regex=1&body=HACKER%5B%5CW_%5D*%2BRECOVERY
@Makyen i remember you mentioned using .* could be problematic in regexes for watches. is there a specific upper bound that you recommend? e.g. .{0,x}
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad keyword in answer, potentially bad keyword in username (40): In the IBM Dynamic Workload Console, the Plan View freezes with Internet Explorer 7 in Jazz for Service Management v1.1.2 on Workload Scheduler ✏️‭ by Amnathe Seoexpert‭ on stackoverflow.com
22:27
@SmokeDetector k
@Dragonrage oooh it's a tsunami :)
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Smoke node tree and path help needed‭ by Zoddball‭ on blender.SE
!!/approve 12777
@Dragonrage I think I can do you one better: metasmoke.erwaysoftware.com/…
@Laurel oh nice
I wonder if that covers all the ones from my search as well
[ SmokeDetector | MS ] Bad keyword in link text in body, pattern-matching website in body (168): As someone who’s constantly trying to stay ahead‭ by Nazariy‭ on scifi.SE
22:51
!!/watch- valhallavitality\.com
@Dragonrage It really depends on what's needed for what you're trying to match. I generally run multiple searches on MS in order to get a range that's as small as reasonable to catch what we've seen, and perhaps a bit more, if I think it's likely a spammer will do that.
If I'm investigating something, then I increase the upper bound notably in order to get more data, but with the expectation that I will revisit it in the not too distant future to see what the effect would be of reducing it (record what the current results are, so you can compare and know what the results are of just after adding the entry).
I've used various numbers, such as 10, 20, 30, 40, 80, 160, 200, and 400, depending on what's needed for that particular regex. More values that I've used can be found in the existing entries.
In the initial investigation phase, I'd probably run 10, or substantially more, regex searches with various different combinations. After an investigation, it's not all that uncommon for me to close 100+ tabs that I've used to look into it.
Another thing I'll typically do is perform a more expansive search on MS to catch all of them, then copy all of the results into regex101, sometimes separated out into TP, FP, and NAA, and play with them there, looking at what the matches are, what's around the keywords I've selected, etc. It's not uncommon for me to have multiple such runs in a single investigation.
As a side note: MS has some strange-isms with respect to the maximum permitted spread in a {x,y}. I'm not recalling what those limits are. I'm just remembering that they exist, and they make using larger spreads ... inconvenient (e.g., multiple searches with various brackets, or multiple paths through the regex, such as fo(?:o{0,1000}|o{1001,2000}) instead of foo{0,2000}).
23:07
@Makyen crypto.*recovery gives 1120 results, 1112 TP, 5 FP, 1 NAA. 0-500 gives 1078, 1071 TP, 4, FP, 1 NAA. 0-300 is 1014 records. 0-200 is 968 records. and 0-100 is 868 records
@Dragonrage OK. Look at the results at the higher end and see what you are/aren't catching (the actual text). That the words are so far apart in some cases tends to indicate that it might not be all that great of a combination for those posts, but then again, it might. Not every entry needs to catch every post.
@Makyen cool. Ill try that out and see what i get. and yeah thanks for the reminder.
imagine though. the perfect regex that caught all spam. it would be an abomination i dont think anyone could parse
@Dragonrage Well, to a large extent we could do very close to that by combining everything we have. It wouldn't catch everything, and there would be data that wasn't retained, but we could go a long way. You're right though, it would be one quite large regex. :)
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Building an App for users to create SPL Tokens & Set Authority‭ by DeFiDevJimmy‭ on solana.SE
23:45
!!/test-q crypto recovery
> Potentially bad keyword in body
----------
Potentially bad keyword in body - Position 0-15: crypto recovery
!!/bisect crypto recovery
@Dragonrage Matched by crypto(?:currency)?[\W_]*+recovery\w*+ on line 53552 of watched_keywords.txt
23:56
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Advice on the assets made by this creator?‭ by Alice‭ on gamedev.SE

« first day (3928 days earlier)      last day (112 days later) »