@JeffSchaller A normalized version, {{'7815000083'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number 7815+0000+83 to determine which entries on the number lists match that pattern, which would tell you: Matched by 7815000083(?#IS NorAm) on line 3163 of watched_numbers.txt: 7815000083 found normalized
@JeffSchaller 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 786-695-0486 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 !!/watch-number 786-695-0486. Append -force to the command word(s) if you really want to add the pattern you provided.
@cocomac looks like it's been deleted, now; I can't see the history, but one possibility is that "closure" was the first tool that came to mind for that mod, just to stop the bleeding, before finally seeing that it was spam. Mods that don't see as much spam as the "regulars" here aren't as tuned-in to it, maybe?
It seems to me that someone is simply trying to give Andersen a bad name here; was about to blacklist andersenlab\.com, but I'm not 100% there. Anyone else, feel free, but this one seems weirdly persistent.
Just a nagging feeling/memory that Andersen is/was a legit larger consulting firm; if I wrote 5 NAA posts saying "www.google.com is the greatest", I wouldn't expect a blacklist of google.com (for example).
again, no real objections to it being blacklisted, I just couldn't bring myself to do it
@JeffSchaller It sounds like the right thing to do would be to go ahead and blacklist the domain, as it does meet the blacklisting criteria and the posts are quite clear spam. An abuse report could then be created and the company contacted to report to them that someone is spamming for them. That might result in a response and, perhaps, a change in behavior. The company may or may not be aware of the campaign and/or aware of what is actually being done as a result of a directive.
We've seen spam and/or inappropriate behavior from users who are directly employed by or contracted to larger companies (e.g. Google and Microsoft). Such things do happen.
@ThomasWard The timeout for queries to MS is back down to a "normal" length of 60 s, which, among other things, causes longer searches to return a "504 Gateway Time-out". When you get a chance, I'd appreciate it if you could adjust the timeout back up to the hour or two at which it was previously. I don't, currently, have anything pressing which this issue is blocking, but it's possible other's might. This is just a "please take care of this when you have a chance", not a "need immediately".
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ns for domain in body, potentially bad keyword in body (42): Site ktaabhulul by Ktaabhulul on webmasters.SE
