@Vickel A normalized version, {{'9831749976'}}, 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 9831-749-976 to determine which entries on the number lists match that pattern, which would tell you: Matched by 9831-7499-76 on line 4694 of watched_numbers.txt: 9831749976 found normalized
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-6: Bitget Potentially bad keyword in title - Position 0-6: Bitget Potentially bad keyword in username - Position 0-6: Bitget
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Bad keyword in body - Position 0-17: OKX Referral Code Bad keyword in title - Position 0-17: OKX Referral Code Bad keyword in username - Position 0-17: OKX Referral Code
@Vickel ahh, sorry I misunderstood. My general reaction was to follow the blacklisting guidelines. I then got distracted by real life stuff (ongoing). I'd be happy to chat more about the idea in circa 10 hours, if you like. (Feel free to ping me in chat ahead of time; I just can't focus here right now)
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Cloud Invoice API by camelll275 on softwarerecs.SE
@tripleee Blacklisted alphanapkinmachines\.com. However, the blacklists were not reloaded at this time. The most likely issue is another change was made on SD's master branch on GitHub and everything is waiting for CI to pass and MS to update the deploy branch. That could take a few to several minutes. If SD doesn't automatically reload the blacklists or automatically reboot after that time, then someone should investigate why that hasn't happened.
@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.
@Cow Huh. Interesting. Seems like partly ESL maybe. I searched online and I found a few places that use it correctly. As in something like "Click here to link your account" or even "Click here to link" (and "here" is the hyperlink. You're on some linking page). But also few places do seem to just use it like that spam did. In fact, one result was the same kind of spam (claims it's a leaked video).
Some of the network search results are indeed using the incorrect phrase (again, probably ESL issue). Some have the words close to each other but the actual message is correct. E.g.
@tripleee excuse me sir, do you know what the ETA is on my PR on the Charcoal website edit on Github? It seems to fade over time, maybe we dont even need it? :)
@tripleee no problem, I was just thinking it might not even be needed I dunno, the talks went on a version 1 and then if people wanted we could add more later
