« first day (3673 days earlier)      last day (75 days later) » 

[ SmokeDetector | MS ] Manually reported answer (93): How to install python3.11 and update Pylint on Amazon Cloud9 IDE?‭ by SKB‭ on stackoverflow.com
 
Sorry to break up the silence, but we have another high rep user committing second degree spam (undisclosed affiliation): stackoverflow.com/a/77623731/20153035
 
12:43 AM
!!/watch- surajbirla\.blogspot
 
PR#9194 ("Jesse: Watch surajbirla\.blogspot") opened by SmokeDetector
 
@Fastnlight Post 1: This does not look like spam
 
@SmokeDetector This should have tripped the "URL similar to username" filter. Anyways, could someone report this?
 
12:47 AM
@Makyen @ThomasWard Getting an error from MS when trying to cast a spam flag:
OpenSSL::SSL::SSLError in PostsController#cast_spam_flag
SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)
 
5 hours ago, by Makyen
@Jesse That's the URL which FIRE is accessing, but the error appears to be generated by MS trying to access the AWS Lambda that performs the actual flagging. The /autoflag/options endpoint is one of the ones defined in the AWS Lambda. While I could probably dig into it to find more detail, this is something that @Undo will be needed to fix, as they are the one with access to that AWS Lambda instance. cc @ThomasWard
 
tpu- feedback received on [MS] Lambda Layer Function for Snowflake‭
 
[ SmokeDetector | MS ] Manually reported answer (93): Get random boolean true/false in PHP‭ by designcise‭ on stackoverflow.com
 
12:50 AM
@Fastnlight done
 
Thanks
 
@Nick Thanks. Yes, that's a problem. Undo has said they might be able to get to it this evening.
 
@Makyen ok thanks. It seems to still be recording my feedback, so I'll just manually cast flags until then
 
In fact, this account is really bad. 70 potential spam posts
I'll mod flag
 
@Fastnlight It's because they have too much rep. I'm going to be experimenting with increasing the rep cap (or potentially removing it entirely) in the near future.
 
12:53 AM
@Jesse I was unaware SD filtered in rep. However, reasons like that where it's almost guaranteed that they are affiliated we may want to flag.
 
Yep, that's why I'll be experimenting with it.
 
@Fastnlight I definitely think that's a good idea.
too hard to report and spam flag them all...
 
@Jesse User blacklisted (2382283 on stackoverflow.com).
 
1:00 AM
Hmm, maybe I should have just done tpu. Oh well, too late.
 
1:16 AM
[ SmokeDetector | MS ] No whitespace in title (70): AuthCodeExchangeError‭ by Randy Kroeger‭ on salesforce.SE
 
fp feedback received on [MS] AuthCodeExchangeError‭
 
[ SmokeDetector | MS ] Link at beginning of body (43): How can I decrypt such a type via dart‭ by Ameen Hamed‭ on stackoverflow.com
 
1:35 AM
@Jesse While it has, relatively recently, become more common to report posts where there is undisclosed affiliation to SD, it's not really SD's purpose to find those when they are from established users. SD and MS are fairly blunt interments as far as handling posts (e.g., autoflagging and how users viewing the reports evaluate posts). In general, posts with undisclosed affiliation from established users tend to need substantially more nuance in their handling, rather than straight spam flagging.
Increasing the max_rep, at least somewhat (how much is to be determined), should be OK, as long as increasing the rep limits on particular detections A) doesn't produce a large number of FP reports, and B) doesn't substantially increase the computational resources required and time necessary for processing posts (the main detection for that would be the watchlist, but the other lists also have a notable impact).
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): CoinMarketCap API with Alamofire decoding data error‭ by Sajaad Ahmad‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Equivalent Card Combinations for n-Cards ✏️‭ by fasutron‭ on math.SE
 
!!/watch-number +1 (423) 248-2140
 
!!/watch oliviatrader44
 
!!/approve 9194
 
!!/approve 9193
 
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (72): How to execute a function after another function is complete in reactjs‭ by Sajaad Ahmad‭ on stackoverflow.com
 
