> Bad keyword in body, bad keyword in title, bad keyword in username, phone number detected in title ---------- Bad keyword in body - Position 9-23: support number Bad keyword in title - Position 9-23: support number Bad keyword in username - Position 9-23: support number Phone number detected in title - Phone number: 1234567890
Added a few watches to catch similar posts to the ones this was targeted at (which were all caught by lots of rules), removing this one since it's hitting a bunch of legitimate biology posts
I'm conflicted on that. One set of pretty spammy posts (with disclosed affiliation) two years ago (pre-launch), no sign of issues since, and a decent chunk of FP. The helpful articles on their site are definitely an SEO trick, though...and extremely formulaic
https://zoomadmin.com/HowToInstall/UbuntuPackage/ + any package name spits out a page on how to install it
@SmokeDetector There were actually 4 of these from this user. The link leads to a blog which then tries to sell you the source code for $100. The blog post was created today.
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (95): How to send a push notification by Paul on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (95): Array of errors display in php by Paul on stackoverflow.com
@RyanM Given what the site sells, their history and it absolutely not being an answer of any kind, I went with a spam flag. I think this is the kind of crap we'll encounter more and more: spam in disguise.
@Mast I'm a bit confused, though, why not post it as a question? They clearly know how to post questions given that they spammed ... checks ... eight of them onto the network.
@RyanM That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; in addition, the regex contains an unescaped "."; in most cases, it should be "\."; append -force if you really want to do that.
@SmokeDetector tpu- undisclosed (...I think... working with Google Translate here) affiliation, user is the author of the post. Note display name "jiaozongguan" vs username of post author "jiao_zg"
@SmokeDetector that's a mess of a promotional answer, but it answers the question and the affiliation is disclosed...not sure how softwarerecs.SE handles stuff like that.
@RyanM That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
If anyone wants to try the bookmarklet I've been using to automate parts of the watchlisting workflow, here it is:
javascript:(async function () {
/* Based on this bookmarklet by Makyen: chat.stackexchange.com/transcript/11540?m=55327802
* which is based on this code by Tim Down to get selected text: stackoverflow.com/a/5379408/208273
*/
var text = "";
const activeEl = document.activeElement;
const activeElTagName = activeEl ? activeEl.tagName.toLowerCase() : null;
if ((activeElTagName == "textarea" || activeElTagName == "input") && /^(?:text|textarea|search|password|tel|url)$/i.test(activeEl.type) && (typeof activeEl.selectionStart == "number")) {
Suggestions welcome, as I am not a JavaScript or web programmer.
Extra bonus points if you can make it not sometimes fail to copy the watch text. Pretty sure it's a focus problem (focused on browser UI rather than the page).
@RyanM Matched by pinterest\.com(?<!api\.pinterest\.com)(?<!assets\.pinterest\.com)(?<!developers\.pinterest\.com) on line 15792 of watched_keywords.txt
@SmokeDetector this watch matches something like 3 clear TP under 100 score, and 125 FP. Need to look more later but it could probably be significantly restricted.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the remote contains work that you do hint: not have locally. This is usually caused by another repository pushing hint: to the same ref. You may want to first integrate the remote changes hint: (e.g., 'git pull ...') before pushing again.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
