« first day (3813 days earlier)      last day (12 days later) » 

8:04 PM
@JoshZhang Query parameters are easier for us, but headers should work too. What's actually difficult for us is if we need to go through a login process using the normal SE login pages, due to the likelihood of hitting a CAPTCHA. I'll need to take a closer look at the Ruby on Rails side of things to verify that setting the headers on MS is reasonable, as I'm not nearly as familiar with Ruby on Rails as I am for Python. For actually setting the secret in the various instances, I'll need to rope in some other people. For discussing what the secret will be, assuming we want it to actually be secret, I'd suggest having that discussion in a private room.
 
[ SmokeDetector | MS ] Link at beginning of answer (37): Create Vertical Scrolling Text in UserForm‭ by MikeVol‭ on stackoverflow.com
 
@SmokeDetector naa-
 
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body, potentially bad keyword in title, potentially problematic ns configuration in body (97): Pertanyaan: Apa itu Slot Zeus?‭ by Ligaciputravip‭ on proofassistants.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): number of pages in word document‭ by Brett Mather‭ on stackoverflow.com
 
@SmokeDetector tpu-
@SmokeDetector fp-
 
@Makyen Thanks! I wasn't sure whether declining or marking helpful had some other impact. I will mark them as helpful.
 
8:12 PM
!!/approve 10856
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (266): Pertanyaan: Apa itu Slot Ligaciputra? ✏️‭ by Ligaciputravip‭ on proofassistants.SE
 
@SmokeDetector tpu Weird edit...
 
@GeneralGrievance Registered question as true positive and blacklisted user.
 
!!/test wocketwallet.com
 
> Potentially problematic ns configuration in body, potentially problematic ns configuration in title
----------
Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for wocketwallet.com are in set {'203.161.50.10'}
Potentially problematic ns configuration in title - Suspicious nameservers: all IP addresses for wocketwallet.com are in set {'203.161.50.10'}
 
8:15 PM
!!/watch wocketwallet\.com "From the first revision"
 
@GeneralGrievance You don't have blacklist manager privileges, but I've created PR#10857 for you.
 
PR#10857 ("General Grievance: Watch wocketwallet\.com "From the first revision"") opened by SmokeDetector
 
@DalijaPrasnikar It only has an impact if you mark a lot of them (as in a month or two of them all at once) as declined within a short period of time (7 days). In that case, it has in the past resulted in SD being flag banned, due to too many declined flags in a 7-day period. If the flags are handled on a reasonably current basis, then even if all of them are declined somewhat close to when they are raised, there aren't enough of them to result in SD being flag banned. So, please don't go looking through the "other" flag queue just for these and decline them all. As for other impact, there is none. There's nothing that looks at the state of if it was marked helpful or declined. It's just a "hey, the humans don't agree and something bad might have happened here."
2
 
!!/blacklist-website- daftarslotonline\.com
 
PR#10858 ("Fastnlight: Blacklist daftarslotonline\.com") opened by SmokeDetector
 
8:24 PM
^^^ 5/0/0 on MS
 
[ SmokeDetector | MS ] Offensive body detected, potentially bad keyword in body (48): My A, and S key on my laptop sometimes doesnt work ✏️‭ by CureYNK‭ on superuser.com
 
!!/approve 10858
 
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): HP printer EWS replace the self signed certificate with a signed certificate ✏️‭ by pol9595‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword with email in body, potentially bad keyword in body, potentially problematic ns configuration in body, blacklisted user (225): DO YOU KNOW HOW I RECOVERED MY SCAMMED CRYPTOCURRENCY?‭ by Susan Manny‭ on money.SE
 
@Vickel User is not blacklisted (30997765 on stackexchange.com).
:65564017 User is not blacklisted (30997765 on stackexchange.com).
 
I think we have a blacklist for "ligaciputra" in user names.
 
@Vickel User blacklisted (30997765 on stackexchange.com).
 
I think so too, but thought it wouldn't hurt blacklisting user on network
 
[ SmokeDetector | MS ] No whitespace in title, repeating characters in title (134): sdsdsdsdsdsdsdsdsdsdsdsdsddddddddddddddddddddddd‭ by Lucas Linhares‭ on math.SE
 
9:09 PM
I love AI
 
9:26 PM
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer, potentially bad keyword in answer, repeating characters in answer (264): I have a question about the gravity probe B geodectic precession formula and why it seems to be twice the planetary precession formula ✏️‭ by Inga Ntenjana‭ on physics.SE
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): JCenter deprecation; impact on Gradle and Android ✏️‭ by Ammar Omari‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Qt 6.7 to open .mdb file, failed at IM002 QODBC: Unable to connect‭ by Gunawan Wicaksono‭ on stackoverflow.com
 
@Makyen Yes, I figured that when you said that declining them in bulk wouldn't be a good idea. If there is no other logic, then marking as helpful is the safest and easiest solution.
 
10:06 PM
[ SmokeDetector | MS ] Blacklisted user (71): Vuejs and quarkus development and deploy ✏️‭ by Sibin Muhammed‭ on stackoverflow.com
 
!!/close 10857 "this appears to ocntain a comment, but was (mis)interpreted as part of the watch"
 
@JeffSchaller Please provide an adequate reason for rejection (at least 20 characters long) so the user can learn from their mistakes. Use -force to force the reject
 
@GeneralGrievance I assume you mean "From the first revision" as a comment, but Smokey interpreted that to be part of the watch; want to re-send the watch by itself?
 
@JeffSchaller Closed pull request #10857.
 
10:13 PM
last seen in chat an hour ago, so I may send it in if they don't reappear shortly
 
@SmokeDetector f edit removed the link to their blog
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Knockout input control and alert‭ by Katta‭ on stackoverflow.com
 
fp feedback received on [MS] Knockout input control and alert‭
 
10:26 PM
!!/watch wocketwallet\.com
 
@GeneralGrievance it looked like you left for the "day", so I went ahead and added this watch for you
 
10:49 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Networked In-Memory FileSystem w/ zram + XFS + GlusterFS - Best Practices ✏️‭ by Victor‭ on serverfault.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body (193): MEXC Referans Kodu: mexc-rb Olarak Bilinir‭ by Asyaflow‭ on meta.SE
 
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)
 
11:07 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Configure Wordpress to use MariaDB over SSL?‭ by themegamenuguy99‭ on superuser.com
 
@Fastnlight User blacklisted (24718066 on stackoverflow.com).
 
11:54 PM
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially problematic ns configuration in body (289): CONTACT ADRIAN LAMO HACKER TO RECOVER LOST DIGITAL ASSETS‭ by Michael Zurn‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, bad keyword in body, bad keyword in title, bad phone number in body, +4 more (587): FIND YOUR STOLEN BITCOIN BY CONTACTING ADWARE RECOVERY SPECIALIST‭ by Recheal Clark‭ on bitcoin.SE
 

« first day (3813 days earlier)      last day (12 days later) »