2:00 AM
@Makyen Yeah, that makes sense. I highly doubt a high-rep user would ever need to be auto flagged (except maybe edge cases where someone bought/hacked the account). However the main question that I'm left with is who is holding these higher rep users to the same standards that we hold new users to?
I understand that that may not be the job of this room specifically, but I feel like someone has to do it, and with as many high-rep users that have been caught posting their own links without disclosure, I think it's safe to say they've been getting away with it for a good while.
 
!!/approve 9191
 
Maybe a different room could be created with a fork of SD that's specifically looking at higher rep users with a stricter criteria.
 
@Jesse I think it would probably be pretty empty after an initial rush
 
@cocomac User is not blacklisted (23058344 on stackoverflow.com).
 
Given that there's many fewer of those (high-rep users), perhaps a custom flag would be appropriate, so a moderator could send the user a message (and/or suspension), asking the user to edit their posts?
 
@cocomac User blacklisted (23058344 on stackoverflow.com).
 
!!/approve 9187
 
2:03 AM
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer (2): Where to submit an incomplete work just for the sake of record‭ by Cheryl‭ on academia.SE
 
@Nick Yeah probably.
 
!!/approve 9186
 
@JeffSchaller True, and that's what we've been doing (for the most part), but having a bot similar to SD that is always watching would be helpful.
 
!!/approve 9185
seems more like a one-time pass, to me
 
(meaning, scan the high-rep users' posts for links that seem fishy)
!!/approve 9184
 
!!/approve 9183
 
@Jesse I think you might want to unblacklist designcise, they are actively editing posts e.g. stackoverflow.com/a/77406507/9473764
 
2:06 AM
!!/approve 9182
 
!!/approve 9181
 
@Nick apologies for that .. can you kindly re-check? — designcise 11 mins ago
 
!!/approve 9179
 
@Nick Alright. If I remember correctly, marking one of their posts as FP would also remove them from the blacklist.
 
@Jesse No such command 'removeblu'.
 
uhhh
 
2:08 AM
!!/approve 9178
rmblu, I think
 
I forgot the command
 
[ SmokeDetector | MS ] Blacklisted user (71): Node.js throws "btoa is not defined" error ✏️‭ by designcise‭ on stackoverflow.com
@Jesse The user has been removed from the user-blacklist (2382283 on stackoverflow.com).
 
@JeffSchaller Ah that's it. Thanks
 
!!/approve 9177
 
2:10 AM
@Jesse yeah, that would have worked too... Luckily SD hadn't got round to posting them all yet)
 
!!/approve 9176
!!/approve 9175
 
@JeffSchaller Yeah, that's true. Not sure why I didn't think of that. Looks like that would be about 250k users, which honestly I don't think would take too long to scan through with a script. Only limiting factor would be rate limits I think.
 
@Jesse there are 6 older FP on-site for PR 9174, just FYI
!!/approve 9174
 
2:14 AM
@Jesse could be made a bit more efficient with the API, maybe
 
@JeffSchaller Yeah I noticed that. That's why I left a comment on the PR.
 
May 1 at 19:53, by Jeff Schaller
Nov 12, 2021 at 18:24, by Jeff Schaller
reading?! No one told me we had to read around here! (╯°□°)╯︵ ┻━┻
!!/approve 9173
 
@Jesse how do you do that? I've often wanted to and just put it in the feed next to the watch.
 
!!/approve 9172
 
@JeffSchaller Fair. We should take VLAZ's suggestion one step further and just all communicate telepathically.
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): What is the "meditation on emptiness" in MN 121? ✏️‭ by a deleted user on buddhism.SE
 
@Nick I just went to the PR page on github and left a comment.
 
@Jesse oh yeah, I guess that makes sense. But does it require a github account?
 
2:22 AM
@Nick Yes
 
!!/approve 9169
 
@Jesse that's not gonna work then...
 
Although it would be cool if you could reply to one of MS' "PR opened" messages to add a comment as SmokeDetector or something.
@Nick Are you not able to make one?
 
