@Nick That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
> Blacklisted website in body, blacklisted website in title, blacklisted website in username, potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Blacklisted website in body - Position 0-11: quytech.com Blacklisted website in title - Position 0-11: quytech.com Blacklisted website in username - Position 0-11: quytech.com Potentially bad ns for domain in body - quytech.com NS suspicious ns8545.hostgator.com.,ns8546.hostgator.com. Potentially bad ns for domain in title - quytech.com NS suspicious ns8545.hostgator.com.,ns8546.hostgator.com.
STDERR: To https://github.com/Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to 'https://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
STDERR: To https://github.com/Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to 'https://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
I'm kind of wondering how users are discovering Discussions. Seems some find it easily, others not at all. Some spammers seems to home in on it (and never post on other sites) others also post there. But the latter seem to be rarer.
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - orientrailjourneys.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com. Potentially bad ns for domain in title - orientrailjourneys.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com.
@Machavity They made three discussion posts today, the more recent two had random gibberish in the title and a copy-paste code dump, which is why I chose R/A. Not disputing your decision, just explaining why I chose what I did.
@Fastnlight 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.
@SmokeDetector This is weird. After the user got called out for a mistake on the first one, they came back with the same graph, just photoshopped out the part that contradicts their claim.
@Catija I don't think it is spam, rather a list of filters and features they found at that other platform. I've edited out that platform name and the answer seems now reasonable to me. Anyway feel free to rollback if you disagree
^ OP is an established user and their profile seems not to be linked to that mentioned job platform
Though I certainly see where your initial reaction came from
I think it's a response to "When thinking about searching for your next technical role, what pieces of information or features would be most useful for you?"
@Makyen 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.
@Makyen 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.
