@cigien In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. In order for a "number" to make an exact match, the pattern must end with a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@cigien Deobfuscated: +44 7459 299307; deobfuscated and normalized: 447459299307
@cigien In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector The question was edited to include links to learnshareit (and not a specific article). Given the spam posts for that domain in the last 10 days, this is suspicious.
@cigien As the code is currently written, the deobfuscation wouldn't get rid of those, as they don't translate to a number, but the normalization does remove them, as normalization removes everything except numbers.
@cigien I suspect what might have happened is that you copied the normalized version as an edit into the already existing "sdc watch-number ", but didn't end up deleting the LEFT-TO-RIGHT EMBEDDING character which existed just after the space. Without explicitly intending to delete the invisible character, it would have been very easy to not delete it, thinking that you were leaving the space. Basically, to be sure, you would have needed to also delete the space and then re-type the space.
I thought we explicitly warned when patterns contained the embedding or override characters, but it seems that logic could be improved, or my memory isn't accurate.
Yeah, I copy-pasted only the number part of the text, and didn't edit any of the other part of the message, including the space. Good to know that's what might have caused it.
[ SmokeDetector | MS ] Pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer (79): BUTTONS AND MODALS by gujjar on stackoverflow.com
@tripleee 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.
@tripleee 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.
@tripleee Already watched on line 38492 of watched_keywords.txt
The quota_remaining property was not in the API response. Error: no method found with this name at 05:07:52 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, body starts with title and ends in url, link at end of body, potentially bad asn for hostname in body, potentially bad ns for domain in body, +1 more (291): Aspirin Manufacturer by Saphnix Lifesciences on superuser.com
@tripleee 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.
@tripleee 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 ] Bad ns for domain in body, bad keyword in body, blacklisted website in body, potentially bad keyword in body (289): What is Spring Framework? by aakhil on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, pattern-matching product name in body, potentially bad asn for hostname in body, +1 more (361): Adidas Ultra Boost Shoes Sale by Bilal Bajwa on stackoverflow.com
@RyanM To avoid SmokeDetector reporting posts too slowly, you can report at most 5 posts at a time. This is to avoid SmokeDetector's chat messages getting rate-limited too much, which would slow down reports.
!!/report stackoverflow.com/a/74544638 "A very confused spammer mistakes SO for a traditional discussion forum and also seems to briefly forget what acccount they're using?"
@tripleee I'll have to look at it more closely to figure out what's going on, but that seems to be around where the check's happening. Thanks for the pointer.
it's pretty involved, I was looking at it the other day for the earlier question about why something wasn't reported ... it could use some comments methinks
@tripleee 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.