@Jesse that would be cool. I'm trying not to have any more accounts than I absolutely need, already have enough trouble keeping track of passwords...
 
2:27 AM
Ah, fair enough.
 
[ SmokeDetector | MS ] Offensive title detected (56): Listen to me I have shit to say‭ by Jerry Bryson‭ on meta.SE (@Ollie @Ethan)
 
You should get a password manager ;)
 
tp feedback received on [MS] Listen to me I have shit to say‭
 
@Jesse Who: moderators, when it is reported to us (usually through flags), and the company, when their involvement is needed. We can and do hold users to the same standards regardless of their reputation. The Terms of Service, Code of Conduct, and all associated policies, etc. Users who have other beneficial contributions are, however, often treated with more nuance than just straight spam flagging everything and destroying the user, but their conduct and the content they post to the SE Network must meet the same requirements. We have had higher reputation users where we have gone through and deleted hundreds of their posts for various violations of policy, and handed out sanctions up to and including the destruction of their entire SE account. We do not, however, discuss publicly what actions are taken with respect to a specific user, unless that specific user chooses to make the conversation public.
 
@VLAZ based on what Makyen told me here, I think we'd want watches like PR #9165 to look more like NYANLINN[\W_]*+HTET(?:[\W_]*+NYANARIUM)? -- with the two additional + symbols to make the greedy * possessive, for efficiency in matching/non-matching
@Makyen would you be offended if I (or someone) approved PR9165 (above) as-is, or would you prefer it was rejected and re-entered with the *+ enhancement?
 
2:35 AM
@Nick That's what password managers are for. Using a password manager, and unique passwords for each site, is strongly recommended from a security point of view.
 
@Makyen Well yeah I know that. I wasn't implying that moderators don't take care of stuff like that, I was more meaning that moderators can't be everywhere at once, so they need people to flag stuff like that in order for it to get taken care of. It would just be nice to have a tool like SD to make the people that would flag that sort of thing aware of it.
Because right now there's a good amount of people getting away with it, it seems like.
 
@JeffSchaller Either way would be OK.
 
!!/approve 9165
 
@Makyen but then you have to trust the security of the password manager, and any that are cloud-based are inherently not secure
 
2:39 AM
[ SmokeDetector | MS ] Blacklisted user (71): Serialized JSON is not deserializing‭ by user16606026‭ on stackoverflow.com
 
@Nick I would recommend Bitwarden. It's free, open-source, and it's pretty easy to set up your own server to store everything if you want it synced between devices.
Whatever you do, avoid lastpass like the plague.
 
@Jesse thanks, I'll look into it
 
!!/approve 9164
!!/approve 9163
!!/approve 9162
!!/approve 9161
 
2:42 AM
@Nick There is notably less security with it synced to the cloud. I, personally, don't permit that to happen with the one I use. However, as long you choose a secure main password and the password manager does the reasonable thing and only stores the encrypted passwords in the cloud, using good encryption, it's not that significant a risk. There are a variety of Q&A about password managers on Information Security which might make for good reading.
 
@Jesse I second that - I've had a pretty good experience with Bitwarden. Can't speak to it's 2FA abilities, though (I use a seperate app for that)
 
!!/approve 9160
 
@Makyen thanks for that. I'll read that article.
 
@Nick I've just landed on security.stackexchange.com/questions/45170/…, which has some good discussion
 
2:47 AM
@JeffSchaller Feel free to reject those blacklist PRs if you don't think they meet the criteria. When I opened them, I was under the impression that having a single other blacklisted domain in the post and 0 FPs automatically qualified it for blacklisting, but after reading the watchlist and blacklist guidance page I'm not so sure.
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, blacklisted user (72): Did Jesus celebrate Hanukkah in John 10:22?‭ by Sabine Vlaming‭ on hermeneutics.SE
 
@Jesse thanks for the info! my time here is expiring, so if they're still available in ~10 hours or so, I'll check them out.
 
