@Tigerware You're welcome to your opinion. If you have an issue with me or my actions as a moderator, you are welcome to use the Contact Us link available at the bottom of all pages of the Main or Meta sites. It is, however, inappropriate to bring something like what I have to assume you're talking about as an issue into this room when the issue didn't originate here in this room.
@SmokeDetector It's not clear to me why this is spam/abusive. It looks like a software engineering HW question, asked on various forums (e.g. coursehero.com/tutors-problems/Computer-Science/…) What am I missing here?
@SmokeDetector To me, the entire first 3/4 of this appears to be marketing copy. The "question" which is tacked on at the bottom feels like a typical "let's as a question which makes them more interested in our company". If the company wasn't real, then I could see it as a made up assignment, but the company and products appear to be real.
So are the multiple places online with that exact text (e.g. the one I linked to), all spam for the company? Certainly possible, but I don't think I've seen something like that before.
@cigien Looking through some of the user's posts, spamming seems a little out of place for the user as well. Not that I can see their deleted content, of course. Anyway, I don't have any issue with the tp feedback, I was just wondering what I missed, and if my fp feedback was totally misplaced. (Implicit fp that is, by choosing to not report it).
@SmokeDetector This list has been updated to include all requests mentioned in the erroneous rollover messages which SD posted when the SE API quota was changed. It should reflect the requests made from the prior actual rollover. The totals of the requests shown matches within a "normal" difference to the reported total remaining requests at the time the quota rolled over.
@Makyen That pattern can't be detected by the number detections. Patterns for the number detections must match the NUMBER_REGEX in phone_numbers.py, at least when deobfuscated. In order to do so, it needs to have between 7 and 20 digits and not include more than one consecutive alpha character (i.e. matching [A-Za-z]). Generally, you should watch/blacklist the non-obfuscated version of the number. The supplied pattern contains 0 digits, which doesn't meet the requirements.
@Makyen That pattern appears to be homoglyph obfuscated. It's better to use the non-obfuscated number. Perhaps try: !!/blacklist-number 87977:84804. That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 879-778-4804 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 879-778-4804. 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.
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 02:31:29 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 02:31:48 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 02:32:03 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 02:32:17 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 02:32:37 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
@SmokeDetector NAA Link goes to official Instagram page, not individual account, and honestly seems like someone doing a poor job of asking for help in an answer. If someone has evidence of TP instead of NAA, I'm happy to hear it though
@Nick 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 ] Bad keyword with email in answer, link at end of answer, potentially bad ns for domain in answer (147): Shared IC tape out by Jane教英语 on electronics.SE
@SmokeDetector The question asks about someone abusing the system to get multiple association bonuses. This appears to be from the person who was abusing the system (i.e. the one the question is asking about), who is now using this answer to abuse the question OP with the listed account usernames (listed usernames are derogatory variations on the question OP's username).
@cocomac Potentially bad keyword in body - Position 212-315: buy a new one again. Or what would help here?</p><p>RTX 3070 Ti, i9-12900k 32GB 3200MHz RAM</p><p><a
@cocomac ' buy a new one again. Or what would help here?</p><p>RTX 3070 Ti, i9-12900k 32GB 3200MHz RAM</p><p><a' is not caught by a blacklist or watchlist item.
sdc bisect lding with cycles. My Render settings and some statistics you can see below. Is it enough if I upgrade my RAM because my graphics card is actually very good and I don't want to buy a new one again. Or what would help here?
@SmokeDetector You rolled over again, so soon??? I wonder if it's going to roll over at the "normal" time too. In other words, is this because of some time shift, or is one of SE's servers out of sync?
@CodyGray Yeah, that is a bit longer than other responses. A) because the "blacklist-" was previously missing in all the suggested "!!/blacklist-number" statements, a recently fixed bug. B) That response hits a number of the possible different responses, which are combined together into that response. I don't recall if it will make an even longer response (without changing the code), but, now, I'm tempted to try. :)
@CodyGray @JeffSchaller For the "buy within 400 characters" watched regex which you were interested in, has, since it was added, 8375 Total / 3337 TP (39.84% TP) / 4885 FP / 136 NAA. The TP rate could certainly be improved. For this, like many watches, the important thing will be to make sure we're still detecting the TP where this is the only detection.
> Bad phone number in body, bad phone number in title ---------- Bad phone number in body - 8521184871 found obfuscated Bad phone number in title - 8521184871 found obfuscated
