@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.
@JeffSchaller A normalized version, {{'16015572843', '6015572843'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +1(601)557-2843 to determine which entries on the number lists match that pattern, which would tell you: Matched by +1(601)557-2843 on line 3593 of watched_numbers.txt: +1(601)557-2843 found verbatim; 6015572843 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 840-938-7675 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 840-938-7675. Append -force to the command word(s) if you really want to add the pattern you provided.
Both metasmoke and SmokeDetector/Thoth will be going down starting NOW for the next hour or so while I do some migrations from low-capacity storage to larger capacity storage.
@Makyen A normalized version, {{'27672740459'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +27672740459 to determine which entries on the number lists match that pattern, which would tell you: Matched by 27672740459 on line 3584 of watched_numbers.txt: 27672740459 found normalized
@JohannesKuhn I'm sorry. I set you up for failure there by not remembering that MS is down at the moment. OTOH, we've at least cleared up what the procedure should be for you once MS is back up.
@Jesse also, yes, whenever there's maintenance on my end or unexpected outage beyond a quick reboot i usually post a pinned message at the top of the star wall
@Jesse Survey/questionnaire posts are treated as spam on ru.so. As Vickel said, probably a mis-click. A bit odd though, since my spam flag was marked helpful.
There will be an EXTENDED outage of SmokeDetector's teward/Thoth instance and Metasmoke starting on June 1, 2023 in the Eastern US timezone. This outage will last up to two days at most while MASSIVE overhauls of the infrastructure (wiring, configuration, etc.) are implemented - these massive overhauls of the infra are overdue by over a year and needs to be done now.
Regarding the current issues within Stack Exchange, any decisions or discussions regarding Charcoal or SmokeDetector will be handled internally within the Charcoal team, and these discussions on this topic are not open. Please do not ask us to do anything in response to the current state of affairs / issues. (Posts asking us to do things or our opinions on this matter as Charcoal will be deleted)