Should I close this issue I wrote? It (and Discussions?) might be worth considering at some point. OTOH, from what I can tell, CMs handle discussions, and it's unclear when/if there will be a functional Articles endpoint, as that one was somewhat not intentional (now not working)
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Portable Monitors for MacBook Pro?‭ by Leslie TAT‭ on apple.SE
 
3:01 AM
@JeffSchaller thanks, will take a look
 
3:16 AM
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
[ SmokeDetector | MS ] Manually reported question (92): ISRAEL PROPHECIES BIBLE thruth?‭ by Jerry lugtu‭ on meta.SE (@Ollie @Ethan)
 
tpu- feedback received on [MS] ISRAEL PROPHECIES BIBLE thruth?‭
 
@Jesse What about writing something to scan the data dumps for users who keep posting the same links (which nobody else is linking to)? (Or in SEDE)
Anyway I think we all can appreciate this ironic profile text quote from that last report: "TROUBLE SHOUTING" (yes, all caps)
 
3:36 AM
Yes, for existing posts, it would be better to use the data dump, rather than try to pull everything from the SE API. What you're wanting to do is roughly equivalent to scanning all existing questions and answers, which would be better done by hooking into the data dump.
 
teward/Thoth: Executing automatic scheduled reboot.
Restart: API quota is 77465.
 
3:53 AM
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, potentially bad keyword in answer, blacklisted user (245): Getting the private instagram users followers count via API‭ by Fan Milk‭ on stackoverflow.com
 
@SmokeDetector tpu-
 
@Laurel Ah true. Not sure why I didn't think of that. I'll probably do that at some point.
 
@SmokeDetector Not spam, but the body text is close to (and quite possibly over) what's permitted in terms of SE policies. I don't know that it is worthy of an R/A flag, though.
 
There is no question, this is an attempt to abuse the reputation site. Gain your reputation by following the rules. — aled 8 mins ago
@aled That's the point. — Blank - Host. 7 mins ago
 
@cocomac I personally think that qualifies as R/A (especially based on their comments).
But I could see it going either way to be honest.
 
Agreed, flagged as R/A. Admitting that you're trying to break the rules qualifies IMO. Someone else posted a [tag:flag-pls] in SOCVR for an R/A flag
 
!!/watch- proxiesapi\.com
 
!!/watch- proxiesapi(?!\.com)
 
[ SmokeDetector | MS ] Blacklisted user (71): C# WPF TextBox not focusing‭ by Blank - Host.‭ on stackoverflow.com
 
tpu- feedback received on [MS] C# WPF TextBox not focusing‭
 
How and why did that answer get accepted?
 
4:24 AM
@Jesse I suspect socks. They said "I also gained 6 Rep for posting this." on the other post and said "That's the point" in response to a comment calling the post abuse. That (clearly!) R/A or Very Low Quality or NAA answer also got accepted. Custom flagged.
 
Should we blacklist the user that asked the question just in case? There's no way they're not associated right?
 
Eh, it's for mods and CMs to determine that. If they get suspended for voting irregularities, then maybe, but we're generally not supposed to moderate users for socks, especially when we lack the tools to prove it. We'd also want to be convinced the sock will post spam or R/A. Rule breaking socks are bad, but they also aren't really for SD unless it's also spam or R/A.
 
Yeah I guess. I opened a mod flag for it. I'm just worried the other guy might start posting R/A stuff too after the other account (presumably) gets nuked.
 
4:42 AM
@Jesse If the other user posts something R/A, then it's very likely fair game for them being blacklisted
 
[ SmokeDetector | MS ] Link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (64): Searching using intitle‭ by gobi y‭ on meta.SE (@Ollie @Ethan)
 
tpu- feedback received on [MS] Searching using intitle‭
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Portable Monitors for MacBook Pro? ✏️‭ by Leslie TAT‭ on apple.SE
 
fp- feedback received on [MS] Portable Monitors for MacBook Pro?‭
 
