Some time ago I came across this question which is no more than 'How can I make a site like this <link>'. When I saw this, I thought it was so low quality it was hard to believe it was a serious question and was more likely a spam post. However, my spam flag on the post was declined. When are que...
sdc test In this collection, we offer personalized gifts to express your condolences for those who are dealing with the loss of a pet. From custom keepsakes to practical items like mugs, hoodies, or blankets, these meaningful gifts will be moral support for anyone during the darkest time.
> Potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in title - Position 20-28: we offer Potentially bad keyword in username - Position 20-28: we offer
sdc test-q In this collection, we offer personalized gifts to express your condolences for those who are dealing with the loss of a pet. From custom keepsakes to practical items like mugs, hoodies, or blankets, these meaningful gifts will be moral support for anyone during the darkest time.
line 2360 of findspam.py mentions "we offer" but in line 2365 it appears that it doesn't trigger on body. Should that be changed? I don't see any particular reason that "We offer" would be a frequently used phrase anywhere
'Don't flag if some small part of the answer seems to indicate "me too" since a small edit can fix that and reinforce the part of the answer that is relevant.'
It seems to indicate that if the entire answer is "me too" and not a part of the answer, then flagging is appropriate. It would seem to me that the answer would make for a fantastic comment, but a poor answer. I suppose I ought to pick my battles
@ThomasWard The most recent known functional was 2022-06-10. I did check the general formatting of the confirmation email between a 2018 copy and today. It appeared that if it gets to the function on MS which is supposed to decode the email, then it (grossly) appears that it should be working. I'd need to add a variety of logging into that code to verify that it's getting called and/or that it's properly decoding the message data.
Given that there's something in AWS that's doing the relay from receiving the email to a POST to MS, that seems like a likely place that it would be failing.
@Brandon_J np. It's something that happens to all of us from time to time. It often helps to have more than one person look at things. Having more than one person look at changes/issues is one of the reasons we have most things done publicly here in Charcoal HQ.
@Brandon_J I know I've forgotten to check that a bunch of times too. With domains specifically, FIRE Additional Functionality can show SE hits and MS hits (if you use FIRE)
@Brandon_J cocomac addressed this, but in fact the standard for NAA (link-only, "me-too", etc) is very different on AskDifferent than on an pretty much any other SE site. e.g. Link-only answers are not NAA if there's even the slightest hint of it being helpful. Many users have been bitten by this, as was I, and I've ended up asking for the guidance to be clearer.
The FAQ was updated in Rev 10 to explicitly state that the guidance is different than on the rest of the network, which is about as clear as it can be made (without changing the actual flagging dialog). So basically, avoid raising NAA flags unless they're literally saying something along the lines of "thanks, this helped".
Note that this doesn't affect how you give feedback to SD in any way. If you're generally giving naa feedback to SD for reports of link-only answers, you can continue doing so for reports of AskDifferent answers as well. You should just refrain from raising a NAA flag on the site for such answers.
@SmokeDetector I'm not sure this is actually spam. The question is asking for such recommendation answers, and the recommendation itself seems legit (there's another answer on the question that refers to it, as far as I can see). A site mod has also definitely seen the answer, and chosen not to delete it.
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, messaging number in answer, pattern-matching email in answer, potentially bad keyword in answer (366): Predicting lottery numbers by Raymond Buxton on math.SE
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:19:44 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:20:09 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:20:24 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:20:38 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:20:52 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
@tripleee 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.
@tripleee 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.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in username, +1 more (173): laser removal in San Diego ✏️ by Allurant medical on meta.SE (@Ollie)
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body (293): Unfinished Java Assignment by bro jack on meta.SE (@Ollie)
@RyanM 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.
@tripleee The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector Indian flower spam IPs, also watched the whole AS but will probably have to disable it if they manage to reverse the trend of new spam domains
[ SmokeDetector | MS ] Bad keyword in body, body starts with title and ends in url, link at beginning of body, link at end of body, potentially bad asn for hostname in body, +3 more (430): Repair My Appliances by Working Mail on askubuntu.com