5:05 AM
[ 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 (483): cashwise Customer care number / 7894338705✔️ 8867644269 ✏️‭ by Mohan Govllnd‭ on academia.SE
[ SmokeDetector | MS ] Bad keyword in answer, bad phone number in answer, potentially bad keyword in answer (189): cashwise Customer care number / 7894338705✔️ 8867644269‭ by Mohan Govllnd‭ on academia.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)
 
[ SmokeDetector | MS ] Blacklisted user (71): I'm awesome tetragrammaton‭ by YAHWEH RAPHA‭ on math.SE
 
tpu- feedback received on [MS] I'm awesome tetragrammaton‭
 
5:20 AM
[ SmokeDetector | MS ] Repeating characters in answer (78): Find the gcd of 2 complex numbers/ complex number division‭ by anonymous‭ on math.SE
 
5:39 AM
[ SmokeDetector | MS ] Bad ip for hostname in answer, potentially bad asn for hostname in answer, potentially bad keyword in answer (99): One page website menu too long‭ by dinesh kumar‭ on ux.SE
 
tpu- feedback received on [MS] One page website menu too long‭
 
[ SmokeDetector | MS ] Bad keyword in link text in body (71): Where can I find Lenskart coupons?‭ by Cashback xpress‭ on meta.SE (@Ollie @Ethan)
 
!!/watch- cashaly\.com
 
tpu- feedback received on [MS] Where can I find Lenskart coupons?‭
PR#9195 ("Jesse: Watch cashaly\.com") opened by SmokeDetector
 
5:55 AM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Open an Outlook PST File Without Changing It‭ by Adom WebDev‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): Open an Outlook PST File Without Changing It ✏️‭ by Adom WebDev‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Is my algorithm, to check whether a number is prime or not, very fast?‭ by Peter‭ on cs.SE
 
!!/watch- invoidea(?!\.com)
 
!!/approve 9195
!!/watch- cashaly(?!\.com)
 
@JeffSchaller Thanks for this, I'll make sure I use greedy possessive quantifiers going forward.
 
[ SmokeDetector | MS ] Manually reported question (92): Edit businesses profile ✏️‭ by Manbir Singh‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body (2): "Cozy Homestays near Guruvayur Temple: Recommendations for a Tranquil Stay"‭ by Nunu homestay‭ on superuser.com
 
[ metasmoke ] GitHub Actions: success on 40333dc by makyen in the master branch
[ metasmoke-deploy ] deploy started by Makyen
[ metasmoke ] ci/circleci success on 40333dc: Your tests passed on CircleCI!
 
!!/watch- nunuhomestay\.com
 
!!/watch- nunu[\W_]*+homestay(?!\.com(?<=nunuhomestay\.com))
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Can't send eth + data into contract with etherjs‭ by Zambaize‭ on ethereum.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): How to show a set of images in Google SERP?‭ by kivan Smith‭ on webmasters.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Automatic short URL in posts‭ by Siaavash‭ on wordpress.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): How to search using intitle:searchText using YouTube API‭ by gobi y‭ on stackoverflow.com
 
My whatsapp +8617329428281 — oilpressmachine 1 min ago
 
!!/watch- omaliving\.com
 
!!/watch-number- +8617329428281
 
PR#9196 ("VLAZ: Watch +8617329428281") opened by SmokeDetector
 
@Jesse And you are correct! The user that answered it got their account nuked, and the user that answered it got suspended for voting irregularities (note to mods/ROs - if this crosses over the line about discussing suspensions, feel free to delete this, although I'd appreciate a ping to let me know it was over the line)
 
6:56 AM
!!/approve 9196
 
My whatsapp+8617329428281 — oilpressmachine 1 min ago
@SmokeDetector User posted it as a comment again, so it seems reasonable to watch it, even though it wasn't in the actual post.
 
[ SmokeDetector | MS ] Username similar to website in answer (71): Check URL/IP with port with regex‭ by 17Hieng‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): StackUnify: A community mobile app‭ by gobi y‭ on stackapps.com
 
tpu- feedback received on [MS] StackUnify: A community mobile app‭
 
!!/watch- techzapk\.net
 
7:06 AM
@VLAZ 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.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Making an ice cream or icing effect as shown in GIF below ✏️‭ by Huzaifa‭ on gamedev.SE
 
[ metasmoke ] ci/circleci success on 8e696cc: Your tests passed on CircleCI!
[ metasmoke ] GitHub Actions: success on 8e696cc by makyen in the master branch
[ metasmoke-deploy ] deploy started by Makyen
 
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body (44): Có thể tự học SQL trong vòng 3 tháng không?‭ by Học viện UniGap‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (3): Chi phí du học Canada 2 năm khoảng bao nhiêu? Bao gồm các khoản nào?‭ by studyaboardblog‭ on money.SE
 
!!/watch- americanstudy\.edu\.vn
 
7:16 AM
PR#9197 ("VLAZ: Watch americanstudy\.edu\.vn") opened by SmokeDetector
 
!!/approve 9197
 
[ SmokeDetector | MS ] Pattern-matching website in body, potentially problematic ns configuration in body (96): Nurturing Minds: The Intersection of Education and Writing‭ by Zoe Calvin‭ on serverfault.com
 
!!/watch- britishessaywriters\.co\.uk
 
[ SmokeDetector | MS ] Mostly punctuation marks in body, repeating characters in body (84): How can I solve this in a smart way?‭ by Felipi Sampaio‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (72): How to bundle nestjs application with webpack‭ by JS HUB‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body (262): Buy Dissertation Abstract‭ by sarah john‭ on woodworking.SE
 
tpu- feedback received on [MS] Buy Dissertation Abstract‭
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Qual é o preço das portas de aço de grãos de madeira?‭ by Cửa Thép Vân Gỗ Alux‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Bake actions to use child of constraint‭ by gamer guy‭ on blender.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, blacklisted user (73): Can I make a fishing line going through a small hole waterproof?‭ by Fahad Saleem‭ on engineering.SE
 
7:54 AM
MS: Neither signing up for autoflagging nor revoking the autoflagging token will work at this time, due to an SSL certificate issue. There's a workaround in place which will allow us to continue to raise both autoflags and manual flags through MS. If you need to de-authorize MS from autoflagging, please do so through the interface provided in your profile on an SE/SO site and/or adjust your autoflagging conditions and preferences such that it's not enabled.
4
@Undo FYI: I've disabled SSL certificate verification from MS to the flagging AWS Lambda for the two endpoints which are used when flagging, but not on the other endpoints. MS makes public in the flag logs the data passed for those two flagging endpoints immediately after the transaction, so there isn't all that much that a MITM attack would gain from impersonating the flagging Lambda. cc @ThomasWard
While this alleviates the most pressing issue of being able autoflag and raise manual flags from MS, there are still functions which won't work (e.g., signing up for autoflagging and revoking the token). So, the need for a real fix is lessened, but still present.
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username (197): IN KAGISO SAFE ABORTION PILLS 0835584027 TOP TERMINATION CLINIC IN SOWETO,BARA‭ by Babi womensclinic‭ on askubuntu.com
 
!!/watch-number- 0835584027
 
PR#9198 ("VLAZ: Watch 0835584027") opened by SmokeDetector
 
7:57 AM
@Makyen How do I know if I need to deauthorise autoflagging?
 
!!/watch- alux\.com\.vn
!!/blacklist-number- 0835584027
 
I guess my question is more "do I need to deauthorise autoflagging" as in for now. Or is there some other consideration for why I'd want to deauthorise?
 
!!/reject-force 9198 "Went with blacklisting"
 
7:58 AM
@Makyen Closed pull request #9198.
 
@VLAZ If you no longer wish to participate in autoflagging, then it's a good idea to revoke the token. If you want to continue to participate in autoflagging, then you need to not revoke the token.
 
Thank you. I'll leave autoflagging on.
 
I don't see anything in the current SSL certificate situation which would change that decision. While disabling SSL certificate verification is, generally, a bad thing, it's only been disabled on MS's use of only two very specific endpoints. The data that is sent on those endpoints is all made public in the flagging logs milliseconds after the attempt to flag is made. It's possible that something could do a MITM attack on MS' use of those two endpoints, but there's very little to gain.
 
8:10 AM
"I don't see anything in the current SSL certificate situation which would change that decision." me neither. But you mentioned it in the SSL announcement. Also, I've not had coffee yet, so in my still sleepy brain I assumed there was a connection. Sorry for the confusion. I'll go make a coffee now.
 
[ SmokeDetector | MS ] Pattern-matching website in body, potentially bad keyword in body, blacklisted user (167): Can you provide guidance on integrating a Stock Advisor API with a web server for real-time data?‭ by Best Stock Advisory‭ on serverfault.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): sdf ksjdf ksdfh skdjsdkjsdksdsdkjfhsdkfj‭ by user23064320‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad ns for domain in body, potentially bad asn for hostname in body, potentially bad keyword in body, potentially bad keyword in username, blacklisted user (169): Mazda CX-30: Đánh giá chi tiết, giá bán, khuyến mãi‭ by Caready VN‭ on meta.SE (@Ollie @Ethan)
 
8:24 AM
@SmokeDetector tpu-
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad pattern in url body, potentially bad asn for hostname in body, potentially bad ns for domain in body, +2 more (252): The Ultimate Fix for QuickBooks Error H202: Step-by-Step Solution‭ by Benjamin James‭ on superuser.com
 
0
Q: a clue about "git command is not returning any value in makefile" questions on SO?

LeGECThere was a question asked in January 2023: git command not returning any value in makefile which was duplicated (as in ctrl+C/ctrl+V, spotted by an SO user) in November: Git command is not returning any value in makefile and recently a sequence of questions mentioned the exact same issue (variat...

 
8:44 AM
[ SmokeDetector | MS ] Manually reported question (92): walk me through set up with the twillio account‭ by Lewis Esigns‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body (2): What is the best place to purchase Ironwood Sculptures?‭ by best Ironwood‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to Combine two Normal Maps?‭ by Manuel Fankhänel‭ on blender.SE
[ SmokeDetector | MS ] Scam aimed at customers in answer (42): Delphi 10.4: Connection to a MS Access 2019 Database‭ by Thomas Schreiber‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Image is cropped on the "wrong" side‭ by Mathias‭ on wordpress.SE
[ SmokeDetector | MS ] Few unique characters in body, repeating characters in body, repeating words in body (192): test Selenium for labs‭ by Asliddin‭ on stackoverflow.com
 
@Nick re: metasmoke.erwaysoftware.com/post/453020 - see my comment there. It seems to be plagiarism. I think that is supposed to be marked tp
 
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in title (101): Female Escorts near Wadsworth‭ by avasmith‭ on chemistry.SE
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
!!/watch- bestironwood\.com
 
PR#9199 ("VLAZ: Watch bestironwood\.com") opened by SmokeDetector
 
9:22 AM
3
Q: a clue about "git command is not returning any value in makefile" questions on SO?

LeGECThere was a question asked in January 2023: git command not returning any value in makefile which was duplicated (as in ctrl+C/ctrl+V, spotted by an SO user) in November: Git command is not returning any value in makefile and recently a sequence of questions mentioned the exact same issue (variat...

 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, pattern-matching website in body, potentially bad asn for hostname in body, potentially bad keyword in body, +1 more (263): Nurturing Minds: The Intersection of Education and Writing‭ by Eva Anna‭ on serverfault.com
teward/Thoth: Executing automatic scheduled reboot.
Restart: API quota is 74338.
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body, potentially bad keyword in title (73): Smart Storage Solutions: Where to Buy Storage Devices?‭ by Danny129‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer (2): How to reduce a unuse css file?‭ by Business Magazine‭ on stackoverflow.com
 
9:54 AM
tpu- feedback received on [MS] How to reduce a unuse css file?‭
 
!!/watch- businessconnectindia\.in
 

« first day (3673 days earlier)      last day (75 days later) »